Hopiu/angular.js
1
0
Fork 0
mirror of https://github.com/Hopiu/angular.js.git synced 2026-05-01 03:44:41 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

docs(overview.ngdoc): clarify wording

Browse source
This commit is contained in:
adamshaylor 2013-05-23 11:33:10 -06:00 committed by Pete Bacon Darwin
parent 815053e403
commit bce75d7c68
1 changed files with 14 additions and 14 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

28
docs/content/guide/overview.ngdoc
View file

@ -8,28 +8,28 @@
AngularJS is a structural framework for dynamic web apps. It lets you use HTML as your template AngularJS is a structural framework for dynamic web apps. It lets you use HTML as your template
language and lets you extend HTML's syntax to express your application's components clearly and language and lets you extend HTML's syntax to express your application's components clearly and
succinctly. Out of the box, it eliminates much of the code you currently write through data succinctly. Out of the box, it eliminates much of the code you currently write through data
binding and dependency injection. And it all happens in JavaScript within the browser making it an binding and dependency injection. And it all happens in JavaScript within the browser, making it
ideal partner with any server technology. an ideal partner with any server technology.
Angular is what HTML would have been had it been designed for applications. HTML is a great Angular is what HTML would have been had it been designed for applications. HTML is a great
declarative language for static documents. It does not contain much in the way of creating declarative language for static documents. It does not contain much in the way of creating
applications, and as a result building web applications is an exercise in *what do I have to do, so applications, and as a result building web applications is an exercise in *what do I have to do
that I trick the browser in to doing what I want.* to trick the browser into doing what I want.*
The impedance mismatch between dynamic applications and static documents is often solved as: The impedance mismatch between dynamic applications and static documents is often solved with:
* **library** - a collection of functions which are useful when writing web apps. Your code is * **a library** - a collection of functions which are useful when writing web apps. Your code is
in charge and it calls into the library when it sees fit. E.g., `jQuery`. in charge and it calls into the library when it sees fit. E.g., `jQuery`.
* **frameworks** - a particular implementation of a web application, where your code fills in * **frameworks** - a particular implementation of a web application, where your code fills in
the details. The framework is in charge and it calls into your code when it needs something the details. The framework is in charge and it calls into your code when it needs something
app specific. E.g., `knockout`, `sproutcore`, etc. app specific. E.g., `knockout`, `ember`, etc.
Angular takes another approach. It attempts to minimize the impedance mismatch between document Angular takes another approach. It attempts to minimize the impedance mismatch between document
centric HTML and what an application needs by creating new HTML constructs. Angular teaches the centric HTML and what an application needs by creating new HTML constructs. Angular teaches the
browser new syntax through a construct we call directives. Examples include: browser new syntax through a construct we call directives. Examples include:
* Data binding as in `{{}}`. * Data binding, as in `{{}}`.
* DOM control structures for repeating/hiding DOM fragments. * DOM control structures for repeating/hiding DOM fragments.
* Support for forms and form validation. * Support for forms and form validation.
* Attaching code-behind to DOM elements. * Attaching code-behind to DOM elements.
@ -37,13 +37,13 @@ browser new syntax through a construct we call directives. Examples include:
## End-to-end solution ## A complete client-side solution
Angular tries to be an end-to-end solution, when building a web application. This means it is Angular is not a single piece in the overall puzzle of building the client-side of a web
not a single piece in an overall puzzle of building a web application, but an end-to-end solution. application. It handles all of the DOM and AJAX glue code you once wrote by hand and puts it in a
This makes Angular opinionated about how a CRUD application should be built. But while it is well-defined structure. This makes Angular opinionated about how a CRUD application should be
opinionated, it also tries to make sure that its opinion is just a starting point, which you can built. But while it is opinionated, it also tries to make sure that its opinion is just a
easily change. Angular comes with the following out-of-the-box: starting point you can easily change. Angular comes with the following out-of-the-box:
* Everything you need to build a CRUD app in a cohesive set: data-binding, basic templating * Everything you need to build a CRUD app in a cohesive set: data-binding, basic templating
directives, form validation, routing, deep-linking, reusable components, dependency injection. directives, form validation, routing, deep-linking, reusable components, dependency injection.