diff --git a/public/docs/_examples/toh-4/ts/app/boot.1.js b/public/docs/_examples/toh-4/ts/app/boot.1.js deleted file mode 100644 index 639ce566e8..0000000000 --- a/public/docs/_examples/toh-4/ts/app/boot.1.js +++ /dev/null @@ -1,16 +0,0 @@ -System.register(['angular2/platform/browser', './app.component.1'], function(exports_1) { - var browser_1, app_component_1_1; - return { - setters:[ - function (browser_1_1) { - browser_1 = browser_1_1; - }, - function (app_component_1_1_1) { - app_component_1_1 = app_component_1_1_1; - }], - execute: function() { - browser_1.bootstrap(app_component_1_1.AppComponent); - } - } -}); -//# sourceMappingURL=main.1.js.map \ No newline at end of file diff --git a/public/docs/_examples/toh-4/ts/app/boot.js b/public/docs/_examples/toh-4/ts/app/boot.js deleted file mode 100644 index da70522909..0000000000 --- a/public/docs/_examples/toh-4/ts/app/boot.js +++ /dev/null @@ -1,16 +0,0 @@ -System.register(['angular2/platform/browser', './app.component'], function(exports_1) { - var browser_1, app_component_1; - return { - setters:[ - function (browser_1_1) { - browser_1 = browser_1_1; - }, - function (app_component_1_1) { - app_component_1 = app_component_1_1; - }], - execute: function() { - browser_1.bootstrap(app_component_1.AppComponent); - } - } -}); -//# sourceMappingURL=main.js.map \ No newline at end of file diff --git a/public/docs/ts/latest/guide/template-syntax.jade b/public/docs/ts/latest/guide/template-syntax.jade index 558ed1f8e5..97cbf150da 100644 --- a/public/docs/ts/latest/guide/template-syntax.jade +++ b/public/docs/ts/latest/guide/template-syntax.jade @@ -113,8 +113,7 @@ include ../../../../_includes/_util-fns The component itself is usually the expression *context*, in which case the template expression usually references that component. - The expression context can include objects - other than the component. + The expression context can include objects other than the component. A [local template variable](#local-vars) is one such alternative context object. @@ -785,8 +784,6 @@ code-example(format="", language="html"). `ngModelChange` output property. That’s a specific example of a more general pattern in which Angular matches `[(x)]` to an `x` input property for property binding and an `xChange` output property for event binding. - :marked Is `[(ngModel)]` all we need? Is there ever a reason to fall back to its expanded form? @@ -801,7 +798,6 @@ code-example(format="", language="html"). figure.image-display img(src='/resources/images/devguide/template-syntax/ng-model-anim.gif' alt="NgModel variations") :marked - .l-main-section :marked @@ -1131,7 +1127,6 @@ figure.image-display .alert.is-important :markdown Remember: All **components** are **directives**. - :marked .l-sub-section :marked @@ -1185,7 +1180,9 @@ figure.image-display *Output* properties expose event producers, such as `EventEmitter` objects. The terms _input_ and _output_ reflect the perspective of the target directive. - +figure.image-display + img(src='/resources/images/devguide/template-syntax/input-output.png' alt="Inputs and outputs") +:marked `HeroDetailComponent.hero` is an **input** property from the perspective of `HeroDetailComponent` because data flows *into* that property from a template binding expression. diff --git a/public/resources/images/devguide/template-syntax/input-output.png b/public/resources/images/devguide/template-syntax/input-output.png new file mode 100644 index 0000000000..9df8efa5c4 Binary files /dev/null and b/public/resources/images/devguide/template-syntax/input-output.png differ