knowhow-server
Version:
A personal workflow engine that can manage and use any network connected host
110 lines (109 loc) • 6.13 kB
HTML
<a href="http://github.com/angular/angular.js/edit/master/docs/content/guide/bootstrap.ngdoc" class="improve-docs btn btn-primary"><i class="icon-edit"> </i> Improve this doc</a><h1><code ng:non-bindable=""></code>
<div><span class="hint"></span>
</div>
</h1>
<div><div class="developer-guide-page developer-guide-bootstrap-page"><h2 id="overview">Overview</h2>
<p>This page explains the Angular initialization process and how you can manually initialize Angular
if necessary.</p>
<h3 id="overview_angular-tag">Angular <code><script></code> Tag</h3>
<p>This example shows the recommended path for integrating Angular with what we call automatic
initialization.</p>
<pre class="prettyprint linenums">
<!doctype html>
<html xmlns:ng="http://angularjs.org" ng-app>
<body>
...
<script src="angular.js">
</body>
</html>
</pre>
<ul>
<li>Place the <code>script</code> tag at the bottom of the page. Placing script tags at the end of the page
improves app load time because the HTML loading is not blocked by loading of the <code>angular.js</code>
script. You can get the latest bits from <a href="http://code.angularjs.org"><a href="http://code.angularjs.org">http://code.angularjs.org</a></a>. Please don't link
your production code to this URL, as it will expose a security hole on your site. For
experimental development linking to our site is fine.<ul>
<li>Choose: <code>angular-[version].js</code> for a human-readable file, suitable for development and
debugging.</li>
<li>Choose: <code>angular-[version].min.js</code> for a compressed and obfuscated file, suitable for use in
production.</li>
</ul>
</li>
<li><p>Place <code>ng-app</code> to the root of your application, typically on the <code><html></code> tag if you want
angular to auto-bootstrap your application.</p>
<pre><code><html ng-app></code></pre>
</li>
<li><p>If IE7 support is required add <code>id="ng-app"</code></p>
<pre><code><html ng-app id="ng-app"></code></pre>
</li>
<li><p>If you choose to use the old style directive syntax <code>ng:</code> then include xml-namespace in <code>html</code>
to make IE happy. (This is here for historical reasons, and we no longer recommend use of
<code>ng:</code>.)</p>
<pre><code><html xmlns:ng="http://angularjs.org"></code></pre>
</li>
</ul>
<h3 id="overview_automatic-initialization">Automatic Initialization</h3>
<p><img class="pull-right" style="padding-left: 3em;" src="img/guide/concepts-startup.png"></p>
<p>Angular initializes automatically upon <code>DOMContentLoaded</code> event or when the <code>angular.js</code> script is
evaluated if at that time <code>document.readyState</code> is set to <code>'complete'</code>. At this point Angular looks
for the <a href="api/ng.directive:ngApp"><code><code>ng-app</code></code></a> directive which designates your application root.
If the <a href="api/ng.directive:ngApp"><code><code>ng-app</code></code></a> directive is found then Angular will:</p>
<ul>
<li>load the <a href="guide/module">module</a> associated with the directive.</li>
<li>create the application <a href="api/AUTO.$injector"><code>injector</code></a></li>
<li>compile the DOM treating the <a href="api/ng.directive:ngApp"><code><code>ng-app</code></code></a> 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.</li>
</ul>
<pre class="prettyprint linenums">
<!doctype html>
<html ng-app="optionalModuleName">
<body>
I can add: {{ 1+2 }}.
<script src="angular.js"></script>
</body>
</html>
</pre>
<h3 id="overview_manual-initialization">Manual Initialization</h3>
<p>If you need to have more control over the initialization process, you can use a manual
bootstrapping method instead. Examples of when you'd need to do this include using script loaders
or the need to perform an operation before Angular compiles a page.</p>
<p>Here is an example of manually initializing Angular:</p>
<pre class="prettyprint linenums">
<!doctype html>
<html xmlns:ng="http://angularjs.org">
<body>
Hello {{'World'}}!
<script src="http://code.angularjs.org/angular.js"></script>
<script>
angular.element(document).ready(function() {
angular.module('myApp', []);
angular.bootstrap(document, ['myApp']);
});
</script>
</body>
</html>
</pre>
<p>Note that we have provided the name of our application module to be loaded into the injector as the second
parameter of the <a href="api/angular.bootstrap"><code>api/angular.bootstrap</code></a> function. Notice that <code>angular.bootstrap</code> will not create modules
on the fly. You must create any custom <a href="guide/module">modules</a> before you pass them as a parameter. </p>
<p>This is the sequence that your code should follow:</p>
<ol>
<li><p>After the page and all of the code is loaded, find the root element of your AngularJS
application, which is typically the root of the document.</p>
</li>
<li><p>Call <a href="api/angular.bootstrap"><code>api/angular.bootstrap</code></a> to <a href="guide/compiler">compile</a> the element into an
executable, bi-directionally bound application.</p>
</li>
</ol>
<h3 id="overview_deferred-bootstrap">Deferred Bootstrap</h3>
<p>This feature enables tools like Batarang and test runners to
hook into angular's bootstrap process and sneak in more modules
into the DI registry which can replace or augment DI services for
the purpose of instrumentation or mocking out heavy dependencies.</p>
<p>If <code>window.name</code> contains prefix <code>NG_DEFER_BOOTSTRAP!</code> when
<a href="api/angular.bootstrap"><code>api/angular.bootstrap</code></a> is called, the bootstrap process will be paused
until <code>angular.resumeBootstrap()</code> is called.</p>
<p><code>angular.resumeBootstrap()</code> takes an optional array of modules that
should be added to the original list of modules that the app was
about to be bootstrapped with.</p>
</div></div>