From 075c089b5cbe72e95ec96638f8925aeb44824f7c Mon Sep 17 00:00:00 2001
From: Igor Minar
Date: Fri, 27 Apr 2012 15:18:54 -0700
Subject: docs(tutorial): update all the remaining steps
I made some diagrams and portions of the text that are stil stale
invisible. We'll fix these in the next relese.
---
docs/content/tutorial/step_10.ngdoc | 57 ++++++++++++++++++-------------------
1 file changed, 28 insertions(+), 29 deletions(-)
(limited to 'docs/content/tutorial/step_10.ngdoc')
diff --git a/docs/content/tutorial/step_10.ngdoc b/docs/content/tutorial/step_10.ngdoc
index dd31da82..1d60de06 100644
--- a/docs/content/tutorial/step_10.ngdoc
+++ b/docs/content/tutorial/step_10.ngdoc
@@ -2,8 +2,6 @@
@name Tutorial: 10 - Event Handlers
@description
-
This page has not been updated for AngularJS 1.0 yet
In the `PhoneDetailCtrl` controller, we created the `mainImageUrl` model property and set its
default value to the first phone image url.
-We also created a `setImage` controller method to change the value of `mainImageUrl`.
+We also created a `setImage` event handler function that will change the value of `mainImageUrl`.
## Template
__`app/partials/phone-detail.html`:__
-
+
...
-
-
+
+
...
-We bound the `ng:src` attribute of the large image to the `mainImageUrl` property.
+We bound the `ngSrc` directive of the large image to the `mainImageUrl` property.
-We also registered an {@link api/angular.directive.ng:click `ng:click`} handler with thumbnail
-images. When a user clicks on one of the thumbnail images, the handler will use the `setImage`
-controller method to change the value of the `mainImageUrl` property to the url of the thumbnail
-image.
+We also registered an {@link api/angular.module.ng.$compileProvider.directive.ngClick `ngClick`}
+handler with thumbnail images. When a user clicks on one of the thumbnail images, the handler will
+use the `setImage` event handler function to change the value of the `mainImageUrl` property to the
+url of the thumbnail image.
+
+TODO!
+
## Test
@@ -85,13 +84,10 @@ __`test/e2e/scenarios.js`:__
...
describe('Phone detail view', function() {
- beforeEach(function() {
- browser().navigateTo('../../app/index.html#/phones/nexus-s');
- });
-
+...
it('should display the first phone image as the main phone image', function() {
- expect(element('img.phone').attr('src')).toBe('img/phones/nexus-s.0.jpg');
+ expect(element('img.phone').attr('src')).toBe('img/phones/nexus-s.0.jpg');
});
@@ -113,24 +109,27 @@ angular's server}.
# Experiments
-* Let's add a new controller method to `PhoneCatCtrl`:
+* Let's add a new controller method to `PhoneDetailCtrl`:
- this.hello = function(name) {
+ $scope.hello = function(name) {
alert('Hello ' + (name || 'world') + '!');
}
and add:
-
+
- to the `index.html` template.
+ to the `phone-details.html` template.
+
+TODO!
The controller methods are inherited between controllers/scopes, so you can use the same snippet
in the `phone-list.html` template as well.
* Move the `hello` method from `PhoneCatCtrl` to `PhoneListCtrl` and you'll see that the button
declared in `index.html` will stop working, while the one declared in the `phone-list.html`
template remains operational.
+