diff options
| author | Igor Minar | 2011-06-06 22:02:30 -0700 |
|---|---|---|
| committer | Igor Minar | 2011-06-06 23:10:30 -0700 |
| commit | c35b0a7907de1535269876668c345ce944681804 (patch) | |
| tree | a3ba548369ca65db790809197196ae946cc93a18 /docs/content/tutorial/step_02.ngdoc | |
| parent | 805bb5bb6e5842a5760976a446074d553609f5b6 (diff) | |
| download | angular.js-c35b0a7907de1535269876668c345ce944681804.tar.bz2 | |
yet another docs batch
Diffstat (limited to 'docs/content/tutorial/step_02.ngdoc')
| -rw-r--r--[-rwxr-xr-x] | docs/content/tutorial/step_02.ngdoc | 30 |
1 files changed, 14 insertions, 16 deletions
diff --git a/docs/content/tutorial/step_02.ngdoc b/docs/content/tutorial/step_02.ngdoc index 10721679..1715990b 100755..100644 --- a/docs/content/tutorial/step_02.ngdoc +++ b/docs/content/tutorial/step_02.ngdoc @@ -66,15 +66,15 @@ widget} and two {@link guide/dev_guide.expressions angular expressions} enclosed `{{phone.name}}` and `{{phone.snippet}}`: - * The `ng:repeat="phone in phones"` statement in the `<li>` tag is an angular repeater. It -tells angular to create a `<li>` element for each phone in the phones list, using the first `<li>` -tag as the template. +* The `ng:repeat="phone in phones"` statement in the `<li>` tag is an angular repeater. It tells +angular to create a `<li>` element for each phone in the phones list, using the first `<li>` tag as +the template. <img src="img/tutorial/tutorial_02_final.png"> - * The curly braces around `phone.name` and `phone.snippet` are an example of {@link +* The curly braces around `phone.name` and `phone.snippet` are an example of {@link guide/dev_guide.compiler.markup angular markup}. The curly markup is shorthand for the angular directive {@link api/angular.directive.ng:bind ng:bind}. The `ng:bind` directives indicate to angular that these are template binding points. Binding points are locations in the template where @@ -117,20 +117,18 @@ the model and the view. Note in the following how we connected the dots between data, and logic components: - * The name of our controller function (in the JavaScript file `controllers.js`) matches the -{@link api/angular.directive.@ng:controller ng:controller} directive in the `<body>` tag -(`PhoneListCtrl`). - * We instantiated our data within the scope of our controller function, and our template -binding points are located within the block bounded by the `<body ng:controller="PhoneListCtrl">` -tag. +* The name of our controller function (in the JavaScript file `controllers.js`) matches the {@link +api/angular.directive.ng:controller ng:controller} directive in the `<body>` tag (`PhoneListCtrl`). +* We instantiated our data within the scope of our controller function, and our template binding +points are located within the block bounded by the `<body ng:controller="PhoneListCtrl">` tag. - Angular scopes are a crucial concept in angular; you can think of scopes as the glue that makes -the template, model and controller all work together. Angular uses scopes, along with the -information contained in the template, data model, and controller, to keep the model and view -separated but in sync. Any changes to the model are reflected in the view; any changes that occur -in the view are reflected in the model. To learn more about angular scopes, see the {@link -api/angular.scope angular scope documentation}. +Angular scopes are a crucial concept in angular; you can think of scopes as the glue that makes the +template, model and controller all work together. Angular uses scopes, along with the information +contained in the template, data model, and controller, to keep the model and view separated but in +sync. Any changes to the model are reflected in the view; any changes that occur in the view are +reflected in the model. To learn more about angular scopes, see the {@link api/angular.scope +angular scope documentation}. |