(public).sospep.systems ~ view step ~ step-002-templates-dynamic

<h1 style="text-align: center;">step-002 -&nbsp;angularjs template</h1>
Now it's time to make the web page dynamic &mdash; with AngularJS.
We'll also add a test that verifies the code for the controller we are going to add.
&nbsp;use a little Angular and JavaScript to add model, view, and controller components to our app.
<ol>
<li>[00:00] NEW step IN</li>
<ol>
<li>x] git checkout -f step-2 - resets app code for this example</li>
<li>*] index page now displays a list with 3 phones showing</li>
</ol>
<li>[00:00] NEW step IN review differences</li>
<ol>
<li>] git diff <a href="https://github.com/angular/angular-phonecat/compare/step-1...step-2" target="_blank">https://github.com/angular/angular-phonecat/compare/step-1...step-2</a>&nbsp;to review exactly what has changed in this branch(step-2) VS the previous branch</li>
<li>x] you can see&nbsp;3 files changed, 1 new file&nbsp;has been added,&nbsp;&nbsp;</li>
<ol>
<li>]&nbsp;controllerjs, index.html, controllerSpecjs ( tests )</li>
</ol>
<li>x] changes&nbsp;to "index.html" include</li>
<ol>
<li>] add script controllerjs</li>
<li>] change directive on html from "ng-app" to "ng-app=phonecat-app"</li>
<li>] add directive to "body element"&nbsp;= ng-controller=phonelist</li>
<li>] add directive to li = ng-repeat =phone in phones</li>
<li>] replace static li items with li template {{ }}</li>
</ol>
<li>x] changes to test/unit/controllersSpecjs include&nbsp; ( whooahh )</li>
<ol>
<li>] add describe phonecat controllers</li>
<li>] add describe phonelistControl</li>
<li>] beforeEach module</li>
<li>] it should ...</li>
</ol></ol>
<li>[00:00] NEW step IN</li>
<ol>
<li>]</li>
</ol></ol>
&nbsp;
<hr />
<h1 style="text-align: center;">&nbsp;need to know</h1>
<ol>
<li>view and template</li>
<ol>
<li>] the view is a projection of the model through the HTML template. This means that whenever the model changes, Angular refreshes the appropriate binding points, which updates the view</li>
<ol>
<li>We replaced the hard-coded phone list with the <a href="https://docs.angularjs.org/api/ng/directive/ngRepeat" target="_blank">ngRepeat directive</a> and two <a href="https://docs.angularjs.org/guide/expression" target="_blank">Angular expressions</a>:</li>
</ol>
<li>] added a new directive, called <code>ng-controller</code>, which attaches a <code>PhoneListCtrl</code> controller to the &lt;body&gt; tag. At this point:</li>
<ol>
<li>The expressions in curly braces (<code>{{phone.name}}</code> and <code>{{phone.snippet}}</code> denote bindings, which are referring to our application model, which is set up in our <code>PhoneListCtrl</code> controller.</li>
</ol></ol>
<li>model and controller</li>
<ol>
<li>] the data model - an array of phones in object literal notation - is now instantiated within the <code>PhoneListCtrl</code> controller. The controller is simply a constructor function that takes a <code>$scope</code> parameter:</li>
<li>] Here we declared a controller called <code>PhoneListCtrl</code> and registered it in an AngularJS module, <code>phonecatApp</code>. Notice that our <code>ng-app</code> directive (on the <code>&lt;html&gt;</code> tag) now specifies the <code>phonecatApp</code> module name as the module to load when bootstrapping the Angular application.</li>
<li>] Although the controller is not yet doing very much, it plays a crucial role. By providing context for our data model, the controller allows us to establish data-binding between the model and the view. We connected the dots between the presentation, data, and logic components as follows:</li>
<ol>
<li>] The <a href="https://docs.angularjs.org/api/ng/directive/ngController" target="_blank">ngController</a> directive, located on the <code>&lt;body&gt;</code> tag, references the name of our controller, <code>PhoneListCtrl</code> (located in the JavaScript file <code>controllers.js</code>).</li>
<li>] The <code>PhoneListCtrl</code> controller attaches the phone data to the <code>$scope</code> that was injected into our controller function. This scope is a prototypical descendant of the root scope that was created when the application was defined. This controller scope is available to all bindings located within the <code>&lt;bodyng-controller="PhoneListCtrl"&gt;</code> tag.</li>
</ol></ol>
<li>scope</li>
<ol>
<li>] The concept of a scope in Angular is crucial. A scope can be seen as the glue which allows the template, model and controller to work together. Angular uses scopes, along with the information contained in the template, data model, and controller, to keep models and views separate, but in sync. Any changes made to the model are reflected in the view; any changes that occur in the view are reflected in the model. To learn more about Angular scopes, see the <a href="https://docs.angularjs.org/api/ng/type/$rootScope.Scope" target="_blank">angular scope documentation</a></li>
</ol>
<li>tests</li>
<ol>
<li>] The "Angular way" of separating controller from the view, makes it easy to test code as it is being developed. If our controller is available on the global namespace then we could simply instantiate it with a mock <code>scope</code> object:</li>
<li>] see example test</li>
<li>] The test instantiates <code>PhoneListCtrl</code> and verifies that the phones array property on the scope contains three records. This example demonstrates how easy it is to create a unit test for code in Angular. Since testing is such a critical part of software development, we make it easy to create tests in Angular so that developers are encouraged to write them.</li>
</ol>
<li>testing non global controllers</li>
<ol>
<li>] In practice, you will not want to have your controller functions in the global namespace. Instead, you can see that we have registered it via an anonymous constructor function on the <code>phonecatApp</code> module.</li>
<li>] In this case Angular provides a service, <code>$controller</code>, which will retrieve your controller by name. Here is the same test using <code>$controller</code>:</li>
<li>] example test</li>
<li>] Before each test we tell Angular to load the <code>phonecatApp</code> module.</li>
<li>] We ask Angular to <code>inject</code> the <code>$controller</code> service into our test function</li>
<li>] We use <code>$controller</code> to create an instance of the <code>PhoneListCtrl</code></li>
<li>] With this instance, we verify that the phones array property on the scope contains three records.</li>
</ol>
<li>writing and running tests</li>
<ol>
<li>] Angular developers prefer the syntax of Jasmine's Behavior-driven Development (BDD) framework when writing tests. Although Angular does not require you to use Jasmine, we wrote all of the tests in this tutorial in Jasmine v1.3. You can learn about Jasmine on the <a href="http://jasmine.github.io/" target="_blank">Jasmine home page</a> and at the <a href="http://jasmine.github.io/1.3/introduction.html" target="_blank">Jasmine docs</a>.</li>
<li>] The angular-seed project is pre-configured to run unit tests using <a href="http://karma-runner.github.io/" target="_blank">Karma</a> but you will need to ensure that Karma and its necessary plugins are installed. You can do this by running <code>npm install</code>. To run the tests, and then watch the files for changes: <code>npm test</code></li>
<li>] To rerun the tests, just change any of the source or test .js files. Karma will notice the change and will rerun the tests for you. Now isn't that sweet</li>
<li>] Make sure you don't minimize the browser that Karma opened. On some OS, memory assigned to a minimized browser is limited, which results in your karma tests running extremely slow</li>
</ol>
<li>experiments</li>
<ol>
<li>x] add another "binding" to index -</li>
<ol>
<li>x] ex total number of phones - display</li>
</ol>
<li>x] Create a new model property in the controllerjs and bind to it from the template. For example:</li>
<ol>
<li>x] $scope.Name = "World"</li>
</ol>
<li>x] add another binding</li>
<ol>
<li>x] &lt;p&gt; hello {{name}}&lt;/p&gt;</li>
<li>x] man. test in browser = OK</li>
</ol>
<li>x] update the unit test in controllersSpec.js</li>
<ol>
<li>x] expect(scope.name).toBe('World');</li>
<li>x] man. test in browser = OK </li>
</ol>
<li>x] Create a repeater in <code>index.html</code> that constructs a simple table</li>
<ol>
<li>x] OK</li>
</ol>
<li>x] Now, make the list 1-based by incrementing <code>i</code> by one in the binding</li>
<ol>
<li>x] OK </li>
</ol>
<li>x] Extra points: try and make an 8x8 table using an additional <code>ng-repeat</code>.</li>
<ol>
<li>x] sort of, using 2 repeaters, #'s dont jive</li>
</ol>
<li>x] make the unit test fail</li>
<ol>
<li>x] OK </li>
<li>?] are the tests running continuosly? </li>
</ol></ol>
<li>summary</li>
<ol>
<li>] You now have a dynamic app that features separate model, view, and controller components, and you are testing as you go. </li>
</ol></ol>
&nbsp;
<hr />
DIRECTIVES
ng-app, ng-app="app.name"
ng-repeat
ng-controller
CONTROLLER
module
phonelist
&nbsp;
<hr />
&lt;!-- table nested --&gt; &lt;table&gt; &nbsp; &lt;tr&gt;&lt;th ng-repeat="i in [0, 1, 2, 3, 4, 5, 6, 7]"&gt; row number &lt;th&gt;&lt;/tr&gt; &nbsp;&nbsp;&nbsp; &lt;tr ng-repeat="i in [0, 1, 2, 3, 4, 5, 6, 7]"&gt; &nbsp;&nbsp; &lt;td ng-repeat="i in [0, 1, 2, 3, 4, 5, 6, 7]"&gt;{{i+1}}&lt;/td&gt; &nbsp;&nbsp; &lt;/tr&gt; &lt;/table&gt;
&nbsp;

~ view step ~ Procedure] angular-tutorial FROM [ App] framework-angular IN [ servers] technology-developer-www