From 139e1b09a94f60b351cc961d8bfd882c0b8ba594 Mon Sep 17 00:00:00 2001 From: Vojta Jina Date: Thu, 23 Feb 2012 19:47:58 -0800 Subject: docs(forms): Update API docs for forms - API forms (ng:model + controller, form + controller) - fix some broken links - ng:change, ng:model-instant --- docs/content/guide/dev_guide.bootstrap.manual_bootstrap.ngdoc | 2 +- .../content/guide/dev_guide.compiler.understanding_compiler.ngdoc | 8 ++++---- docs/content/guide/dev_guide.scopes.internals.ngdoc | 8 ++++---- 3 files changed, 9 insertions(+), 9 deletions(-) (limited to 'docs/content/guide') diff --git a/docs/content/guide/dev_guide.bootstrap.manual_bootstrap.ngdoc b/docs/content/guide/dev_guide.bootstrap.manual_bootstrap.ngdoc index 1c934745..09c3a07b 100644 --- a/docs/content/guide/dev_guide.bootstrap.manual_bootstrap.ngdoc +++ b/docs/content/guide/dev_guide.bootstrap.manual_bootstrap.ngdoc @@ -7,7 +7,7 @@ angular, but advanced users who want more control over the initialization proces the manual bootstrapping method instead. The best way to get started with manual bootstrapping is to look at the what happens when you use -{@link api/angular.directive.ng:app ng:app}, by showing each step of the process +{@link api/angular.module.ng.$compileProvider.directive.ng:app ng:app}, by showing each step of the process explicitly. 
diff --git a/docs/content/guide/dev_guide.compiler.understanding_compiler.ngdoc b/docs/content/guide/dev_guide.compiler.understanding_compiler.ngdoc
index e802aee6..8d31b44a 100644
--- a/docs/content/guide/dev_guide.compiler.understanding_compiler.ngdoc
+++ b/docs/content/guide/dev_guide.compiler.understanding_compiler.ngdoc
@@ -2,8 +2,8 @@
 @name Developer Guide: Angular HTML Compiler: Understanding How the Compiler Works
 @description
 
-The {@link angular.module.ng.$compile compiler} is responsible for applying
-{@link angular.module.ng.$compileProvider.directive directives} to the HTML. The directives
+The {@link api/angular.module.ng.$compile compiler} is responsible for applying
+{@link api/angular.module.ng.$compileProvider.directive directives} to the HTML. The directives
 extend the behavior of HTML elements and can effect the DOM structure, presentation, and behavior.
 This allows Angular to teach the browser new tricks.
 
@@ -13,7 +13,7 @@ function. The result of the compilation process is a linking function. The linki
 can be used on the template clones to quickly bind the directives with the scope.
 
 The result of the compilation process is a live view. We say 'live' since any changes to the
-model attached to the {@link angular.module.ng.$rootScope.Scope scope} are reflected in the view,
+model attached to the {@link api/angular.module.ng.$rootScope.Scope scope} are reflected in the view,
 and any changes in the view are reflected in the scope. This makes the scope the 'single source of
 truth'.
 
@@ -21,7 +21,7 @@ Since directives allow attachment of behavior to the HTML, the angular philosoph
 HTML as Domain Specific Language (DSL) when building an application. For example it may be useful
 to declare `TabPanel` directive, or `KeyboardShortcut` directive when for an application.
 
-For details on how directives are created see {@link angular.module.ng.$compileProvider.directive
+For details on how directives are created see {@link api/angular.module.ng.$compileProvider.directive
 directives}
 
 ## Related Topics
diff --git a/docs/content/guide/dev_guide.scopes.internals.ngdoc b/docs/content/guide/dev_guide.scopes.internals.ngdoc
index 7cfac09a..a57146a0 100644
--- a/docs/content/guide/dev_guide.scopes.internals.ngdoc
+++ b/docs/content/guide/dev_guide.scopes.internals.ngdoc
@@ -46,7 +46,7 @@ reside on a child scope, if a property read does not find the property on a scop
 recursively check the parent scope, grandparent scope, etc. all the way to the root scope before
 defaulting to undefined.
 
-{@link angular.module.ng.$compileProvider.directive directives} associated with elements
+{@link api/angular.module.ng.$compileProvider.directive directives} associated with elements
 (ng:controller, ng:repeat, ng:include, etc.) create new child scopes that inherit properties from
 the current parent scope. Any code in Angular is free to create a new scope. Whether or not your
 code does so is an implementation detail of the directive, that is, you can decide when or if this
@@ -117,9 +117,9 @@ scopes come into play throughout and get a sense of their interactions.
 1. At application compile time, a root scope is created and is attached to the root `` DOM
 element.
 2. During the compilation phase, the {@link dev_guide.compiler compiler} matches {@link
-angular.module.ng.$compileProvider.directive directives} against the DOM template. The directives
+api/angular.module.ng.$compileProvider.directive directives} against the DOM template. The directives
 usually fall into one of two categories:
-   - Observing {@link angular.module.ng.$compileProvider.directive directives}, such as double-curly
+   - Observing {@link api/angular.module.ng.$compileProvider.directive directives}, such as double-curly
     expressions `{{expression}}`, register listeners using the {@link
     api/angular.module.ng.$rootScope.Scope#$watch $watch()} method. This type of directive needs to
     be notified whenever the expression changes so that it can update the view.
@@ -133,7 +133,7 @@ api/angular.module.ng.$rootScope.Scope#$apply $apply()} method so that all liste
 
 
 ### Directives that create scopes
-In most cases, {@link angular.module.ng.$compileProvider.directive directives} and scopes interact but do not create new
+In most cases, {@link api/angular.module.ng.$compileProvider.directive directives} and scopes interact but do not create new
 instances of scope. However, some directives, such as {@link api/angular.module.ng.$compileProvider.directive.ng:controller
 ng:controller} and {@link api/angular.module.ng.$compileProvider.directive.@ng:repeat ng:repeat}, create new child scopes using
 the {@link api/angular.module.ng.$rootScope.Scope#$new $new()} method and then attach the child scope to the
-- 
cgit v1.2.3