This is an automated email from the ASF dual-hosted git repository.

andreww pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/royale-asjs.wiki.git


The following commit(s) were added to refs/heads/master by this push:
     new 35b61d2  Updated Royale in a Week project (markdown)
35b61d2 is described below

commit 35b61d242c8e4cdcf2038acf76cd8ec8d13019e7
Author: Andrew Wetmore <[email protected]>
AuthorDate: Sun Dec 15 07:53:46 2019 -0400

    Updated Royale in a Week project (markdown)
---
 Royale-in-a-Week-project.md | 16 +++++++++++-----
 1 file changed, 11 insertions(+), 5 deletions(-)

diff --git a/Royale-in-a-Week-project.md b/Royale-in-a-Week-project.md
index 3d419b3..ff51d34 100644
--- a/Royale-in-a-Week-project.md
+++ b/Royale-in-a-Week-project.md
@@ -5,6 +5,8 @@ Although I gained a lot from Flex in a Week, I found some of 
its structure a lit
 I am putting in italics all the entries in "Flex in a Week" that are not 
particularly relevant to Royale.
 
 ## Flex in a Week
+Videos between 5 and 25 minutes long, downloadable PDFs, downloadable code 
examples.
+The main delivery system was the videos, with the PDFs as downloadable backup 
material.
 
 * Introduction
   * Welcome
@@ -50,6 +52,10 @@ I am putting in italics all the entries in "Flex in a Week" 
that are not particu
 
 
 ## Royale in a Week
+Videos, online transcripts in the help docs, downloadable code samples.
+Carlos Rovira: "Videos should be between 1' and 3' mins long. Mostly as pills, 
more extended videos does not have impact today. In that way we can have lots 
of videos and promote in social media and have many material to share, and 
people will take the time to see it, instead of longs videos that people will 
never watch."
+The main delivery system would be the online text, with the videos 
illustrating key points.
+
 
 * Prerequisites
   * IDE or comfort with command line
@@ -69,15 +75,15 @@ I am putting in italics all the entries in "Flex in a Week" 
that are not particu
   * Building a data-driven Royale application
   * Your project structure
   * Organizing visual elements and code
-  * Migrating an existing application
-    *Emulation
+  * _Migrating an existing application_
+  * _Emulation_
 
 * Day 2 - Data Basics
   * Understanding event-driven development
   * Retrieving remote data
   * Creating a typed data model
 
-^ Day 3 - Dynamic Data Display
+* Day 3 - Dynamic Data Display
   * Extending events
   * Sending remote data
   * Validating and formatting data
@@ -100,5 +106,5 @@ I am putting in italics all the entries in "Flex in a Week" 
that are not particu
 
 
 * Next steps
-  * Unit testing
-  * _various links_
+  * Unit testing??
+  * _various links_??

Reply via email to