kylefang/angular.js
1
0
Fork 0
mirror of https://github.com/zhigang1992/angular.js.git synced 2026-04-23 11:37:38 +08:00
Code Issues Packages Projects Releases Wiki Activity

doc(guide): clean up broken links

Browse Source
This commit is contained in:
Misko Hevery
2012-05-24 14:49:47 -07:00
parent f0be543614
commit 0532aabcf9
24 changed files with 53 additions and 53 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
docs/content/cookbook/form.ngdoc
View File

@@ -108,8 +108,7 @@ allow a user to enter data.
is going on.
* The {@link api/angular.module.ng.$compileProvider.directive.input input directives} simply refer
to the model and are data-bound.
* The inputs {@link guide/dev_guide.forms validate}. (Try leaving them blank or entering non digits
in the zip field)
* The inputs validate. (Try leaving them blank or entering non digits in the zip field)
* In your application you can simply read from or write to the model and the form will be updated.
* By clicking the 'add' link you are adding new items into the `user.contacts` array which are then
reflected in the view.

6
docs/content/guide/bootstrap.ngdoc
View File

@@ -49,14 +49,14 @@ initialization.
# Automatic Initialization
Angular initializes automatically upon `DOMContentLoaded` event, at which point angular looks for
the {@link api/angular.module.ng.$compileProvider.directive.ng:app `ng-app`} directive which
the {@link api/angular.module.ng.$compileProvider.directive.ngApp `ng-app`} directive which
designates your application root. If {@link
api/angular.module.ng.$compileProvider.directive.ng:app `ng-app`} directive is found then Angular
will:
* load the {@link guide/module module} associated with the directive.
* create the application {@link api/angular.module.AUTO.$injector injector}
* compile the DOM treating the {@link api/angular.module.ng.$compileProvider.directive.ng:app
* compile the DOM treating the {@link api/angular.module.ng.$compileProvider.directive.ngApp
`ng-app`} directive as the root of the compilation. This allows you to tell it to treat only a
portion of the DOM as an Angular application.
@@ -82,7 +82,7 @@ or the need to perform an operation before the Angular compiles a page.
Here is an example of manually initializing Angular. The example is equivalent to using the {@link
api/angular.module.ng.$compileProvider.directive.ng:app ng:app} directive.
api/angular.module.ng.$compileProvider.directive.ngApp ng-app} directive.
<pre>
<!doctype html>

4
docs/content/guide/compiler.ngdoc
View File

@@ -39,7 +39,7 @@ process happens into two phases.
scope model are reflected in the view, and any user interactions with the view are reflected
in the scope model. Making the scope model a single source of truth.
Some directives such {@link api/angular.module.ng.$compileProvider.directive.ng:repeat
Some directives such {@link api/angular.module.ng.$compileProvider.directive.ngRepeat
`ng-repeat`} clone DOM elements once for each item in collection. Having a compile and link phase
improves performance since the cloned template only needs to be compiled once, and then linked
once for each clone instance.
@@ -50,7 +50,7 @@ once for each clone instance.
Directive is a behavior which should be triggered when specific HTML constructs are encountered in
compilation process. The directives can be placed in element names, attributes, class names, as
well as comments. Here are some equivalent examples of invoking {@link
api/angular.module.ng.$compileProvider.directive.ng:bind `ng-bind`} directive.
api/angular.module.ng.$compileProvider.directive.ngBind `ng-bind`} directive.
<pre>
<span ng-bind="exp"></span>

2
docs/content/guide/dev_guide.mvc.understanding_controller.ngdoc
View File

@@ -58,7 +58,7 @@ Putting any presentation logic into controllers significantly affects testabilit
logic. Angular offers {@link dev_guide.templates.databinding} for automatic DOM manipulation. If
you have to perform your own manual DOM manipulation, encapsulate the presentation logic in
{@link guide/directive directives}.
- Input formatting — Use {@link dev_guide.forms angular form controls} instead.
- Input formatting — Use {@link forms angular form controls} instead.
- Output filtering — Use {@link dev_guide.templates.filters angular filters} instead.
- Run stateless or stateful code shared across controllers — Use {@link dev_guide.services angular
services} instead.

2
docs/content/guide/dev_guide.mvc.understanding_model.ngdoc
View File

@@ -26,7 +26,7 @@ occurs in controllers:
$scope.foo = 'bar';
}
* Use an {@link dev_guide.expressions angular expression} with an assignment operator in templates:
* Use an {@link expression angular expression} with an assignment operator in templates:
<button ng-click="{{foos='ball'}}">Click me</button>

2
docs/content/guide/dev_guide.services.creating_services.ngdoc
View File

@@ -49,7 +49,7 @@ 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 di.understanding_di Read more} about the DI
as arguments of the factory function. {@link di Read more} about the DI
in Angular and the use of array notation and $inject property to make DI annotation
minification-proof.

2
docs/content/guide/dev_guide.templates.css-styling.ngdoc
View File

@@ -20,4 +20,4 @@ Angular sets these CSS classes. It is up to your application to provide useful s
## Related Topics
* {@link dev_guide.templates Angular Templates}
* {@link dev_guide.forms Angular Forms}
* {@link forms Angular Forms}

2
docs/content/guide/dev_guide.templates.filters.creating_filters.ngdoc
View File

@@ -59,7 +59,7 @@ text upper-case and assigns color.
## Related Topics
* {@link dev_guide.templates.filters Understanding Angular Filters}
* {@link dev_guide.compiler Angular HTML Compiler}
* {@link compiler Angular HTML Compiler}
## Related API

6
docs/content/guide/dev_guide.templates.ngdoc
View File

@@ -15,14 +15,14 @@ These are the types of angular elements and element attributes you can use in a
* {@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 controls} — Lets you validate user input.
* {@link 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 guide/directive directives} and curly-brace bindings
with {@link dev_guide.expressions expressions}:
with {@link expression expressions}:
<pre>
<html ng-app>
@@ -50,7 +50,7 @@ eight.
## Related Topics
* {@link dev_guide.templates.filters Angular Filters}
* {@link dev_guide.forms Angular Forms}
* {@link forms Angular Forms}
## Related API

2
docs/content/guide/directive.ngdoc
View File

@@ -1,5 +1,5 @@
@ngdoc overview
@name directive
@name Directives
@description
Directives are a way to teach HTML new tricks. During DOM compilation directives are matched

2
docs/content/guide/index.ngdoc
View File

@@ -30,7 +30,7 @@ of the following documents before returning here to the Developer Guide:
## {@link dev_guide.templates Angular Templates}
* {@link dev_guide.templates.filters Understanding Angular Filters}
* {@link dev_guide.forms Understanding Angular Forms}
* {@link forms Understanding Angular Forms}
## {@link dev_guide.services Angular Services}

17
docs/content/guide/scope.ngdoc
View File

@@ -164,7 +164,7 @@ where the `department` property is defined.
Scopes are attached to the DOM as `$scope` data property, and can be retrieved for debugging
purposes. (It is unlikely that one would need to retrieve scopes in this way inside the
application.) The location where the root scope is attached to the DOM is defined by the location
of {@link api/angular.module.ng.$compileProvider.directive.ng:app `ng-app`} directive. Typically
of {@link api/angular.module.ng.$compileProvider.directive.ngApp `ng-app`} directive. Typically
`ng-app` is placed an the `<html>` element, but it can be placed on other elements as well, if,
for example, only a portion of the view needs to be controlled by angular.
@@ -228,7 +228,7 @@ modifications the execution has to enter the Angular execution context using the
api/angular.module.ng.$rootScope.Scope#$apply `$apply`} method. Only model modifications which
execute inside the `$apply` method will be properly accounted for by Angular. For example if a
directive listens on DOM events, such as {@link
api/angular.module.ng.$compileProvider.directive.ng:click `ng-click`} it must evaluate the
api/angular.module.ng.$compileProvider.directive.ngClick `ng-click`} it must evaluate the
expression inside the `$apply` method.
After evaluating the expression `$apply` method performs a {@link
@@ -287,8 +287,8 @@ usually fall into one of two categories:
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.
- Listener directives, such as {@link api/angular.module.ng.$compileProvider.directive.ng:click
ng:click}, register a listener with the DOM. When the DOM listener fires, the directive
- Listener directives, such as {@link api/angular.module.ng.$compileProvider.directive.ngClick
ng-click}, register a listener with the DOM. When the DOM listener fires, the directive
executes the associated expression and updates the view using the {@link
api/angular.module.ng.$rootScope.Scope#$apply $apply()} method.
@@ -301,8 +301,8 @@ correctly.
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
api/angular.module.ng.$compileProvider.directive.ngController ng-controller} and {@link
api/angular.module.ng.$compileProvider.directive.ngRepeat ng-repeat}, create new child scopes
and attach the child scope to the corresponding DOM element. You can retrieve a scope for any DOM
element by using an `angular.element(aDomElement).scope()` method call.
@@ -311,14 +311,15 @@ element by using an `angular.element(aDomElement).scope()` method call.
Scopes and controllers interact with each other in the following situations:
- Controllers use scopes to expose controller methods to templates (see {@link
api/angular.module.ng.$compileProvider.directive.ng:controller ng:controller}).
api/angular.module.ng.$compileProvider.directive.ngController ng-controller}).
- Controllers define methods (behavior) that can mutate the model (properties on the scope).
- Controllers may register {@link api/angular.module.ng.$rootScope.Scope#$watch watches} on
the model. These watches execute immediately after the controller behavior executes.
See the {@link controller controller documentation} for more information.
See the {@link api/angular.module.ng.$compileProvider.directive.ngController ng-controller} for more
information.
### Scope `$watch` Performance Considerations

4
docs/content/tutorial/step_00.ngdoc
View File

@@ -200,7 +200,7 @@ being the element on which the `ngApp` directive was defined.
binding will result in efficient continuous updates whenever the result of the expression
evaluation changes.
{@link guide/dev_guide.expressions Angular expression} is a JavaScript-like code snippet that is
{@link guide/expression Angular expression} is a JavaScript-like code snippet that is
evaluated by Angular in the context of the current model scope, rather than within the scope of
the global context (`window`).
@@ -211,7 +211,7 @@ being the element on which the `ngApp` directive was defined.
Bootstrapping AngularJS apps automatically using the `ngApp` directive is very easy and suitable
for most cases. In advanced cases, such as when using script loaders, you can use
{@link guide/dev_guide.bootstrap.manual_bootstrap imperative / manual way} to bootstrap the app.
{@link guide/bootstrap imperative / manual way} to bootstrap the app.
There are 3 important things that happen during the app bootstrap:

2
docs/content/tutorial/step_02.ngdoc
View File

@@ -53,7 +53,7 @@ __`app/index.html`:__
We replaced the hard-coded phone list with the
{@link api/angular.module.ng.$compileProvider.directive.ngRepeat ngRepeat directive} and two
{@link guide/dev_guide.expressions Angular expressions} enclosed in curly braces:
{@link guide/expression Angular expressions} enclosed in curly braces:
`{{phone.name}}` and `{{phone.snippet}}`:
* The `ng-repeat="phone in phones"` statement in the `<li>` tag is an Angular repeater. The

4
docs/content/tutorial/step_05.ngdoc
View File

@@ -7,7 +7,7 @@
Enough of building an app with three phones in a hard-coded dataset! Let's fetch a larger dataset
from our server using one of angular's built-in {@link api/angular.module.ng services} called {@link
api/angular.module.ng.$http $http}. We will use angular's {@link guide/dev_guide.di dependency
api/angular.module.ng.$http $http}. We will use angular's {@link guide/di dependency
injection (DI)} to provide the service to the `PhoneListCtrl` controller.
@@ -47,7 +47,7 @@ request to your web server to fetch the data in the `app/phones/phones.json` fil
one of several built-in {@link api/angular.module.ng angular services} that handle common operations
in web apps. Angular injects these services for you where you need them.
Services are managed by angular's {@link guide/dev_guide.di DI subsystem}. Dependency injection
Services are managed by angular's {@link guide/di DI subsystem}. Dependency injection
helps to make your web apps both well-structured (e.g., separate components for presentation, data,
and control) and loosely coupled (dependencies between components are not resolved by the
components themselves, but by the DI subsystem).