docs(architecture/dart): post-review changes

Author: chalin

public/docs/_examples/architecture/dart/lib/hero_list_component.dart

@@ -15,11 +15,11 @@ import 'hero_service.dart';
 // #docregion class
 class HeroListComponent implements OnInit {
   // #enddocregion metadata, providers
-  final HeroService _heroService;
   List<Hero> heroes;
   Hero selectedHero;
-
   // #docregion ctor
+  final HeroService _heroService;
+
   HeroListComponent(this._heroService);
   // #enddocregion ctor
 

public/docs/dart/latest/guide/animations.jade

@@ -0,0 +1 @@
+!= partial("../../../_includes/_ts-temp")

public/docs/dart/latest/guide/architecture.jade

@@ -14,29 +14,39 @@ block angular-parts
     Angular 2 for Dart is published as the `angular2` package, which
     (like many other Dart packages) is available via the Pub tool.
 
-block dart-terminology
+block modules-in-dart
   .callout.is-helpful
-    header Dart difference: Module is a compilation unit
+    header Dart difference: Modules are compilation units or packages
     :marked
-      The term "module" used in this guide refers to a
-      Dart _compilation unit_, i.e., a _library_ or _part_.
-      For more information about compilation units, see
+      In this guide, the term _module_ refers to a Dart compilation unit, such
+      as a library, or a package. (If a Dart file has no `library` or `part`
+      directive, then that file itself is a library and thus a compilation
+      unit.) For more information about compilation units, see
       the chapter on "Libraries and Scripts" in the
       [Dart Language Specification](https://www.dartlang.org/docs/spec/).
 
 block modules-are-optional
   //- N/A
 
-block ts-export
-  //- N/A
+block export-qualifier
+  .callout.is-helpful
+    header Dart difference: Public names are exported by default
+    :marked
+      Contrary to TypeScript, a Dart library always exports all names and
+      declarations in its **public** namespace, making explicit `export`
+      qualifiers unnecessary.
+      
+      When we say that a module _exports_ a declaration, we mean that the
+      declaration is _public_. For more details about name spaces and export
+      statements, see the section on "Exports" in the
+      [Dart Language Specification](https://www.dartlang.org/docs/spec/).
 
 block ts-import
   //- N/A
 
 block angular-library-modules
   :marked
-    Some modules are libraries.
-    Angular itself ships as a collection of libraries within the
+    Angular ships as a collection of libraries within the
     [**angular2**](https://pub.dartlang.org/packages/angular2) package.
 
 block angular-imports
@@ -49,3 +59,14 @@ block ts-decorator
     information Angular needs to create and present the component and its view.
 
     Here are a few of the possible `@Component` parameters:
+
+block dart-bool
+  .callout.is-helpful
+    header Dart difference: Only true is true
+    :marked
+      In Dart, **the only value that is true is the boolean value `true`**; all
+      other values are false. JavaScript and TypeScript, in contrast, treat values
+      such as 1 and most non-null objects as true. For this reason, the JavaScript
+      and TypeScript versions of this app can use just `selectedHero` as the value
+      of the `*ngIf` expression. The Dart version must use a boolean operator such
+      as `!=` instead.

public/docs/ts/latest/guide/architecture.jade

@@ -57,7 +57,7 @@ figure
   A module **exports** something of value in that code, typically one thing such as a class.
   <br clear="all"><br>
 
-block dart-terminology
+block modules-in-dart
   //- N/A
 
 block modules-are-optional
@@ -73,18 +73,19 @@ block modules-are-optional
        Find setup and organization clues in the JavaScript track (select it from the combo-box at the top of this page)
        which demonstrates Angular 2 development with plain old JavaScript and no module system.
 
+- var _app_comp_filename = _docsFor == 'dart' ? 'app_component.dart' : 'app.component.ts';
 :marked
   Perhaps the first module we meet is a module that exports a *component* class.
   The component is one of the basic Angular blocks, we write a lot of them,
   and we'll talk about components in the next segment. For the moment it is enough to know that a
   component class is the kind of thing we'd export from a module.
 
-  Most applications have an `AppComponent`. By convention, we'll find it in a file named `app.component.ts`.
+  Most applications have an `AppComponent`. By convention, we'll find it in a file named `!{_app_comp_filename}`.
   Look inside such a file and we'll see a declaration like this one.
 
 +makeExcerpt('app/app.component.ts ()', 'export')
 
-block ts-export
+block export-qualifier
   :marked
     The `export` statement tells TypeScript that this is a module whose
     `AppComponent` class is public and accessible to other modules of the application.
@@ -150,13 +151,15 @@ block angular-imports
       While we're focused on our application, *import* and *export*
       is about all we need to know.
 
+- var _export = _docsFor == 'dart' ? 'publicly declare' : 'export';
+- var _declare = _docsFor == 'dart' ? 'declare' : 'export';
 :marked
   The key take-aways are:
   * Angular apps are composed of modules.
-  * Modules export things &mdash; classes, function, values &mdash; that other modules import.
+  * Modules !{_export} things &mdash; classes, function, values &mdash; that other modules import.
   * We prefer to write our application as a collection of modules, each module exporting one thing.
 
-  The first module we write will most likely export a component.
+  The first module we write will most likely !{_declare} a component.
 
 .l-main-section
 :marked
@@ -181,7 +184,7 @@ figure
 +makeExcerpt('app/hero-list.component.ts', 'class')
 :marked
   Angular creates, updates, and destroys components as the user moves through the application.
-  The developer can take action at each moment in this lifecycle through optional [lifecycle hooks](lifecycle-hooks.html).
+  The developer can take action at each moment in this lifecycle through optional [lifecycle hooks](lifecycle-hooks.html), like `ngOnInit()` declared above.
 .l-sub-section
   :marked
     We may wonder who is calling the component's constructor? Who provides the service parameter?
@@ -391,14 +394,8 @@ figure
   * [`*ngFor`](displaying-data.html#ngFor) tells Angular to stamp out one `<li>` per hero in the `heroes` list.
   * [`*ngIf`](displaying-data.html#ngIf) includes the `HeroDetail` component only if a selected hero exists.
 
-.l-sub-section
-  :marked
-    In Dart, **the only value that is true is the boolean value `true`**; all
-    other values are false. JavaScript and TypeScript, in contrast, treat values
-    such as 1 and most non-null objects as true. For this reason, the JavaScript
-    and TypeScript versions of this app can use just `selectedHero` as the value
-    of the `*ngIf` expression. The Dart version must use a boolean operator such
-    as `!=` instead.
+block dart-bool
+  //- N/A
 
 :marked
   **Attribute** directives alter the appearance or behavior of an existing element.
@@ -412,7 +409,7 @@ figure
 +makeExcerpt('app/hero-detail.component.html', 'ngModel')
 :marked
   Angular ships with a small number of other directives that either alter the layout structure
-  (e.g. [ngSwitch](template-syntax.html#ngSwitch))
+  (for example, [ngSwitch](template-syntax.html#ngSwitch))
   or modify aspects of DOM elements and components
   (for example, [ngStyle](template-syntax.html#ngStyle) and [ngClass](template-syntax.html#ngClass)).