From ccdaed9d8d27c03b69053f439316da6dbbcde2bb Mon Sep 17 00:00:00 2001
From: Bill Erickson <berickxx@gmail.com>
Date: Mon, 23 Apr 2018 14:37:30 -0400
Subject: [PATCH] ang2 preso

Signed-off-by: Bill Erickson <berickxx@gmail.com>
---
 NOTES.adoc      |  4 ++--
 ang2-preso.adoc | 45 ++++++++++++++++++++++++++++-----------------
 2 files changed, 30 insertions(+), 19 deletions(-)

diff --git a/NOTES.adoc b/NOTES.adoc
index 2a24af1fa..14c83aa4d 100644
--- a/NOTES.adoc
+++ b/NOTES.adoc
@@ -243,8 +243,8 @@ RewriteRule ^(.+) %{DOCUMENT_ROOT}/root_org/$1 [L]
 * sudo npm install -g @angular/cli
 * cd Open-ILS/src/eg2
 * npm install
-* ng build --app eg-migration --output-path ../../web/js/ui/default/staff/ng2-shell
-* ng build --app eg --deploy-url /eg2/ --base-href /eg2/ --output-path  ../../web/eg2/  --watch
+* ng build --aot --app eg-migration --output-path ../../web/js/ui/default/staff/ng2-shell
+* ng build --aot --app eg --deploy-url /eg2/ --base-href /eg2/ --output-path  ../../web/eg2/  --watch
 
 ==
 
diff --git a/ang2-preso.adoc b/ang2-preso.adoc
index 1dc5eb883..183d932ea 100644
--- a/ang2-preso.adoc
+++ b/ang2-preso.adoc
@@ -20,6 +20,8 @@
 * 3-year LTS
 * EG version 3.7 (March 2021)
 
+https://blog.angular.io/stable-angularjs-and-long-term-support-7e077635ee9c
+
 == AngularJS 1.7 LTS Support
 
 1. A security flaw is detected in the 1.7.x branch of the framework
@@ -30,26 +32,25 @@ production applications using AngularJS 1.7.x to stop working
 3. The jQuery library releases a version that will cause current production 
 applications using AngularJS 1.7.x to stop working.
 
-https://blog.angular.io/stable-angularjs-and-long-term-support-7e077635ee9c
-
 == Introducing Angular
 
-A complete rewrite of AngularJS.
+A complete redesign and rewrite of AngularJS.
 
 == Key Changes and Additions
 
 * Nested Routing and Lazy Loading
 * Integrated i18n
 * Use of TypeScript
-* Native Service Workers Module
+* Ahead-of-Time Compilation
 * Expressive component interactions / data binding
 * Route-reuse for components.
+* Native Service Workers Module
 * Integrated ReactiveX library for JavaScript (RxJS).
 * ng-cli Command line tool for compiling, testing, building.
 
 == Nested Routing and Lazy Loading
 * Routers and resolvers all the way down.
-* Code for lazy-loaded modules is retrieved by the browser on demand.
+* Code and templates for lazy-loaded modules is retrieved on demand.
 * Apps can have many modules and still load quickly.
 
 == Integrated I18N 
@@ -58,7 +59,7 @@ A complete rewrite of AngularJS.
 ----------------------------------------------------------------------
 <h1 i18>Hello i18n!</h1>
 <h1 i18n="Section welcome header">Hello i18n!</h1>
-<h1 i18n="page header|Section welcome header">Hello i18n!</h1>
+<h1 i18n="welcome|Section welcome header">Hello i18n!</h1>
 
 <eg-confirm-dialog
   i18n-dialogTitle
@@ -72,6 +73,7 @@ A complete rewrite of AngularJS.
  
 * ng xi18n
 * https://en.wikipedia.org/wiki/XLIFF -- default format
+** Supports XLIFF 1.2 (default), XLIFF 2, XML Message Bundle (XMB)
 * PO files not supported, but XLIFF/PO translators exist
 ** http://docs.translatehouse.org/projects/translate-toolkit/en/latest/commands/xliff2po.html
 
@@ -98,11 +100,11 @@ In v6 we will release runtime i18n: one bundle for all locale, translations
 resolved at runtime, and maybe *code translations* if we have the time 
 (otherwise it'll come soon after). 
 
-== Template Toolkit?
+== Retire Template Toolkit?
 
-* Mixing ng5 i18n and TT no-go.
-* Lets us return to standard ng5 structure.
-* Code & templates in same directory
+* Using standard ng5 layout and tools
+** Mixing ng5 i18n and TT no-go.
+* Code & templates in same directory is very convenient
 * Org unit template overlays possible using ModRewrite
 
 == RxJS
@@ -229,7 +231,7 @@ image:images/ng1_plus_ng5_shared.png[ng1 sharing with ng5]
 
 == Unshared Parallel: Challenges
 * Maintaining multiple versions of share-able code.
-** The 1/4
+** The ~1/4
 
 == Intermission: Migration App Demo
 
@@ -237,14 +239,23 @@ https://35.186.179.218/eg2/staff/splash
 
 == Other Migration Tasks
 
-* Phasing out iframes and Dojo UIs.
-
-== IMHO
+* Phasing out Dojo UI's and iframes.
 
+== Decisions
 [role="incremental"]
-* Use Parallel migration without downgrading services
-* Start by migrating Dojo / iframe interfaces
-* Follow the Angular style guide.
+* Are we doing this?
+* Pick a migration strategy
+* Pick an icon set
+* Determine minimum requirements for initial deployment.
+
+== Potential Migration Milestones (parallel / no downgrades)
+* 3.2 Key services ported and navbar synchronized.
+* 3.3 First batch of Dojo/iframe UIs migrated.  Initial deployment.
+* 3.4 More Dojo UI's migrated. New UI's too.
+* 3.5 Dojo wrapped up, first batch of ng1 UI's ported.
+* 3.6 More ng1 UI's ported.
+* 3.7 ng1 migration wrapped up, ng1 deprecated.
+* 3.8 (4.0?) Purge ng1
 
 == Questions
 
-- 
2.11.0