-var root = angular.module.ng.$rootScope.Scope();
-var child = root.$new();
-
-root.name = 'angular';
-expect(child.name).toEqual('angular');
-expect(root.name).toEqual('angular');
-
-child.name = 'super-heroic framework';
-expect(child.name).toEqual('super-heroic framework');
-expect(root.name).toEqual('angular');
+it('should inherit properties', inject(function($rootScope)) {
+ var root = $rootScope;
+ var child = root.$new();
+
+ root.name = 'angular';
+ expect(child.name).toEqual('angular');
+ expect(root.name).toEqual('angular');
+
+ child.name = 'super-heroic framework';
+ expect(child.name).toEqual('super-heroic framework');
+ expect(root.name).toEqual('angular');
+});
@@ -172,8 +174,8 @@ doesn't need to worry about propagating the `$digest` call from the parent scope
This happens automatically.
## Scopes in unit-testing
-You can create scopes, including the root scope, in tests using the {@link api/angular.module.ng.$rootScope.Scope
-angular.module.ng.$rootScope.Scope()} API. This allows you to mimic the run-time environment and have full control over
+You can create scopes, including the root scope, in tests by having the $rootScope injected into
+your spec. This allows you to mimic the run-time environment and have full control over
the life cycle of the scope so that you can assert correct model transitions. Since these scopes
are created outside the normal compilation process, their life cycles must be managed by the test.
@@ -183,18 +185,20 @@ within the unit-tests.
// example of a test
- var scope = angular.module.ng.$rootScope.Scope();
- scope.$watch('name', function(scope, name){
- scope.greeting = 'Hello ' + name + '!';
- });
-
- scope.name = 'angular';
- // The watch does not fire yet since we have to manually trigger the digest phase.
- expect(scope.greeting).toEqual(undefined);
-
- // manually trigger digest phase from the test
- scope.$digest();
- expect(scope.greeting).toEqual('Hello Angular!');
+ it('should trigger a watcher', inject(function($rootScope) {
+ var scope = $rootScope;
+ scope.$watch('name', function(scope, name){
+ scope.greeting = 'Hello ' + name + '!';
+ });
+
+ scope.name = 'angular';
+ // The watch does not fire yet since we have to manually trigger the digest phase.
+ expect(scope.greeting).toEqual(undefined);
+
+ // manually trigger digest phase from the test
+ scope.$digest();
+ expect(scope.greeting).toEqual('Hello Angular!');
+ }
diff --git a/docs/content/guide/dev_guide.services.creating_services.ngdoc b/docs/content/guide/dev_guide.services.creating_services.ngdoc
index 06d57d77..4ce16a76 100644
--- a/docs/content/guide/dev_guide.services.creating_services.ngdoc
+++ b/docs/content/guide/dev_guide.services.creating_services.ngdoc
@@ -1,51 +1,100 @@
@ngdoc overview
-@name Developer Guide: Angular Services: Creating Angular Services
+@name Developer Guide: Angular Services: Creating Services
@description
While angular offers several useful services, for any nontrivial application you'll find it useful
to write your own custom services. To do this you begin by registering a service factory function
-that angular's DI will use to create the service object when it is needed.
-
-The `angular.module.ng` method accepts three parameters:
-
-- `{string} name` - Name of the service.
-- `{function()} factory` - Factory function(called just once by DI).
-- `{Object} config` - Configuration object with the following properties:
- - `$inject` - {Array.
+var myModule = angular.module('myModule', []);
+myModule.factory('serviceId', function() {
+ var shinyNewServiceInstance;
+ //factory function body that constructs shinyNewServiceInstance
+ return shinyNewServiceInstance;
+});
+
+
+Using the $provide service:
+
+angular.module('myModule', [], function($provide) {
+ $provide.factory('serviceId', function() {
+ var shinyNewServiceInstance;
+ //factory function body that constructs shinyNewServiceInstance
+ return shinyNewServiceInstance;
+ });
+});
+
+
+Note that you are not registering a service instance, but rather a factory function that will
+create this instance when called.
+
+
+# Dependencies
+
+Services can not only be depended upon, but also have its own dependencies. These can be specified
+as arguments of the factory function. {@link dev_guide.di.understanding_di Read more} about the DI
+in Angular and the use of array notation and $inject property to make DI annotation
+minification-proof.
+
Following is an example of a very simple service. This service depends on the `$window` service
(which is passed as a parameter to the factory function) and is just a function. The service simply
stores all notifications; after the third one, the service displays all of the notifications by
window alert.
- angular.module.ng('notify', function(win) {
- var msgs = [];
- return function(msg) {
- msgs.push(msg);
- if (msgs.length == 3) {
- win.alert(msgs.join("\n"));
- msgs = [];
- }
- };
- }, {$inject: ['$window']});
+angular.module('myModule', [], function($provide) {
+ $provide.factory('notify', ['$window', function(win) {
+ var msgs = [];
+ return function(msg) {
+ msgs.push(msg);
+ if (msgs.length == 3) {
+ win.alert(msgs.join("\n"));
+ msgs = [];
+ }
+ };
+ }]);
+});
+# Instantiating Angular Services
+
+All services in Angular are instantiates services lazily, this means that a service will be created
+only when it is needed for instantiation of a service or an application component that depends on it.
+In other words, angular won't instantiate lazy services unless they are requested directly or
+indirectly by the application.
+
+
+# Services as singletons
+
+Lastly, it is important to realize that all angular services are application singletons. This means
+that there is only one instance of a given service per injector. Since angular is lethally allergic
+to the global state, it is possible to create multiple injectors, each with its own instance of a
+given service, but that is rarely needed, except in tests where this property is crucially
+important.
+
+
+
## Related Topics
* {@link dev_guide.services.understanding_services Understanding Angular Services}
-* {@link dev_guide.services.registering_services Registering Angular Services}
* {@link dev_guide.services.managing_dependencies Managing Service Dependencies}
* {@link dev_guide.services.injecting_controllers Injecting Services Into Controllers }
* {@link dev_guide.services.testing_services Testing Angular Services}
diff --git a/docs/content/guide/dev_guide.services.injecting_controllers.ngdoc b/docs/content/guide/dev_guide.services.injecting_controllers.ngdoc
index e98eb5e0..9f48d3c7 100644
--- a/docs/content/guide/dev_guide.services.injecting_controllers.ngdoc
+++ b/docs/content/guide/dev_guide.services.injecting_controllers.ngdoc
@@ -71,7 +71,6 @@ it('should test service', function() {
{@link dev_guide.services.understanding_services Understanding Angular Services}
{@link dev_guide.services.creating_services Creating Angular Services}
-{@link dev_guide.services.registering_services Registering Angular Services}
{@link dev_guide.services.managing_dependencies Managing Service Dependencies}
{@link dev_guide.services.testing_services Testing Angular Services}
diff --git a/docs/content/guide/dev_guide.services.managing_dependencies.ngdoc b/docs/content/guide/dev_guide.services.managing_dependencies.ngdoc
index 43e5a4ae..bccc6539 100644
--- a/docs/content/guide/dev_guide.services.managing_dependencies.ngdoc
+++ b/docs/content/guide/dev_guide.services.managing_dependencies.ngdoc
@@ -5,12 +5,42 @@
Angular allows services to declare other services as dependencies needed for construction of their
instances.
-To declare dependencies, you specify them in the factory function signature and via the `$inject`
-property, as an array of string identifiers. Optionally the `$inject` property declaration can be
+To declare dependencies, you specify them in the factory function signature and annotate the
+function with the inject annotations either using by setting the `$inject` property, as an array of
+string identifiers or using the array notation. Optionally the `$inject` property declaration can be
dropped (see "Inferring `$inject`" but note that that is currently an experimental feature).
+Using the array notation:
+
+
+function myModuleCfgFn($provide) {
+ $provide.factory('myService', ['dep1', 'dep2', function(dep1, dep2) {}]);
+}
+
+
+
+Using the $inject property:
+
+
+function myModuleCfgFn($provide) {
+ var myServiceFactory = function(dep1, dep2) {};
+ myServiceFactory.$inject = ['dep1', 'dep2'];
+ $provide.factory('myService', myServiceFactory);
+}
+
+
+
+Using DI inference (incompatible with minifiers):
+
+
+function myModuleCfgFn($provide) {
+ $provide.factory('myService', function(dep1, dep2) {});
+}
+
+
+
Here is an example of two services that depend on each other, as well as on other services that are
-provided by angular's web framework:
+provided by Angular's web framework:
/**
@@ -63,22 +93,21 @@ Things to notice in this example:
`console.log` in batches.
* The `routeTemplateMonitor` service depends on the built-in {@link api/angular.module.ng.$route
$route} service as well as our custom `batchLog` service.
-* Both of our services use the factory function signature as well as the `$inject` property to
-declare their dependencies. It is important that the order of the string identifiers in the array
-associated with the `$inject` property is the same as the order of argument names in the signature
-of the factory function. Unless the dependencies are inferred from the function signature, it is
-this array with IDs and their order that the injector uses to determine which services and in which
-order to inject.
+* Both of our services use the factory function signature and array notation for inject annotations
+to declare their dependencies. It is important that the order of the string identifiers in the array
+is the same as the order of argument names in the signature of the factory function. Unless the
+dependencies are inferred from the function signature, it is this array with IDs and their order
+that the injector uses to determine which services and in which order to inject.
## Related Topics
* {@link dev_guide.services.understanding_services Understanding Angular Services}
* {@link dev_guide.services.creating_services Creating Angular Services}
-* {@link dev_guide.services.registering_services Registering Services}
* {@link dev_guide.services.injecting_controllers Injecting Services Into Controllers }
* {@link dev_guide.services.testing_services Testing Angular Services}
+
## Related API
* {@link api/angular.module.ng Angular Service API}
diff --git a/docs/content/guide/dev_guide.services.ngdoc b/docs/content/guide/dev_guide.services.ngdoc
index d59dafe9..bd000507 100644
--- a/docs/content/guide/dev_guide.services.ngdoc
+++ b/docs/content/guide/dev_guide.services.ngdoc
@@ -12,9 +12,8 @@ most often used with {@link dev_guide.di dependency injection}, also a key featu
* {@link dev_guide.services.understanding_services Understanding Angular Services}
* {@link dev_guide.services.creating_services Creating Angular Services}
-* {@link dev_guide.services.registering_services Registering Angular Services}
* {@link dev_guide.services.managing_dependencies Managing Service Dependencies}
-* {@link dev_guide.services.injecting_controllers Injecting Services Into Conrollers}
+* {@link dev_guide.services.injecting_controllers Injecting Services Into Controllers}
* {@link dev_guide.services.testing_services Testing Angular Services}
## Related API
diff --git a/docs/content/guide/dev_guide.services.registering_services.ngdoc b/docs/content/guide/dev_guide.services.registering_services.ngdoc
deleted file mode 100644
index 25a51504..00000000
--- a/docs/content/guide/dev_guide.services.registering_services.ngdoc
+++ /dev/null
@@ -1,64 +0,0 @@
-@ngdoc overview
-@name Developer Guide: Angular Services: Registering Angular Services
-@description
-
-To register a service, retrieve the {@link api/angular.module.AUTO.$provide $provide} service and use one of itse
-registration methods for new service declaration. The following pseudo-code shows a simple service registration:
-
-
-$provide.factory('service id', function() {
- var shinyNewServiceInstance;
- //factory function body that constructs shinyNewServiceInstance
- return shinyNewServiceInstance;
-});
-
-
-Note that you are not registering a service instance, but rather a factory function that will
-create this instance when called.
-
-# Instantiating Angular Services
-
-A service can be instantiated eagerly or lazily. By default angular instantiates services lazily,
-which means that a service will be created only when it is needed for instantiation of a service or
-an application component that depends on it. In other words, angular won't instantiate lazy
-services unless they are requested directly or indirectly by the application.
-
-Eager services on the other hand, are instantiated right after the injector itself is created,
-which happens when the angular {@link dev_guide.bootstrap application initializes}.
-
-To override the default, you can request that a service is eagerly instantiated as follows:
-
-
-angular.module.ng('service id', function() {
- var shinyNewServiceInstance;
- //factory function body that constructs shinyNewServiceInstance
- return shinyNewServiceInstance;
-});
-
-
-* Nothing in your application declares this service as its dependency, and this service affects the
-state or configuration of the application (e.g. a service that configures `$route` or `$resource`
-services)
-* A guarantee is needed that the service will be instantiated at application boot time, usually
-because the service passively observes the application and it is optional for other application
-components to depend on it. An example of this scenario is a service that monitors and logs
-application memory usage.
-
-Lastly, it is important to realize that all angular services are applicaiton singletons. This means
-that there is only one instance of a given service per injector. Since angular is lethally allergic
-to the global state, it is possible to create multiple injectors, each with its own instance of a
-given service, but that is rarely needed, except in tests where this property is crucially
-important.
-
-
-## Related Topics
-
-* {@link dev_guide.services.understanding_services Understanding Angular Services}
-* {@link dev_guide.services.creating_services Creating Angular Services}
-* {@link dev_guide.services.managing_dependencies Managing Service Dependencies}
-* {@link dev_guide.services.injecting_controllers Injecting Services Into Controllers }
-* {@link dev_guide.services.testing_services Testing Angular Services}
-
-## Related API
-
-* {@link api/angular.module.ng Angular Service API}
diff --git a/docs/content/guide/dev_guide.services.testing_services.ngdoc b/docs/content/guide/dev_guide.services.testing_services.ngdoc
index c18cfda1..d867215b 100644
--- a/docs/content/guide/dev_guide.services.testing_services.ngdoc
+++ b/docs/content/guide/dev_guide.services.testing_services.ngdoc
@@ -11,7 +11,14 @@ var mock, notify;
beforeEach(function() {
mock = {alert: jasmine.createSpy()};
- notify = angular.module.ng('notify')(mock);
+
+ module(function($provide) {
+ $provide.value('$window', mock);
+ });
+
+ inject(function($injector) {
+ notify = $injector.get('notify');
+ });
});
it('should not alert first two notifications', function() {
@@ -47,12 +54,9 @@ it('should clear messages after alert', function() {
* {@link dev_guide.services.understanding_services Understanding Angular Services}
* {@link dev_guide.services.creating_services Creating Angular Services}
-* {@link dev_guide.services.registering_services Registering Angular Services}
* {@link dev_guide.services.managing_dependencies Managing Service Dependencies}
* {@link dev_guide.services.injecting_controllers Injecting Services Into Conrollers}
## Related API
* {@link api/angular.module.ng Angular Service API}
-
-
diff --git a/docs/content/guide/dev_guide.services.understanding_services.ngdoc b/docs/content/guide/dev_guide.services.understanding_services.ngdoc
index ac4a7909..390ced0c 100644
--- a/docs/content/guide/dev_guide.services.understanding_services.ngdoc
+++ b/docs/content/guide/dev_guide.services.understanding_services.ngdoc
@@ -12,14 +12,14 @@ of the rest. The angular injector subsystem is in charge of service instantiatio
dependencies, and provision of dependencies to factory functions as requested.
Angular injects dependencies using "constructor" injection (the service is passed in via a factory
-function). Because JavaScript is a dynamically typed language, angular's dependency injection
+function). Because JavaScript is a dynamically typed language, Angular's dependency injection
subsystem cannot use static types to identify service dependencies. For this reason a dependent
must explicitly define its dependencies by using the `$inject` property. For example:
myController.$inject = ['$location'];
The angular web framework provides a set of services for common operations. Like other core angular
-variables and identifiers, the built-in services always start with `$` (such as `$xhr` mentioned
+variables and identifiers, the built-in services always start with `$` (such as `$http` mentioned
above). You can also create your own custom services.
@@ -27,7 +27,6 @@ above). You can also create your own custom services.
* {@link dev_guide.di About Angular Dependency Injection}
* {@link dev_guide.services.creating_services Creating Angular Services}
-* {@link dev_guide.services.registering_services Registering Angular Services}
* {@link dev_guide.services.managing_dependencies Managing Service Dependencies}
* {@link dev_guide.services.testing_services Testing Angular Services}
diff --git a/docs/content/guide/dev_guide.templates.filters.ngdoc b/docs/content/guide/dev_guide.templates.filters.ngdoc
index 52780ec0..0308edb2 100644
--- a/docs/content/guide/dev_guide.templates.filters.ngdoc
+++ b/docs/content/guide/dev_guide.templates.filters.ngdoc
@@ -11,7 +11,8 @@ displaying it to the user. You can pass expressions through a chain of filters l
name | uppercase
-The expression evaluator simply passes the value of name to `angular.module.ng.$filter.uppercase()`.
+The expression evaluator simply passes the value of name to
+{@link api/angular.module.ng.$filter.uppercase uppercase filter}.
In addition to formatting data, filters can also modify the DOM. This allows filters to handle
tasks such as conditionally applying CSS styles to filtered output.
diff --git a/docs/content/guide/dev_guide.unit-testing.ngdoc b/docs/content/guide/dev_guide.unit-testing.ngdoc
index 8b4d4687..a14ddd39 100644
--- a/docs/content/guide/dev_guide.unit-testing.ngdoc
+++ b/docs/content/guide/dev_guide.unit-testing.ngdoc
@@ -252,11 +252,13 @@ format. They are important because they remove the formatting responsibility fro
logic, further simplifying the application logic.
-angular.module.ng.$filter('length', function(text){
- return (''+(text||'')).length;
+myModule.filter('length', function() {
+ return function(text){
+ return (''+(text||'')).length;
+ }
});
-var length = angular.module.ng.$filter('length');
+var length = $filter('length');
expect(length(null)).toEqual(0);
expect(length('abc')).toEqual(3);
diff --git a/docs/content/guide/index.ngdoc b/docs/content/guide/index.ngdoc
index ff66f770..8066d095 100644
--- a/docs/content/guide/index.ngdoc
+++ b/docs/content/guide/index.ngdoc
@@ -47,7 +47,6 @@ of the following documents before returning here to the Developer Guide:
* {@link dev_guide.services.understanding_services Understanding Angular Services}
* {@link dev_guide.services.creating_services Creating Angular Services}
-* {@link dev_guide.services.registering_services Registering Angular Services}
* {@link dev_guide.services.managing_dependencies Managing Service Dependencies}
* {@link dev_guide.services.testing_services Testing Angular Services}
diff --git a/docs/content/tutorial/index.ngdoc b/docs/content/tutorial/index.ngdoc
deleted file mode 100644
index c26ea2df..00000000
--- a/docs/content/tutorial/index.ngdoc
+++ /dev/null
@@ -1,150 +0,0 @@
-@ngdoc overview
-@name Tutorial
-@description
-
-A great way to get introduced to Angular is to work through this tutorial, which walks you through
-the construction of an AngularJS web app. The app you will build is a catalog that displays a list
-of Android devices, lets you filter the list to see only devices that interest you, and then view
-details for any device.
-
-
-
-Work through the tutorial to see how Angular makes browsers smarter — without the use of extensions
-or plug-ins. As you work through the tutorial, you will:
-
-* See examples of how to use client-side data binding and dependency injection to build dynamic
-views of data that change immediately in response to user actions.
-* See how Angular creates listeners on your data without the need for DOM manipulation.
-* Learn a better, easier way to test your web apps.
-* Learn how to use Angular services to make common web tasks, such as getting data into your app,
-easier.
-
-And all of this works in any browser without modification to the browser!
-
-When you finish the tutorial you will be able to:
-
-* Create a dynamic application that works in any browser.
-* Define the differences between Angular and common JavaScript frameworks.
-* Understand how data binding works in AngularJS.
-* Use the angular-seed project to quickly boot-strap your own projects.
-* Create and run tests.
-* Identify resources for learning more about AngularJS.
-
-The tutorial guides you through the entire process of building a simple application, including
-writing and running unit and end-to-end tests. Experiments at the end of each step provide
-suggestions for you learn more about AngularJS and the application you are building.
-
-You can go through the whole tutorial in a couple of hours or you may want to spend a pleasant day
-really digging into it. If you're looking for a shorter introduction to AngularJS, check out the
-{@link misc/started Getting Started} document.
-
-
-
-
-
-
-
-# Working with the code
-
-You can follow this tutorial and hack on the code in either the Mac/Linux or the Windows
-environment. Options for working with the tutorial are to use the Git versioning system for source
-code management or to use scripts that copy snapshots of project files into your workspace
-(`sandbox`) directory. Select one of the tabs below and follow the instructions for setting up your
-computer for your preferred option.
-
-
-
-
- Verify that you have Java installed by running the
-following command in a terminal window:
- java -version
- You will need Java to run unit tests.
Download Git from the Git site.
- You can build Git from source or use the pre-compiled package.
Clone the angular-phonecat repository located at Github by running the following command:
- git clone git://github.com/angular/angular-phonecat.git
- This command creates the angular-phonecat directory in your current
-directory.
Change your current directory to angular-phonecat:
- cd angular-phonecat
- The tutorial instructions assume you are running all commands from the angular-phonecat
-directory.
You will need an http server running on your system. Mac and Linux machines typically
-have Apache pre-installed, but If you don't already have one installed, you can install
-node.js. Use node to run scripts/web-server.js, a simple bundled
-http server.
-
-
-
-
- You will need Java to run unit tests, so run the following command to verify that you
-have Java installed and that the java executable is on
-your PATH.
- java -version
- Install msysGit from the Git site.
Open msysGit bash and clone the angular-phonecat repository located at Github by running the following command:
- git clone git://github.com/angular/angular-phonecat.git
- This command creates the angular-phonecat directory in your current directory.
Change your current directory to angular-phonecat.
- cd angular-phonecat
- The tutorial instructions assume you are running all commands from the angular-phonecat
-directory.
- You should run all git commands from msysGit bash.
- Other commands like test-server.bat or test.bat should be
-executed from the Windows command line.
You need an http server running on your system. If you don't already have one
-installed, you can install node.js. Download the pre-compiled binaries, unzip them, and then add
-nodejs\bin into your PATH. Use node to run
-scripts\web-server.js, a simple, bundled http server.
-
-
-
-
- You need Java to run unit tests, so verify that you have Java installed by running the following command in a terminal
-window:
- java -version
- Download the zip archive
-containing all of the files and unzip them into the [tutorial-dir] directory
.Change your current directory to [tutorial-dir]/sandbox, as follows:
- cd [tutorial-dir]/sandbox
- The tutorial instructions assume you are running all commands from your
-sandbox directory.
You need an http server running on your system and Mac and Linux machines typically
-have Apache pre-installed. If you don't have an http server installed, you can install
-node.js and use it to run scripts/web-server.js, a simple bundled http
-server.
-
-
-
-
- Verify that you have Java installed and that the
-java executable is on your PATH by running the following command in the
-Windows command line:
- java -version
- You need Java to run unit tests, so download the zip archive that contains all of the files
-and unzip the files into the [tutorial-dir] directory
Change your current directory to [tutorial-dir]/sandbox, as follows:
- cd [tutorial-dir]/sandbox
- The tutorial instructions assume you are running all commands from this directory.
You need an http server running on your system, but if you don't already have one
-already installed, you can install node.js. Download the pre-compiled binaries, unzip them, and then add
-nodejs\bin into your PATH. Use node to run
-scripts\web-server.js, a simple bundled http server.
-
-
-
-The last thing to do is to make sure your computer has a web browser and a good text editor
-installed. Now, let's get going with {@link step_00 step 0}.
diff --git a/docs/content/tutorial/step_00.ngdoc b/docs/content/tutorial/step_00.ngdoc
deleted file mode 100644
index b7f469ff..00000000
--- a/docs/content/tutorial/step_00.ngdoc
+++ /dev/null
@@ -1,216 +0,0 @@
-@ngdoc overview
-@name Tutorial: 0 - angular-seed
-@description
-
--
-
In angular-phonecat directory, run this command:
-
-git checkout -f step-0This resets your workspace to step 0 of the tutorial app.
-You must repeat this for every future step in the tutorial and change the number to - the number of the step you are on. This will cause any changes you made within - your working directory to be lost.
-
- - To see the app running in a browser, do one of the following:
-
-
-
- For node.js users:
-
-
-
- In a separate terminal tab or window, run
-
./scripts/web-server.jsto start the web server.
- - Open a browser window for the app and navigate to http://localhost:8000/app/index.html -
- - In a separate terminal tab or window, run
-
- For other http servers:
-
-
-
- Configure the server to serve the files in the
angular-phonecat-directory.
- - Navigate in your browser to
-
http://localhost:[port-number]/[context-path]/app/index.html.
-
- - Configure the server to serve the files in the
- - For node.js users:
-
-
-
Open msysGit bash and run this command (in angular-phonecat directory):
-
-git checkout -f step-0This resets your workspace to step 0 of the tutorial app.
-You must repeat this for every future step in the tutorial and change the number to - the number of the step you are on. This will cause any changes you made within - your working directory to be lost.
- - To see the app running in a browser, do one of the following:
-
-
-
- For node.js users:
-
-
-
- In a separate terminal tab or window, run
node -scripts\web-server.jsto start the web server.
- - Open a browser window for the app and navigate to http://localhost:8000/app/index.html -
- - In a separate terminal tab or window, run
- For other http servers:
-
-
-
- Configure the server to serve the files in the
angular-phonecat-directory.
- - Navigate in your browser to
-
http://localhost:[port-number]/[context-path]/app/index.html.
-
- - Configure the server to serve the files in the
- - For node.js users:
-
-
-
In the angular-phonecat directory, run this command:
-
-./goto_step.sh 0This resets your workspace to step 0 of the tutorial app.
-You must repeat this for every future step in the tutorial and change the number to - the number of the step you are on. This will cause any changes you made within - your working directory to be lost.
- - To see the app running in a browser, do one of the following:
-
-
-
- For node.js users:
-
-
-
- In a separate terminal tab or window, run
-
./scripts/web-server.jsto start the web server.
- - Open a browser window for the app and navigate to http://localhost:8000/app/index.html -
- - In a separate terminal tab or window, run
-
- For other http servers:
-
-
-
- Configure the server to serve the files in the angular-phonecat
-
sandboxdirectory.
- - Navigate in your browser to
-
http://localhost:[port-number]/[context-path]/app/index.html.
-
- - Configure the server to serve the files in the angular-phonecat
-
- - For node.js users:
-
-
-
Open windows command line and run this command (in the angular-phonecat directory):
-
-goto_step.bat 0This resets your workspace to step 0 of the tutorial app.
-You must repeat this for every future step in the tutorial and change the number to - the number of the step you are on. This will cause any changes you made within - your working directory to be lost.
- - To see the app running in a browser, do one of the following:
-
-
-
- For node.js users:
-
-
-
- In a separate terminal tab or window, run
node -scripts\web-server.jsto start the web server.
- - Open a browser window for the app and navigate to http://localhost:8000/app/index.html -
- - In a separate terminal tab or window, run
- For other http servers:
-
-
-
- Configure the server to serve the files in the angular-phonecat
-
sandboxdirectory.
- - Navigate in your browser to
-
http://localhost:[port-number]/[context-path]/app/index.html.
-
- - Configure the server to serve the files in the angular-phonecat
-
- - For node.js users:
-
- - - - -- - - -## What is the code doing? - -* xmlns declaration - - - - This `xmlns` declaration for the `ng` namespace must be specified in all Angular applications in -order to make Angular work with XHTML and IE versions older than 9 (regardless of whether you are -using XHTML or HTML). - -* Angular script tag - - - - -my angular app - - - - - Nothing here yet! - - - - -