diff options
| author | Misko Hevery | 2011-01-19 12:16:38 -0800 |
|---|---|---|
| committer | Misko Hevery | 2011-01-24 14:23:51 -0800 |
| commit | 5d0d34ae72a9ca47f1b2dabda60711ad16ee9313 (patch) | |
| tree | 13620adf30e9b7c4939b34032fcf2c64fc5ec6d9 /src | |
| parent | 70c74a9c4e3f1c3fdeb285e765a03bc878d14422 (diff) | |
| download | angular.js-5d0d34ae72a9ca47f1b2dabda60711ad16ee9313.tar.bz2 | |
remove trailing whitespace
Diffstat (limited to 'src')
| -rw-r--r-- | src/Angular.js | 22 |
1 files changed, 11 insertions, 11 deletions
diff --git a/src/Angular.js b/src/Angular.js index 722dc409..30360900 100644 --- a/src/Angular.js +++ b/src/Angular.js @@ -841,20 +841,20 @@ function toKeyValue(obj) { * * ## The angular distribution * Note that there are two versions of the angular javascript file that you can use: - * + * * * `angular.js` - the development version - this file is unobfuscated, uncompressed, and thus * human-readable and useful when developing your angular applications. * * `angular.min.js` - the production version - this is a minified and obfuscated version of * `angular.js`. You want to use this version when you want to load a smaller but functionally * equivalent version of the code in your application. We use the Closure compiler to create this * file. - * - * + * + * * ## Auto-bootstrap with `ng:autobind` * The simplest way to get an <angular/> application up and running is by inserting a script tag in * your HTML file that bootstraps the `http://code.angularjs.org/angular-x.x.x.min.js` code and uses * the special `ng:autobind` attribute, like in this snippet of HTML: - * + * * <pre> <!doctype html> <html xmlns:ng="http://angularjs.org"> @@ -916,11 +916,11 @@ function toKeyValue(obj) { * ## Manual Bootstrap * Using auto-bootstrap is a handy way to start using <angular/>, but advanced users who want more * control over the initialization process might prefer to use manual bootstrap instead. - * + * * The best way to get started with manual bootstraping is to look at the magic behind `ng:autobind` * by writing out each step of the autobind process explicitly. Note that the following code is * equivalent to the code in the previous section. - * + * * <pre> <!doctype html> <html xmlns:ng="http://angularjs.org"> @@ -941,9 +941,9 @@ function toKeyValue(obj) { </body> </html> * </pre> - * + * * This is the sequence that your code should follow if you're bootstrapping angular on your own: - * + * * * After the page is loaded, find the root of the HTML template, which is typically the root of * the document. * * Run the HTML compiler, which converts the templates into an executable, bi-directionally bound @@ -953,7 +953,7 @@ function toKeyValue(obj) { * ##XML Namespace * *IMPORTANT:* When using <angular/> you must declare the ng namespace using the xmlns tag. If you * don't declare the namespace, Internet Explorer does not render widgets properly. - * + * * <pre> * <html xmlns:ng="http://angularjs.org"> * </pre> @@ -964,7 +964,7 @@ function toKeyValue(obj) { * to form the fully qualified widget name. For example, you could map the alias `my` to your domain * and create a widget called my:widget. To create your own namespace, simply add another xmlsn tag * to your page, create an alias, and set it to your unique domain: - * + * * <pre> * <html xmlns:ng="http://angularjs.org" xmlns:my="http://mydomain.com"> * </pre> @@ -973,7 +973,7 @@ function toKeyValue(obj) { * ## Global Object * The <angular/> script creates a single global variable `angular` in the global namespace. All * APIs are bound to fields of this global object. - * + * */ function angularInit(config){ if (config.autobind) { |
