aboutsummaryrefslogtreecommitdiffstats
path: root/docs/content/guide/dev_guide.templates.ngdoc
diff options
context:
space:
mode:
Diffstat (limited to 'docs/content/guide/dev_guide.templates.ngdoc')
-rw-r--r--docs/content/guide/dev_guide.templates.ngdoc25
1 files changed, 11 insertions, 14 deletions
diff --git a/docs/content/guide/dev_guide.templates.ngdoc b/docs/content/guide/dev_guide.templates.ngdoc
index 2f62e89a..541b63fd 100644
--- a/docs/content/guide/dev_guide.templates.ngdoc
+++ b/docs/content/guide/dev_guide.templates.ngdoc
@@ -10,31 +10,28 @@ the dynamic view DOM.
These are the types of angular elements and element attributes you can use in a template:
-* {@link dev_guide.compiler.directives Directive} — An attribute that augments an existing DOM
+* {@link api/angular.module.ng.$compileProvider.directive Directive} — An attribute that augments an existing DOM
element.
-* {@link dev_guide.compiler.widgets Widget} — A custom DOM element. An example of a built-in widget
-is {@link api/angular.module.ng.$compileProvider.directive.@ng:repeat ng:repeat}.
-* {@link dev_guide.compiler.markup Markup} — Shorthand for a widget or a directive. The double
+* {@link api/angular.module.ng.$interpolate Markup} — The double
curly brace notation `{{ }}` to bind expressions to elements is built-in angular markup.
* {@link dev_guide.templates.filters Filter} — Formats your data for display to the user.
-* {@link dev_guide.forms Form widgets} — Lets you validate user input.
+* {@link dev_guide.forms Form controls} — Lets you validate user input.
Note: In addition to declaring the elements above in templates, you can also access these elements
in JavaScript code.
The following code snippet shows a simple angular template made up of standard HTML tags along with
-angular {@link dev_guide.compiler.directives directives}, {@link dev_guide.compiler.markup markup},
-and {@link dev_guide.expressions expressions}:
+angular {@link api/angular.module.ng.$compileProvider.directive directives} and {@link dev_guide.expressions expressions}:
<pre>
-<html ng:app>
- <!-- Body tag augmented with ng:controller directive -->
- <body ng:controller="MyController">
- <input ng:model="foo" value="bar">
- <!-- Button tag with ng:click directive, and
+<html ng-app>
+ <!-- Body tag augmented with ng-controller directive -->
+ <body ng-controller="MyController">
+ <input ng-model="foo" value="bar">
+ <!-- Button tag with ng-click directive, and
string expression 'buttonText'
wrapped in "{{ }}" markup -->
- <button ng:click="changeFoo()">{{buttonText}}</button>
+ <button ng-click="changeFoo()">{{buttonText}}</button>
<script src="angular.js">
</body>
</html>
@@ -44,7 +41,7 @@ In a simple single-page app, the template consists of HTML, CSS, and angular dir
in just one HTML file (usually `index.html`). In a more complex app, you can display multiple views
within one main page using "partials", which are segments of template located in separate HTML
files. You "include" the partials in the main page using the {@link api/angular.module.ng.$route
-$route} service in conjunction with the {@link api/angular.module.ng.$compileProvider.directive.ng:view ng:view} directive. An
+$route} service in conjunction with the {@link api/angular.module.ng.$compileProvider.directive.ng-view ng-view} directive. An
example of this technique is shown in the {@link tutorial/ angular tutorial}, in steps seven and
eight.