glimmer 0.9.5 → 0.10.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: c22f962213e82b271d67b69d910604e73ab8a257e8a797fa58feb2d97d6c199e
-  data.tar.gz: eee60acdf118d572196ef4a2c1eca7705093ea9d3db2fcea1a05bb612710f05b
+  metadata.gz: 4fbfd6caf79d10dbaeb2d737d68a8f028819d6172f45a8b494d1a88c34e3e04b
+  data.tar.gz: 9fcbc6d1948ced1b67192aeb22a25420b9a165930bc084e30534141c2f65a1fb
 SHA512:
-  metadata.gz: 360edce8ae04be32396a272ad947897d256c171759f3304ed4f3b521a208540a2834e05a3140fe61de166337858bbd85c13655d02b92b1cd13e60b44b78cb0d6
-  data.tar.gz: 482df9f676948f24f68e665899c15e7e14b78f40f100580771a4af943fd524b676ae140f19cf1d7b370d2ef1fb5e3c4bff9f0e2eb4a8cb1cb95884c74be6ef37
+  metadata.gz: b5809d0f9a9ae9536dfaf0ff74612c44a74df732d3ea7db7a8102aec6e434373104f9fba13a1aa3c1109faad754cfa390c3ac57bbd5de379f31441d9d61357d0
+  data.tar.gz: 4d5d53bd6881b462b2aa2ca36ddcd2e41ab61862f5162e0a888288596609271fb5e8e3130a9c99647d7226ed1373ee1b2a6477d8e5660ec13bbb615f5a853b72

data/README.md

@@ -1,14 +1,17 @@
-# <img src="https://raw.githubusercontent.com/AndyObtiva/glimmer/master/images/glimmer-logo-hi-res.png" height=85 style="position: relative; top: 20px;" /> Glimmer (Ruby Desktop Development GUI Library)
+# [<img src="https://raw.githubusercontent.com/AndyObtiva/glimmer/master/images/glimmer-logo-hi-res.png" height=85 style="position: relative; top: 20px;" />](https://rubygems.org/gems/glimmer) Glimmer (Ruby Desktop Development GUI Library)
 [![Gem Version](https://badge.fury.io/rb/glimmer.svg)](http://badge.fury.io/rb/glimmer)
 [![Travis CI](https://travis-ci.com/AndyObtiva/glimmer.svg?branch=master)](https://travis-ci.com/github/AndyObtiva/glimmer) 
 [![Coverage Status](https://coveralls.io/repos/github/AndyObtiva/glimmer/badge.svg?branch=master)](https://coveralls.io/github/AndyObtiva/glimmer?branch=master)
+[![Maintainability](https://api.codeclimate.com/v1/badges/38fbc278022862794414/maintainability)](https://codeclimate.com/github/AndyObtiva/glimmer/maintainability)
 [![Join the chat at https://gitter.im/AndyObtiva/glimmer](https://badges.gitter.im/AndyObtiva/glimmer.svg)](https://gitter.im/AndyObtiva/glimmer?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
 
 **[Contributors Wanted! (Submit a Glimmer App Sample to Get Started)](#contributing)**
 
 (The Original Glimmer Library Since 2007. Beware of Imitators!)
 
-Glimmer is a native-GUI cross-platform desktop development library written in Ruby. Glimmer's main innovation is a JRuby DSL that enables productive and efficient authoring of desktop application user-interfaces while relying on the robust Eclipse SWT library. Glimmer additionally innovates by having built-in data-binding support to greatly facilitate synchronizing the GUI with domain models. As a result, that achieves true decoupling of object oriented components, enabling developers to solve business problems without worrying about GUI concerns, or alternatively drive development GUI-first, and then write clean business models test-first afterwards.
+[**Glimmer**](https://rubygems.org/gems/glimmer) is a native-GUI cross-platform desktop development library written in [JRuby](https://www.jruby.org/), an OS-threaded faster version of [Ruby](https://www.ruby-lang.org/en/). [Glimmer](https://rubygems.org/gems/glimmer)'s main innovation is a declarative [Ruby DSL](#glimmer-dsl-syntax) that enables productive and efficient authoring of desktop application user-interfaces while relying on the robust [Eclipse SWT library](https://www.eclipse.org/swt/). [Glimmer](https://rubygems.org/gems/glimmer) additionally innovates by having built-in [data-binding](#data-binding) support, which greatly facilitates synchronizing the GUI with domain models, thus achieving true decoupling of object oriented components and enabling developers to solve business problems (test-first) without worrying about GUI concerns. To get started quickly, [Glimmer](https://rubygems.org/gems/glimmer) offers [scaffolding](#scaffolding) options for [Apps](#in-production), [Gems](#custom-shell-gem), and [Custom Widgets](#custom-widgets). [Glimmer](https://rubygems.org/gems/glimmer) also includes native-executable [packaging](#packaging--distribution) support, sorely lacking in other libraries, thus enabling the delivery of desktop apps written in [Ruby](https://www.ruby-lang.org/en/) as truly native DMG/PKG/APP files on the [Mac](https://www.apple.com/ca/macos) + [App Store](https://developer.apple.com/macos/distribution/) and MSI/EXE files on [Windows](https://www.microsoft.com/en-ca/windows). Unlike libraries like TK, [Glimmer](https://rubygems.org/gems/glimmer) does not require recompilation of [Ruby](https://www.ruby-lang.org/en/). [Glimmer](https://rubygems.org/gems/glimmer) runs native GUI out of the box on every platform thanks to the [JVM](https://java.com/en/download/faq/whatis_java.xml), [JRuby](https://www.jruby.org/), and the [Eclipse SWT library](https://www.eclipse.org/swt/).
+
+NOTE: Glimmer is in beta mode. Please help make better by [contributing](#contributing), adopting for small or low risk projects, and providing feedback. While a lot of hard work has gone into it, it is by no means polished, and definitely has bugs waiting to be reported. The more feedback and issues you report the better.
 
 [<img src="https://covers.oreillystatic.com/images/9780596519650/lrg.jpg" width=105 /><br /> 
 Featured in<br />JRuby Cookbook](http://shop.oreilly.com/product/9780596519650.do)
@@ -17,13 +20,13 @@ Glimmer DSL gems:
 - [glimmer-dsl-swt](https://github.com/AndyObtiva/glimmer-dsl-swt): Glimmer DSL for SWT (Desktop GUI)
 - [glimmer-dsl-opal](https://github.com/AndyObtiva/glimmer-dsl-opal): Glimmer DSL for Opal (Web GUI Adapter for Desktop Apps)
 - [glimmer-dsl-xml](https://github.com/AndyObtiva/glimmer-dsl-xml): Glimmer DSL for XML (& HTML)
-- [glimmer-dsl-css](https://github.com/AndyObtiva/glimmer-dsl-css): Glimmer DSL for CSS (Cascading Style Sheets)
+- [glimmer-dsl-css](https://github.com/AndyObtiva/glimmer-dsl-css): Glimmer DSL for CSS
 
 ## Examples
 
 ### Hello, World!
 
-Glimmer code (from `samples/hello/hello_world.rb`):
+Glimmer code (from [samples/hello/hello_world.rb](https://github.com/AndyObtiva/glimmer-dsl-swt/blob/master/samples/hello/hello_world.rb)):
 ```ruby
 include Glimmer
 
@@ -46,28 +49,28 @@ Glimmer app:
 
 ### Tic Tac Toe
 
-Glimmer code (from `samples/elaborate/tic_tac_toe.rb`):
+Glimmer code (from [samples/elaborate/tic_tac_toe.rb](https://github.com/AndyObtiva/glimmer-dsl-swt/blob/master/samples/elaborate/tic_tac_toe.rb)):
 
 ```ruby
 # ...
-shell {
-  text "Tic-Tac-Toe"
-  composite {
-    grid_layout 3, true
-    (1..3).each { |row|
-      (1..3).each { |column|
-        button {
-          layout_data :fill, :fill, true, true
-          text        bind(@tic_tac_toe_board[row, column], :sign)
-          enabled     bind(@tic_tac_toe_board[row, column], :empty)
-          on_widget_selected {
-            @tic_tac_toe_board.mark(row, column)
+    @shell = shell {
+      text "Tic-Tac-Toe"
+      composite {
+        grid_layout 3, true
+        (1..3).each { |row|
+          (1..3).each { |column|
+            button {
+              layout_data :fill, :fill, true, true
+              text        bind(@tic_tac_toe_board[row, column], :sign)
+              enabled     bind(@tic_tac_toe_board[row, column], :empty)
+              on_widget_selected {
+                @tic_tac_toe_board.mark(row, column)
+              }
+            }
           }
         }
       }
     }
-  }
-}
 # ...
 ```
 
@@ -81,7 +84,95 @@ Glimmer app:
 
 ![Tic Tac Toe](images/glimmer-tic-tac-toe-in-progress.png)
 
-NOTE: Glimmer is in beta mode. Please help make better by [contributing](#contributing), adopting for small or low risk projects, and providing feedback.
+### Contact Manager
+
+Glimmer code (from [samples/elaborate/contact_manager.rb](https://github.com/AndyObtiva/glimmer-dsl-swt/blob/master/samples/elaborate/contact_manager.rb)):
+
+```ruby
+# ...
+    shell {
+      text "Contact Manager"
+      composite {
+        composite {
+          grid_layout 2, false
+          label {text "First &Name: "}
+          text {
+            text bind(@contact_manager_presenter, :first_name)
+            on_key_pressed {|key_event|
+              @contact_manager_presenter.find if key_event.keyCode == swt(:cr)
+            }
+          }
+          label {text "&Last Name: "}
+          text {
+            text bind(@contact_manager_presenter, :last_name)
+            on_key_pressed {|key_event|
+              @contact_manager_presenter.find if key_event.keyCode == swt(:cr)
+            }
+          }
+          label {text "&Email: "}
+          text {
+            text bind(@contact_manager_presenter, :email)
+            on_key_pressed {|key_event|
+              @contact_manager_presenter.find if key_event.keyCode == swt(:cr)
+            }
+          }
+          composite {
+            grid_layout 2, false
+            button {
+              text "&Find"
+              on_widget_selected {
+                @contact_manager_presenter.find
+              }
+            }
+            button {
+              text "&List All"
+              on_widget_selected {
+                @contact_manager_presenter.list
+              }
+            }
+          }
+        }
+
+        table(:multi) { |table_proxy|
+          layout_data {
+            horizontal_alignment :fill
+            vertical_alignment :fill
+            grab_excess_horizontal_space true
+            grab_excess_vertical_space true
+            height_hint 200
+          }
+          table_column {
+            text "First Name"
+            width 80
+          }
+          table_column {
+            text "Last Name"
+            width 80
+          }
+          table_column {
+            text "Email"
+            width 200
+          }
+          items bind(@contact_manager_presenter, :results),
+                column_properties(:first_name, :last_name, :email)
+          on_mouse_up { |event|
+            table_proxy.edit_table_item(event.table_item, event.column_index)
+          }
+        }
+      }
+    }.open
+# ...
+```
+
+Run:
+
+```
+glimmer samples/elaborate/contact_manager.rb
+```
+
+Glimmer App:
+
+![Contact Manager](images/glimmer-contact-manager.png)
 
 ## Table of contents
 
@@ -112,7 +203,8 @@ NOTE: Glimmer is in beta mode. Please help make better by [contributing](#contri
     - [Raw JRuby Command](#raw-jruby-command)
       - [Mac Support](#mac-support)
   - [Girb (Glimmer irb) Command](#girb-glimmer-irb-command)
-  - [Glimmer DSL Syntax](#glimmer-dsl-syntax)
+  - [Glimmer GUI DSL Syntax](#glimmer-gui-dsl-syntax)
+    - [DSL Auto-Expansion](#dsl-auto-expansion)
     - [Widgets](#widgets)
       - [Display](#display)
       - [SWT Proxies](#swt-proxies)
@@ -175,13 +267,15 @@ NOTE: Glimmer is in beta mode. Please help make better by [contributing](#contri
     - [Elaborate Samples](#elaborate-samples)
       - [Login](#login)
       - [Tic Tac Toe Sample](#tic-tac-toe-sample)
-      - [Contact Manager](#contact-manager)
+      - [Contact Manager](#contact-manager-sample)
     - [External Samples](#external-samples)
       - [Glimmer Calculator](#glimmer-calculator)
       - [Gladiator](#gladiator)
+      - [Timer](#timer)
   - [In Production](#in-production)
     - [Math Bowling](#math-bowling)
     - [Are We There Yet?](#are-we-there-yet)
+    - [Garderie Rainbow Daily Agenda](#garderie-rainbow-daily-agenda)
   - [Packaging & Distribution](#packaging--distribution)
     - [Packaging Defaults](#packaging-defaults)
     - [Packaging Configuration](#packaging-configuration)
@@ -189,6 +283,9 @@ NOTE: Glimmer is in beta mode. Please help make better by [contributing](#contri
     - [Mac Application Distribution](#mac-application-distribution)
     - [Self Signed Certificate](#self-signed-certificate)
     - [Gotchas](#gotchas)
+  - [App Updates](#app-updates)
+  - [Glimmer Supporting Libraries](#glimmer-supporting-libraries)
+  - [Glimmer Process](#glimmer-process)
   - [Resources](#resources)
   - [Help](#help)
     - [Issues](#issues)
@@ -223,18 +320,17 @@ https://www.eclipse.org/swt/faq.php
 
 ## Pre-requisites
 
-- SWT 4.15 (comes included in Glimmer gem)
-- JRuby 9.2.12.0 (supporting Ruby 2.5.x syntax) (find at [https://www.jruby.org/download](https://www.jruby.org/download))
-- JDK 8 - 10 (find at [https://www.oracle.com/java/technologies/javase-downloads.html](https://www.oracle.com/java/technologies/javase-downloads.html))
-- (Optional) RVM is needed for [Scaffolding](#scaffolding) only (find at [https://rvm.io/](https://rvm.io/))
+- JDK 8u241 (1.8.0_241) (find at https://www.oracle.com/java/technologies/javase/javase8u211-later-archive-downloads.html)
+- JRuby 9.2.13.0 (supporting Ruby 2.5.x syntax) (get via [RVM](http://rvm.io) on Mac and Linux or find at [https://www.jruby.org/download](https://www.jruby.org/download) for Windows)
+- SWT 4.16 (already included in the [glimmer-dsl-swt](https://rubygems.org/gems/glimmer-dsl-swt) gem)
 
-On **Mac** and **Linux**, an easy way to obtain JRuby is through [RVM](http://rvm.io) by running:
+To obtain JRuby through [RVM](http://rvm.io), you may run:
 
 ```bash
-rvm install jruby-9.2.12.0
+rvm install jruby-9.2.13.0
 ```
 
-Glimmer might still work on lower versions of Java, JRuby and SWT, but there are no guarantees, so it is best to stick to the pre-requisites outlined above.
+Glimmer might still work on other versions of Java, JRuby and SWT, but there are no guarantees, so it is best to stick to the pre-requisites outlined above.
 
 ## Setup
 
@@ -242,20 +338,25 @@ Please follow these instructions to make the `glimmer` command available on your
 
 If you intend to learn the basics of Glimmer but are not ready to build a Glimmer app yet, pick Option 1 ([Direct Install](#option-1-direct-install)).
 
-If you intend to build a Glimmer app from scratch on the Mac, pick Option 1 ([Direct Install](#option-1-direct-install)) to leverage [Glimmer Scaffolding](#scaffolding) (only available on the Mac).
+If you intend to build a Glimmer app from scratch with [scaffolding](#scaffolding), pick Option 1 ([Direct Install](#option-1-direct-install)) as well.
 
-Otherwise, Option 2 ([Bundler](#option-2-bundler)) is recommended for building Glimmer apps on other platforms (Windows and Linux).
+Otherwise, Option 2 ([Bundler](#option-2-bundler)) can be followed in rare cases where you want to build an app without [scaffolding](#scaffolding).
 
 ### Option 1: Direct Install 
-(Use for [Scaffolding](#scaffolding) on the Mac)
+(Use for [Scaffolding](#scaffolding))
 
 Run this command to install directly:
 ```
-jgem install glimmer-dsl-swt -v 0.3.0
+jgem install glimmer-dsl-swt
+```
+
+Or this command if you want a specific version:
+```
+jgem install glimmer-dsl-swt -v 0.6.5
 ```
 
 `jgem` is JRuby's version of `gem` command. 
-RVM allows running `gem` as an alias.
+RVM allows running `gem install` directly as an alias.
 Otherwise, you may also run `jruby -S gem install ...`
 
 If you are new to Glimmer and would like to continue learning the basics, you may continue to the [Glimmer Command](https://github.com/AndyObtiva/glimmer#glimmer-command) section.
@@ -269,7 +370,7 @@ Note: if you're using activerecord or activesupport, keep in mind that Glimmer u
 
 Add the following to `Gemfile`:
 ```
-gem 'glimmer-dsl-swt', '~> 0.3.0'
+gem 'glimmer-dsl-swt', '~> 0.6.5'
 ```
 
 And, then run:
@@ -285,7 +386,17 @@ You may learn more about other Glimmer related gems ([`glimmer-dsl-opal`](https:
 
 The `glimmer` command allows you to run, scaffold, package, and list Glimmer applications/gems.
 
-If you are new to Glimmer, you may read the Basic Usage section and skip the rest until you have gone through [Girb (Glimmer irb) Command](#girb-glimmer-irb-command), [Glimmer DSL Syntax](#glimmer-dsl-syntax), and [Samples](#samples).
+You can bring up usage instructions by running the `glimmer` command without arguments:
+
+```
+glimmer
+```
+
+On Mac and Linux, it additionally brings up a TUI (Text-based User Interface) for interactive navigation and execution of Glimmer tasks (courtesy of [rake-tui](https://github.com/AndyObtiva/rake-tui)). 
+
+On Windows, it simply lists the available Glimmer tasks at the end (courtsey of [rake](https://github.com/ruby/rake)).
+
+If you are new to Glimmer, you may read the Basic Usage section and skip the rest until you have gone through [Girb (Glimmer irb) Command](#girb-glimmer-irb-command), [Glimmer GUI DSL Syntax](#glimmer-gui-dsl-syntax), and [Samples](#samples).
 
 ### Basic Usage
 
@@ -314,42 +425,44 @@ bin/glimmer samples/hello/hello_world.rb
 Below are the full usage instructions that come up when running `glimmer` without args.
 
 ```
+Glimmer (Ruby Desktop Development GUI Library) - JRuby Gem: glimmer-dsl-swt v0.6.5
+      
 Usage: glimmer [--quiet] [--debug] [--log-level=VALUE] [[ENV_VAR=VALUE]...] [[-jruby-option]...] (application.rb or task[task_args]) [[application2.rb]...]
 
-Runs Glimmer applications/tasks.
-
-Either a single task or one or more applications may be specified.
-
-When a task is specified, it runs via rake. Some tasks take arguments in square brackets.
-
-Available tasks are below (you may also lookup by adding `require 'glimmer/rake_task'` in Rakefile and running rake -T):
-glimmer list:custom_shell_gems[query]                             # List Glimmer custom shell gems available at rubygems.org (query is optional)
-glimmer list:custom_widget_gems[query]                            # List Glimmer custom widget gems available at rubygems.org (query is optional)
-glimmer list:dsl_gems[query]                                      # List Glimmer DSL gems available at rubygems.org (query is optional)
-glimmer package                                                   # Package app for distribution (generating config, jar, and native files)
-glimmer package:clean                                             # Clean by removing "dist" and "packages" directories
-glimmer package:config                                            # Generate JAR config file
-glimmer package:jar                                               # Generate JAR file
-glimmer package:native                                            # Generate Native files (DMG/PKG/APP on the Mac)
-glimmer scaffold[app_name]                                        # Scaffold a Glimmer application directory structure to begin building a new app
-glimmer scaffold:custom_shell[custom_shell_name,namespace]        # Scaffold a Glimmer::UI::CustomShell subclass (represents a full window view) under app/views (namespace is optional)
-glimmer scaffold:custom_shell_gem[custom_shell_name,namespace]    # Scaffold a Glimmer::UI::CustomShell subclass (represents a full window view) under its own Ruby gem + app project (namespace is required)
-glimmer scaffold:custom_widget[custom_widget_name,namespace]      # Scaffold a Glimmer::UI::CustomWidget subclass (represents a part of a view) under app/views (namespace is optional)
-glimmer scaffold:custom_widget_gem[custom_widget_name,namespace]  # Scaffold a Glimmer::UI::CustomWidget subclass (represents a part of a view) under its own Ruby gem project (namespace is required)
+Runs Glimmer applications and tasks.    
 
 When applications are specified, they are run using JRuby, 
 automatically preloading the glimmer Ruby gem and SWT jar dependency.
 
-Optionally, extra Glimmer options, JRuby options and environment variables may be passed in.
+Optionally, extra Glimmer options, JRuby options, and/or environment variables may be passed in.
 
 Glimmer options:
 - "--quiet"           : Does not announce file path of Glimmer application being launched
 - "--debug"           : Displays extra debugging information, passes "--debug" to JRuby, and enables debug logging
 - "--log-level=VALUE" : Sets Glimmer's Ruby logger level ("ERROR" / "WARN" / "INFO" / "DEBUG"; default is none)
 
-Example: glimmer samples/hello_world.rb
-
-This runs the Glimmer application samples/hello_world.rb
+Tasks are run via rake. Some tasks take arguments in square brackets.
+
+Available tasks are below (if you do not see any, please add `require 'glimmer/rake_task'` to Rakefile and rerun or run rake -T):
+
+Select a Glimmer task to run: (Press ↑/↓ arrow to move, Enter to select and letters to filter)
+‣ glimmer list:gems:customshell[query]                       # List Glimmer custom shell gems available at rubygems.org (query is optional) [alt: list:gems:cs]
+  glimmer list:gems:customwidget[query]                      # List Glimmer custom widget gems available at rubygems.org (query is optional) [alt: list:gems:cw]
+  glimmer list:gems:dsl[query]                               # List Glimmer DSL gems available at rubygems.org (query is optional)
+  glimmer package[type]                                      # Package app for distribution (generating config, jar, and native files) (type is optional)
+  glimmer package:clean                                      # Clean by removing "dist" and "packages" directories
+  glimmer package:config                                     # Generate JAR config file
+  glimmer package:jar                                        # Generate JAR file
+  glimmer package:lock_jars                                  # Lock JARs
+  glimmer package:native[type]                               # Generate Native files
+  glimmer sample:code[name]                                  # Outputs code for a Glimmer internal sample [included in gem] (name is required)
+  glimmer sample:list[query]                                 # Lists Glimmer internal samples [included in gem]. Filters by query if specified (query is optional)
+  glimmer sample:run[name]                                   # Runs a Glimmer internal sample [included in gem]. If no name is supplied, it runs all samples
+  glimmer scaffold[app_name]                                 # Scaffold Glimmer application directory structure to build a new app
+  glimmer scaffold:customshell[name,namespace]               # Scaffold Glimmer::UI::CustomShell subclass (full window view) under app/views (namespace is optional) [alt: scaffold:cs]
+  glimmer scaffold:customwidget[name,namespace]              # Scaffold Glimmer::UI::CustomWidget subclass (part of a view) under app/views (namespace is optional) [alt: scaffold:cw]
+  glimmer scaffold:gem:customshell[name,namespace]           # Scaffold Glimmer::UI::CustomShell subclass (full window view) under its own Ruby gem + app project (namespace is required) [alt: scaffold:ge...
+  glimmer scaffold:gem:customwidget[name,namespace]          # Scaffold Glimmer::UI::CustomWidget subclass (part of a view) under its own Ruby gem project (namespace is required) [alt: scaffold:gem:cw]
 ```
 
 Example (Glimmer/JRuby option specified):
@@ -366,26 +479,353 @@ glimmer samples/hello/hello_world.rb samples/hello_tab.rb
 
 Launches samples/hello/hello_world.rb and samples/hello_tab.rb at the same time, each in a separate JRuby thread.
 
+### Sample List/Run/Code
+
+#### Sample List
+
+You can list available Glimmer samples by running:
+
+```
+glimmer sample:list
+```
+
+This should output the following (providing the name of each sample, description, and command to run the sample and view its code):
+
+```
+$ glimmer sample:list
+
+  Glimmer Hello Samples (run all via: glimmer sample:run:hello):
+                                                                                                               
+             Name                       Description                                 Run                        
+                                                                                                               
+  hello_browser                 Hello Browser                 glimmer sample:run[hello_browser]                
+  hello_combo                   Hello Combo                   glimmer sample:run[hello_combo]                  
+  hello_computed                Hello Computed                glimmer sample:run[hello_computed]               
+  hello_drag_and_drop           Hello Drag And Drop           glimmer sample:run[hello_drag_and_drop]          
+  hello_list_multi_selection    Hello List Multi Selection    glimmer sample:run[hello_list_multi_selection]   
+  hello_list_single_selection   Hello List Single Selection   glimmer sample:run[hello_list_single_selection]  
+  hello_menu_bar                Hello Menu Bar                glimmer sample:run[hello_menu_bar]               
+  hello_message_box             Hello Message Box             glimmer sample:run[hello_message_box]            
+  hello_pop_up_context_menu     Hello Pop Up Context Menu     glimmer sample:run[hello_pop_up_context_menu]    
+  hello_tab                     Hello Tab                     glimmer sample:run[hello_tab]                    
+  hello_world                   Hello World                   glimmer sample:run[hello_world]                  
+                                                                                                               
+
+  Glimmer Elaborate Samples (run all via: glimmer sample:run:elaborate):
+                                                                           
+       Name           Description                     Run                  
+                                                                           
+  contact_manager   Contact Manager   glimmer sample:run[contact_manager]  
+  login             Login             glimmer sample:run[login]            
+  tic_tac_toe       Tic Tac Toe       glimmer sample:run[tic_tac_toe]                                                   
+```
+
+#### Sample Run
+
+A sample may be run via `glimmer sample:run[name]`. This also outputs the sample code so that you could take a look at it and compare to the GUI that launches. 
+
+If the sample name is left empty (e.g. `glimmer sample:run`), then all samples are run.
+
+Example:
+
+```
+glimmer sample:run[hello_tab]
+```
+
+This will run the hello_tab sample and output its code:
+
+```
+$ glimmer sample:run[hello_tab] 
+
+# /Users/User/.rvm/gems/jruby-9.2.13.0@glimmerapp/gems/glimmer-dsl-swt-0.6.5/samples/hello/hello_tab.rb
+
+class HelloTab
+  include Glimmer
+  def launch
+    shell {
+      text "Hello, Tab!"
+      tab_folder {
+        tab_item {
+          text "English"
+          label {
+            text "Hello, World!"
+          }
+        }
+        tab_item {
+          text "French"
+          label {
+            text "Bonjour, Univers!"
+          }
+        }
+      }
+    }.open
+  end
+end
+
+HelloTab.new.launch
+
+# # #
+```
+
+![Hello Tab English](images/glimmer-hello-tab-english.png)
+
+#### Sample Code
+
+You may output any sample code via this command: `glimmer sample:code[name]`
+
+This is very similar to the sample run command, except the name is required.
+
+It will not only output the main sample file, but any required supporting files as well.
+
+Example:
+
+```
+$ glimmer sample:code[tic_tac_toe] 
+
+# /Users/User/.rvm/gems/jruby-9.2.13.0@glimmerapp/gems/glimmer-dsl-swt-0.6.5/samples/elaborate/tic_tac_toe.rb
+
+require_relative "tic_tac_toe/board"
+
+class TicTacToe
+  include Glimmer
+
+  def initialize
+    @tic_tac_toe_board = Board.new
+    @shell = shell {
+      text "Tic-Tac-Toe"
+      minimum_size 150, 178
+      composite {
+        grid_layout 3, true
+        (1..3).each { |row|
+          (1..3).each { |column|
+            button {
+              layout_data :fill, :fill, true, true
+              text        bind(@tic_tac_toe_board[row, column], :sign)
+              enabled     bind(@tic_tac_toe_board[row, column], :empty)
+              font        style: :bold, height: 20
+              on_widget_selected {
+                @tic_tac_toe_board.mark(row, column)
+              }
+            }
+          }
+        }
+      }
+    }
+    observe(@tic_tac_toe_board, :game_status) { |game_status|
+      display_win_message if game_status == Board::WIN
+      display_draw_message if game_status == Board::DRAW
+    }
+  end
+
+  def display_win_message
+    display_game_over_message("Player #{@tic_tac_toe_board.winning_sign} has won!")
+  end
+
+  def display_draw_message
+    display_game_over_message("Draw!")
+  end
+
+  def display_game_over_message(message_text)
+    message_box(@shell) {
+      text 'Game Over'
+      message message_text
+    }.open
+    @tic_tac_toe_board.reset
+  end
+
+  def open
+    @shell.open
+  end
+end
+
+TicTacToe.new.open
+
+# # #
+
+
+# /Users/User/.rvm/gems/jruby-9.2.13.0@glimmerapp/gems/glimmer-dsl-swt-0.6.5/samples/elaborate/tic_tac_toe/cell.rb
+
+class TicTacToe
+  class Cell
+    EMPTY = ""
+    attr_accessor :sign, :empty
+  
+    def initialize
+      reset
+    end
+  
+    def mark(sign)
+      self.sign = sign
+    end
+  
+    def reset
+      self.sign = EMPTY
+    end
+  
+    def sign=(sign_symbol)
+      @sign = sign_symbol
+      self.empty = sign == EMPTY
+    end
+  
+    def marked
+      !empty
+    end
+  end
+end
+
+# # #
+
+
+# /Users/User/.rvm/gems/jruby-9.2.13.0@glimmerapp/gems/glimmer-dsl-swt-0.6.5/samples/elaborate/tic_tac_toe/board.rb
+
+require_relative 'cell'
+
+class TicTacToe
+  class Board
+    DRAW = :draw
+    IN_PROGRESS = :in_progress
+    WIN = :win
+    attr :winning_sign
+    attr_accessor :game_status
+  
+    def initialize
+      @sign_state_machine = {nil => "X", "X" => "O", "O" => "X"}
+      build_grid
+      @winning_sign = Cell::EMPTY
+      @game_status = IN_PROGRESS
+    end
+  
+    #row and column numbers are 1-based
+    def mark(row, column)
+      self[row, column].mark(current_sign)
+      game_over? #updates winning sign
+    end
+  
+    def current_sign
+      @current_sign = @sign_state_machine[@current_sign]
+    end
+  
+    def [](row, column)
+      @grid[row-1][column-1]
+    end
+  
+    def game_over?
+       win? or draw?
+    end
+  
+    def win?
+      win = (row_win? or column_win? or diagonal_win?)
+      self.game_status=WIN if win
+      win
+    end
+  
+    def reset
+      (1..3).each do |row|
+        (1..3).each do |column|
+          self[row, column].reset
+        end
+      end
+      @winning_sign = Cell::EMPTY
+      @current_sign = nil
+      self.game_status=IN_PROGRESS
+    end
+  
+    private
+  
+    def build_grid
+      @grid = []
+      3.times do |row_index| #0-based
+        @grid << []
+        3.times { @grid[row_index] << Cell.new }
+      end
+    end
+  
+    def row_win?
+      (1..3).each do |row|
+        if row_has_same_sign(row)
+          @winning_sign = self[row, 1].sign
+          return true
+        end
+      end
+      false
+    end
+  
+    def column_win?
+      (1..3).each do |column|
+        if column_has_same_sign(column)
+          @winning_sign = self[1, column].sign
+          return true
+        end
+      end
+      false
+    end
+  
+    #needs refactoring if we ever decide to make the board size dynamic
+    def diagonal_win?
+      if (self[1, 1].sign == self[2, 2].sign) and (self[2, 2].sign == self[3, 3].sign) and self[1, 1].marked
+        @winning_sign = self[1, 1].sign
+        return true
+      end
+      if (self[3, 1].sign == self[2, 2].sign) and (self[2, 2].sign == self[1, 3].sign) and self[3, 1].marked
+        @winning_sign = self[3, 1].sign
+        return true
+      end
+      false
+    end
+  
+    def draw?
+      @board_full = true
+      3.times do |x|
+        3.times do |y|
+          @board_full = false if self[x, y].empty
+        end
+      end
+      self.game_status = DRAW if @board_full
+      @board_full
+    end
+  
+    def row_has_same_sign(number)
+      row_sign = self[number, 1].sign
+      [2, 3].each do |column|
+        return false unless row_sign == (self[number, column].sign)
+      end
+      true if self[number, 1].marked
+    end
+  
+    def column_has_same_sign(number)
+      column_sign = self[1, number].sign
+      [2, 3].each do |row|
+        return false unless column_sign == (self[row, number].sign)
+      end
+      true if self[1, number].marked
+    end
+  
+  end
+end
+
+# # #
+```
+
 ### Scaffolding
 
 Glimmer borrows from Rails the idea of Scaffolding, that is generating a structure for your app files that
-helps you get started just like true building scaffolding helps construction workers, civil engineers, and architects.
+helps you get started just like true buildinThis g scaffolding helps construction workers, civil engineers, and architects.
 
 Glimmer scaffolding goes beyond just scaffolding the app files that Rails does. It also packages it and launches it, 
 getting you to a running and delivered state of an advanced "Hello, World!" Glimmer application right off the bat.
 
 This should greatly facilitate building a new Glimmer app by helping you be productive and focus on app details while 
 letting Glimmer scaffolding take care of initial app file structure concerns, such as adding:
-- Main application class that includes Glimmer
-- Main application view that houses main window content, about dialog, and preferences dialog
-- View and Model directories
-- Rakefile including Glimmer tasks
-- Version
-- License
-- Icon
-- Bin file for starting application
+- Main application class that includes Glimmer (`app/{app_name}.rb`)
+- Main application view that houses main window content, menu, about dialog, and preferences dialog
+- View and Model directories (`app/views` and `app/models`)
+- Rakefile including Glimmer tasks (`Rakefile`)
+- Version (`VERSION`)
+- License (`LICENSE.txt`)
+- Icon (under `package/{platform}/{App Name}.{icon_extension}` for `macosx` .icns, `windows` .ico, and `linux` .png)
+- Bin file for starting application (`bin/{app_name}.rb`)
 
-NOTE: Scaffolding requires RVM and currently supports Mac packaging only at the moment. 
+NOTE: Scaffolding supports Mac and Windows packaging at the moment. 
 
 #### App
 
@@ -402,39 +842,77 @@ This will generate an advanced "Hello, World!" app, package it as a Mac native f
 Suppose you run:
 
 ```
-glimmer scaffold[CarMaker]
+glimmer scaffold[greeter]
 ```
 
 You should see output like the following:
 
 ```
-Created CarMaker/.ruby-version
-Created CarMaker/.ruby-gemset
-Created CarMaker/VERSION
-Created CarMaker/LICENSE.txt
-Created CarMaker/Gemfile
-Created CarMaker/Rakefile
-Created CarMaker/app/car_maker.rb
-Created CarMaker/app/views/car_maker/app_view.rb
-Created CarMaker/package/macosx/Car Maker.icns
-Created CarMaker/bin/car_maker
+$ glimmer scaffold[greeter]
+	create	.gitignore
+	create	Rakefile
+	create	Gemfile
+	create	LICENSE.txt
+	create	README.rdoc
+	create	.document
+	create	lib
+	create	lib/greeter.rb
+	create	spec
+	create	spec/spec_helper.rb
+	create	spec/greeter_spec.rb
+	create	.rspec
+Jeweler has prepared your gem in ./greeter
+Created greeter/.gitignore
+Created greeter/.ruby-version
+Created greeter/.ruby-gemset
+Created greeter/VERSION
+Created greeter/LICENSE.txt
+Created greeter/Gemfile
+Created greeter/Rakefile
+Created greeter/app/greeter.rb
+Created greeter/app/views/greeter/app_view.rb
+Created greeter/package/windows/Greeter.ico
+Created greeter/package/macosx/Greeter.icns
+Created greeter/package/linux/Greeter.png
+Created greeter/bin/greeter
+Created greeter/spec/spec_helper.rb
 ...
 ```
 
-Eventually, it will launch an advanced "Hello, World!" app window having the title of your application and a Mac icon.
+Eventually, it will launch an advanced "Hello, World!" app window having the title of your application ("Greeter").
 
 ![Glimmer Scaffold App](images/glimmer-scaffolding-app.png)
 
-On the Mac, it also comes with a boilerplate Preferences dialog.
+It also comes with a boilerplate Preferences dialog.
 
 ![Glimmer Scaffold App Preferences](images/glimmer-scaffolding-app-preferences.png)
 
+Here is the Windows version of the scaffolded "Greeter" app:
+
+![Glimmer Scaffold App Windows](images/glimmer-scaffolding-app-windows.png)
+
+And, here is the Windows version of the boilerplate Preferences dialog.
+
+![Glimmer Scaffold App Windows Preferences](images/glimmer-scaffolding-app-windows-preferences.png)
+
+In order to run the app after making changes, you must run the `glimmer` command and pass it the generated script under the `bin` directory as an argument:
+
+```
+glimmer bin/greeter
+```
+
 #### Custom Shell
 
 To scaffold a Glimmer custom shell (full window view) for an existing Glimmer app, run the following command:
 
 ```
-glimmer scaffold:custom_shell[custom_shell_name]
+glimmer scaffold:customshell[name]
+```
+
+Or the following alternative abbreviation:
+
+```
+glimmer scaffold:cs[name]
 ```
 
 #### Custom Widget
@@ -442,13 +920,19 @@ glimmer scaffold:custom_shell[custom_shell_name]
 To scaffold a Glimmer custom widget (part of a view) for an existing Glimmer app, run the following command:
 
 ```
-glimmer scaffold:custom_widget[custom_widget_name]
+glimmer scaffold:customwidget[name]
+```
+
+Or the following alternative abbreviation:
+
+```
+glimmer scaffold:cw[name]
 ```
 
 #### Custom Shell Gem
 
 Custom shell gems are self-contained Glimmer apps as well as reusable custom shells. 
-They have everything scaffolded Glimmer apps come with in addition to gem content like a Jeweler Rakefile that can build gemspec and release gems. 
+They have everything scaffolded Glimmer apps come with in addition to gem content like a [jeweler](https://github.com/technicalpickles/jeweler) Rakefile that can build gemspec and release gems. 
 Unlike scaffolded Glimmer apps, custom shell gem content lives under the `lib` directory (not `app`).
 They can be packaged as both a native executable (e.g. Mac DMG/PKG/APP) and a Ruby gem.
 Of course, you can just build a Ruby gem and disregard native executable packaging if you do not need it.
@@ -456,7 +940,13 @@ Of course, you can just build a Ruby gem and disregard native executable packagi
 To scaffold a Glimmer custom shell gem (full window view distributed as a Ruby gem), run the following command:
 
 ```
-glimmer scaffold:custom_shell_gem[custom_shell_name, namespace]
+glimmer scaffold:gem:customshell[name,namespace]
+```
+
+Or the following alternative abbreviation:
+
+```
+glimmer scaffold:gem:cs[name,namespace]
 ```
 
 It is important to specify a namespace to avoid having your gem clash with existing gems.
@@ -465,6 +955,10 @@ The Ruby gem name will follow the convention "glimmer-cs-customwidgetname-namesp
 
 Only official Glimmer gems created by the Glimmer project committers will have no namespace (e.g. [glimmer-cs-gladiator](https://rubygems.org/gems/glimmer-cs-gladiator) Ruby gem)
 
+Since custom shell gems are both an app and a gem, they provide two ways to run:
+- Run the `glimmer` command and pass it the generated script under the `bin` directory that matches the gem name (e.g. run `glimmer bin/glimmer-cs-calculator`)
+- Run the executable binary file that ships with the gem directly (without `glimmer`). It intentionally has a shorter name for convenience since it is meant to be used on the command line (not in a package), so you can leave out the `glimmer-cs-` prefix (e.g. run `bin/calculator` directly)
+
 Examples: 
 
 - [glimmer-cs-gladiator](https://github.com/AndyObtiva/glimmer-cs-gladiator): Gladiator (Glimmer Editor)
@@ -475,16 +969,26 @@ Examples:
 To scaffold a Glimmer custom widget gem (part of a view distributed as a Ruby gem), run the following command:
 
 ```
-glimmer scaffold:custom_widget_gem[custom_widget_name, namespace]
+glimmer scaffold:gem:customwidget[name,namespace]
 ```
 
+Or the following alternative abbreviation:
+
+```
+glimmer scaffold:gem:cw[name,namespace]
+```
+
+
 It is important to specify a namespace to avoid having your gem clash with existing gems.
 
 The Ruby gem name will follow the convention "glimmer-cw-customwidgetname-namespace" (the 'cw' is for Custom Widget)
 
 Only official Glimmer gems created by the Glimmer project committers will have no namespace (e.g. [glimmer-cw-video](https://rubygems.org/gems/glimmer-cw-video) Ruby gem)
 
-Example: [https://github.com/AndyObtiva/glimmer-cw-video](https://github.com/AndyObtiva/glimmer-cw-video)
+Examples: 
+
+- [glimmer-cw-video](https://github.com/AndyObtiva/glimmer-cw-video): Video Widget
+- [glimmer-cw-cdatetime-nebula](https://github.com/AndyObtiva/glimmer-cw-cdatetime-nebula): Nebula CDateTime Widget
 
 ### Gem Listing
 
@@ -495,13 +999,19 @@ The `glimmer` command comes with tasks for listing Glimmer related gems to make
 The following command lists available Glimmer [Custom Shell Gems](#custom-shell-gem) (prefixed with "glimmer-cs-" by scaffolding convention) created by the the Glimmer community and published on [rubygems.org](http://www.rubygems.org):
 
 ```
-glimmer list:custom_shell_gems[query]                             # List Glimmer custom shell gems available at rubygems.org (query is optional)
+glimmer list:gems:customshell[query]
+```
+
+Or the following alternative abbreviation:
+
+```
+glimmer list:gems:cs[query]
 ```
 
 Example:
 
 ```
-glimmer list:custom_shell_gems
+glimmer list:gems:cs
 ```
 
 Output:
@@ -512,8 +1022,9 @@ Output:
                                                                                                                  
      Name               Gem            Version     Author                        Description                     
                                                                                                                  
-  Calculator   glimmer-cs-calculator   1.0.1     Andy Maleh   Calculator - Glimmer Custom Shell                  
-  Gladiator    glimmer-cs-gladiator    0.2.0     Andy Maleh   Gladiator (Glimmer Editor) - Glimmer Custom Shell  
+  Calculator   glimmer-cs-calculator   1.0.2     Andy Maleh   Calculator - Glimmer Custom Shell                   
+  Gladiator    glimmer-cs-gladiator    0.2.4     Andy Maleh   Gladiator (Glimmer Editor) - Glimmer Custom Shell   
+  Timer        glimmer-cs-timer        1.0.0     Andy Maleh   Timer - Glimmer Custom Shell               
                                                                                                                  
 ```
 
@@ -522,7 +1033,13 @@ Output:
 The following command lists available Glimmer [Custom Widget Gems](#custom-widget-gem) (prefixed with "glimmer-cw-" by scaffolding convention) created by the the Glimmer community and published on [rubygems.org](http://www.rubygems.org):
 
 ```
-glimmer list:custom_widget_gems[query]                            # List Glimmer custom widget gems available at rubygems.org (query is optional)
+glimmer list:gems:customwidget[query]
+```
+
+Or the following alternative abbreviation:
+
+```
+glimmer list:gems:cw[query]
 ```
 
 Example:
@@ -530,7 +1047,7 @@ Example:
 Check if there is a custom video widget for Glimmer.
 
 ```
-glimmer list:custom_widget_gems[video]
+glimmer list:gems:cw[video]
 ```
 
 Output:
@@ -541,7 +1058,7 @@ Output:
                                                                                    
   Name          Gem          Version     Author              Description           
                                                                                    
-  Video   glimmer-cw-video   0.1.1     Andy Maleh   Glimmer Custom Widget - Video  
+  Video   glimmer-cw-video   0.1.3     Andy Maleh   Glimmer Custom Widget - Video  
                                                                                    
 ```
 
@@ -550,13 +1067,13 @@ Output:
 The following command lists available Glimmer [DSL Gems](#multi-dsl-support) (prefixed with "glimmer-dsl-" by convention) created by the the Glimmer community and published on [rubygems.org](http://www.rubygems.org):
 
 ```
-glimmer list:dsl_gems[query]                                      # List Glimmer DSL gems available at rubygems.org (query is optional)
+glimmer list:gems:dsl[query]
 ```
 
 Example:
 
 ```
-glimmer list:dsl_gems
+glimmer list:gems:dsl
 ```
 
 Output:
@@ -567,10 +1084,10 @@ Output:
                                                                          
   Name         Gem          Version    Author          Description       
                                                                          
-  Css    glimmer-dsl-css    0.1.0     AndyMaleh   Glimmer DSL for CSS    
-  Opal   glimmer-dsl-opal   0.0.9     AndyMaleh   Glimmer DSL for Opal   
-  Swt    glimmer-dsl-swt    0.3.0     AndyMaleh   Glimmer DSL for SWT    
-  Xml    glimmer-dsl-xml    0.1.0     AndyMaleh   Glimmer DSL for XML    
+  Css    glimmer-dsl-css    0.2.0     AndyMaleh   Glimmer DSL for CSS    
+  Opal   glimmer-dsl-opal   0.1.0     AndyMaleh   Glimmer DSL for Opal   
+  Swt    glimmer-dsl-swt    0.6.5     AndyMaleh   Glimmer DSL for SWT    
+  Xml    glimmer-dsl-xml    0.2.0     AndyMaleh   Glimmer DSL for XML    
                                                                          
 ```
 
@@ -623,15 +1140,76 @@ Watch out for hands-on examples in this README indicated by "you may copy/paste
 
 Keep in mind that all samples live under [https://github.com/AndyObtiva/glimmer-dsl-swt](https://github.com/AndyObtiva/glimmer-dsl-swt)
 
-## Glimmer DSL Syntax
+## Glimmer GUI DSL Syntax
 
-Glimmer DSL syntax consists of static keywords and dynamic keywords to build and bind user-interface objects.
+Glimmer's core is a GUI DSL with a lightweight visual syntax that makes it easy to visualize the nesting of widgets in the GUI hierarchy tree.
 
-Static keywords are pre-identified keywords in the Glimmer DSL, such as `shell`, `message_box`, `async_exec`, and `bind`.
+It is available through mixing in the `Glimmer` module, which makes Glimmer GUI DSL keywords available to both the instance scope and class scope:
 
-Dynamic keywords are dynamically figured out from available SWT widgets, custom widgets, and properties. Examples are: `label`, `combo`, and `list`.
+```ruby
+include Glimmer
+```
 
-The only reason to distinguish between the two types of Glimmer DSL keywords is to realize that importing new Glimmer [custom widgets](#custom-widgets) and Java SWT custom widget libraries automatically expands Glimmer's DSL vocabulary via new dynamic keywords.
+For example, here is the basic "Hello, World!" sample code (you may copy/paste in [`girb`](#girb-glimmer-irb-command)):
+
+```ruby
+include Glimmer
+
+shell {
+  text "Glimmer"
+  label {
+    text "Hello, World!"
+  }
+}.open
+```
+
+The `include Glimmer` declaration on top mixed the `Glimmer` module into the Ruby global main object making the Glimmer GUI DSL available at the top-level global scope.
+
+While this works well enough for mini-samples, it is better to isolate Glimmer in a class or module during production application development to create a clean separation between view code (GUI) and model code (business domain). Here is the "Hello, World!" sample re-written in a class to illustrate how mixing in the `Glimmer` module (via `include Glimmer`) makes the Glimmer GUI DSL available in both the instance scope and class scope. That is clearly demonstrated by pre-initializing a color constant in the class scope and building the GUI in the `#open` instance method (you may copy/paste in [`girb`](#girb-glimmer-irb-command)):
+
+```ruby
+class HelloWorld
+  include Glimmer # makes the GUI DSL available in both the class scope and instance scope
+  
+  COLOR_FOREGROUND_DEFAULT = rgb(255, 0, 0) # rgb is a GUI DSL keyword used in the class scope
+  
+  def open
+    # the following are GUI DSL keywords (shell, text, and label) used in the instance scope
+    shell {
+      text "Glimmer"
+      label {
+        text "Hello, World!"
+        foreground COLOR_FOREGROUND_DEFAULT
+      }
+    }.open
+  end
+end
+
+HelloWorld.new.open
+```
+
+This renders "Hello, World!" with a red foreground color:
+
+![Hello World Red Foreground Color](images/glimmer-hello-world-red-foreground-color.png)
+
+The GUI DSL intentionally avoids overly verbose syntax, requiring as little declarative code as possible to describe what GUI to render, how to style it, and what properties to data-bind to the Models.
+
+As such, it breaks off from Ruby's convention of using `do end` for multi-line blocks, opting instead for the lightweight and visual `{ }` curly brace blocks everywhere inside the GUI DSL. More details about Glimmer's syntax conventions may be found in the [Glimmer Style Guide](#glimmer-style-guide)
+
+Glimmer DSL syntax consists mainly of:
+- keywords (e.g. `table` for a table widget)
+- style/args (e.g. :multi as in `table(:multi)` for a multi-line selection table widget)
+- content (e.g. `{ table_column { text 'Name'} }` as in `table(:multi) { table_column { text 'name'} }` for a multi-line selection table widget with a table column having header text property `'Name'` as content)
+
+### DSL Auto-Expansion
+
+Glimmer supports a new and radical Ruby DSL concept called DSL Auto-Expansion. It is explained by first mentioning the two types of Glimmer GUI DSL keywords: static and dynamic.
+
+Static keywords are pre-identified keywords in the Glimmer DSL, such as `shell`, `display`, `message_box`, `async_exec`, `sync_exec`, and `bind`.
+
+Dynamic keywords are dynamically figured out from currently imported (aka required/loaded) SWT widgets, custom widgets, and widget properties. Examples are: `label`, `combo`, and `list` for widgets and `enabled`, `text`, and `selection` for properties.
+
+The only reason to distinguish between the two types of Glimmer DSL keywords is to realize that importing new Glimmer [custom widgets](#custom-widgets) and Java SWT custom widget libraries automatically expands Glimmer's DSL vocabulary via new dynamic keywords. 
 
 For example, if a project adds this custom Java SWT library:
 
@@ -649,9 +1227,9 @@ https://www.eclipse.org/swt/widgets/
 
 This screenshot taken from the link above should give a glimpse of how SWT widgets look and feel:
 
-![SWT Widgets](images/glimmer-swt-widgets.png)
+[![SWT Widgets](images/glimmer-swt-widgets.png)](https://www.eclipse.org/swt/widgets/)
 
-In Glimmer DSL, widgets are declared with lowercase underscored names mirroring their SWT names minus the package name:
+In Glimmer DSL, widgets are declared with lowercase underscored names mirroring their SWT names minus the package name. For example, here are some Glimmer widgets and their SWT counterparts:
 
 - `shell` instantiates `org.eclipse.swt.widgets.Shell`
 - `text` instantiates `org.eclipse.swt.widgets.Text`
@@ -667,8 +1245,8 @@ In Glimmer DSL, widgets are declared with lowercase underscored names mirroring
 - `list` instantiates `org.eclipse.swt.widgets.List`
 
 Every **widget** is sufficiently declared by name, but may optionally be accompanied with:
-- SWT **style** ***argument*** wrapped by parenthesis according to [Glimmer Style Guide](#glimmer-style-guide) (see [next section](#widget-styles) for details).
-- Ruby block containing **properties** (widget attributes) and **content** (nested widgets)
+- SWT **style**/***arguments*** wrapped by parenthesis according to [Glimmer Style Guide](#glimmer-style-guide) (see [next section](#widget-styles) for details).
+- Ruby block containing **content**, which may be **properties** (e.g. `enabled false`) or nested **widgets** (e.g. `table_column` nested inside `table`)
 
 For example, if we were to revisit `samples/hello/hello_world.rb` above (you may copy/paste in [`girb`](#girb-glimmer-irb-command)):
 
@@ -750,6 +1328,8 @@ shell {
 }.open
 ```
 
+If you are new to Glimmer, you have learned enough to start running some [samples](#samples). Go ahead and run all Glimmer [samples](#samples), and come back to read the rest in any order you like since this material is more organized like a reference.
+
 #### Display
 
 SWT Display is a singleton in Glimmer. It is used in SWT to represent your display device, allowing you to manage GUI globally 
@@ -761,7 +1341,7 @@ automatically uses the display created earlier without having to explicitly hook
 ```ruby
 @display = display {
   cursor_location 300, 300
-  on_event_keydown {
+  on_swt_keydown {
     # ...
   }
   # ...
@@ -837,6 +1417,21 @@ include Glimmer
 @shell.open
 ```
 
+![Hello Message Box Dialog](images/glimmer-hello-message-box-dialog.png)
+
+It is also possible to use `message_box` even before instantiating the first `shell` ([Glimmer](https://rubygems.org/gems/glimmer) builds a throwaway `shell` parent automatically for it):
+
+Example (you may copy/paste in [`girb`](#girb-glimmer-irb-command)):
+
+```ruby
+include Glimmer
+
+message_box {
+  text 'Greeting'
+  message "Hello, World!"
+}.open
+```
+
 ##### `#swt_widget`
 
 Glimmer widget objects come with an instance method `#swt_widget` that returns the actual SWT `Widget` object wrapped by the Glimmer widget object. It is useful in cases you'd like to do some custom SWT programming outside of Glimmer.
@@ -856,6 +1451,24 @@ Shell widget proxy has extra methods specific to SWT Shell:
 - `#pack`: Packs contained widgets using SWT's `Shell#pack` method
 - `#pack_same_size`: Packs contained widgets without changing shell's size when widget sizes change
 
+##### Shell Icon
+
+To set the shell icon, simply set the `image` property under the `shell` widget. This shows up in the operating system toolbar and app-switcher (e.g. CMD+TAB) (and application window top-left corner in Windows)
+
+Example:
+
+```ruby
+shell {
+  # ...
+  image 'path/to/image.png'
+  # ...
+}
+```
+
+###### Shell Icon Tip for Packaging on Windows
+
+When setting shell icon for a [packaged](#packaging--distribution) app, which has a JAR file at its core, you can reference the `ico` file that ships with the app by going one level up (e.g. `'../AppName.ico'`)
+
 #### Dialog
 
 Dialog is a variation on Shell. It is basically a shell that is modal (blocks what's behind it) and belongs to another shell. It only has a close button.
@@ -1031,7 +1644,7 @@ text(:center, :border) { # Multiple SWT styles separated by comma
 Glimmer ships with SWT style **smart defaults** so you wouldn't have to set them yourself most of the time (albeit you can always override them):
 
 - `text(:border)`
-- `table(:border)`
+- `table(:border, :virtual, :full_selection)`
 - `tree(:border, :virtual, :v_scroll, :h_scroll)`
 - `spinner(:border)`
 - `list(:border, :v_scroll)`
@@ -1107,7 +1720,7 @@ button {
 
 In the above example, the `text` widget `enabled` property was data-bound to `#empty` method on `@tic_tac_toe_board.box(row, column)` (learn more about data-binding below)
 
-#### Colors
+#### Color
 
 Colors make up a subset of widget properties. SWT accepts color objects created with RGB (Red Green Blue) or RGBA (Red Green Blue Alpha). Glimmer supports constructing color objects using the `rgb` and `rgba` DSL keywords.
 
@@ -1156,7 +1769,7 @@ Example:
 color(:black).swt_color # returns SWT Color object
 ```
 
-#### Fonts
+#### Font
 
 Fonts are represented in Glimmer as a hash of name, height, and style keys.
 
@@ -1185,6 +1798,33 @@ label {
 # ...
 ```
 
+You may simply use the standalone `font` keyword without nesting in a parent if there is a need to build a Font object to use in manual SWT programming outside of widget font property setting.
+
+Example:
+
+```ruby
+@font = font(name: 'Arial', height: 36, style: :normal)
+```
+
+### Cursor
+
+SWT widget `cursor` property represents the mouse cursor you see on the screen when you hover over that widget.
+
+The `Display` class provides a way to obtain standard system cursors matching of the SWT style constants starting with prefix `CURSOR_` (e.g. `SWT::CURSOR_HELP` shows a question mark mouse cursor)
+
+Glimmer provides an easier way to obtain and set `cursor` property on a widget by simply mentioning the SWT style constant as an abbreviated symbol excluding the "CURSOR_" suffix.
+
+Example:
+
+```ruby
+shell {
+  minimum_size 128, 128                        
+  cursor :appstarting
+}
+```
+
+This sets the shell `cursor` to that of `SWT::CURSOR_APPSTARTING`
+
 ### Layouts
 
 Glimmer lays widgets out visually using SWT layouts, which can only be set on composite widget and subclasses.
@@ -1721,10 +2361,10 @@ Glimmer comes with `Observer` module, which is used internally for data-binding,
 
 Glimmer supports observing widgets with two main types of events:
 1. `on_{swt-listener-method-name}`: where {swt-listener-method-name} is replaced with the lowercase underscored event method name on an SWT listener class (e.g. `on_verify_text` for `org.eclipse.swt.events.VerifyListener#verifyText`).
-2. `on_event_{swt-event-constant}`: where {swt-event-constant} is replaced with an `org.eclipse.swt.SWT` event constant (e.g. `on_event_show` for `SWT.Show` to observe when widget becomes visible)
+2. `on_swt_{swt-event-constant}`: where {swt-event-constant} is replaced with an [`org.eclipse.swt.SWT`](https://help.eclipse.org/2020-06/topic/org.eclipse.platform.doc.isv/reference/api/org/eclipse/swt/SWT.html) event constant (e.g. `on_swt_show` for `SWT.Show` to observe when widget becomes visible)
 
 Additionally, there are two more types of events:
-- SWT `display` supports global listeners called filters that run on any widget. They are hooked via `on_event_{swt-event-constant}`
+- SWT `display` supports global listeners called filters that run on any widget. They are hooked via `on_swt_{swt-event-constant}`
 - SWT `display` supports Mac application menu item observers (`on_about` and `on_preferences`), which you can read about under [Miscellaneous](#miscellaneous).
 
 Number 1 is more commonly used in SWT applications, so make it your starting point. Number 2 covers events not found in number 1, so look into it if you don't find an SWT listener you need in number 1.
@@ -1747,7 +2387,8 @@ Let's revisit the Tic Tac Toe example shown near the beginning of the page:
 ```ruby
 shell {
   text "Tic-Tac-Toe"
-  composite {
+  minimum_size 150, 178
+  composite {  
     grid_layout 3, true
     (1..3).each { |row|
       (1..3).each { |column|
@@ -1769,21 +2410,21 @@ Note that every Tic Tac Toe grid cell has its `text` and `enabled` properties da
 
 Next however, each of these Tic Tac Toe grid cells, which are clickable buttons, have an `on_widget_selected` observer, which once triggered, marks the cell on the `TicTacToe::Board` to make a move.
 
-**Regarding number 2**, you can figure out all available events by looking at the `org.eclipse.swt.SWT` API:
+**Regarding number 2**, you can figure out all available events by looking at the [`org.eclipse.swt.SWT`](https://help.eclipse.org/2020-06/topic/org.eclipse.platform.doc.isv/reference/api/org/eclipse/swt/SWT.html) API:
 
 https://help.eclipse.org/2019-12/nftopic/org.eclipse.platform.doc.isv/reference/api/org/eclipse/swt/SWT.html
 
 Example (you may copy/paste in [`girb`](#girb-glimmer-irb-command)):
 
-`SWT.Show` - hooks a listener for showing a widget (using `on_event_show` in Glimmer)
-`SWT.Hide` - hooks a listener for hiding a widget (using `on_event_hide` in Glimmer)
+`SWT.Show` - hooks a listener for showing a widget (using `on_swt_show` in Glimmer)
+`SWT.Hide` - hooks a listener for hiding a widget (using `on_swt_hide` in Glimmer)
 
 ```ruby
 shell {
   @button1 = button {
     text "Show 2nd Button"
     visible true
-    on_event_show {
+    on_swt_show {
       @button2.swt_widget.setVisible(false)
     }
     on_widget_selected {
@@ -1793,7 +2434,7 @@ shell {
   @button2 = button {
     text "Show 1st Button"
     visible false
-    on_event_show {
+    on_swt_show {
       @button1.swt_widget.setVisible(false)
     }
     on_widget_selected {
@@ -1803,7 +2444,7 @@ shell {
 }.open
 ```
 
-**Gotcha:** SWT.Resize event needs to be hooked using **`on_event_Resize`** because `org.eclipse.swt.SWT` has 2 constants for resize: `RESIZE` and `Resize`, so it cannot infer the right one automatically from the underscored version `on_event_resize`
+**Gotcha:** SWT.Resize event needs to be hooked using **`on_swt_Resize`** because [`org.eclipse.swt.SWT`](https://help.eclipse.org/2020-06/topic/org.eclipse.platform.doc.isv/reference/api/org/eclipse/swt/SWT.html) has 2 constants for resize: `RESIZE` and `Resize`, so it cannot infer the right one automatically from the underscored version `on_swt_resize`
 
 ##### Alternative Syntax
 
@@ -2097,7 +2738,7 @@ shell { |app_shell|
   @current_step_number = 1
   @wizard_steps = 5.times.map { |n|
     wizard_step(number: n+1, step_count: 5) {
-      on_event_hide {
+      on_swt_hide {
         if @current_step_number < 5
           @current_step_number += 1
           app_shell.hide
@@ -2397,7 +3038,7 @@ Also, you may invoke `Display.setAppVersion('1.0.0')` if needed for OS app versi
 
 #### Video Widget
 
-![Video Widget](images/glimmer-video-widget.png)
+[![Video Widget](images/glimmer-video-widget.png)](https://github.com/AndyObtiva/glimmer-cw-video)
 
 Glimmer supports a [video custom widget](https://github.com/AndyObtiva/glimmer-cw-video) not in SWT. 
 
@@ -2449,17 +3090,14 @@ Glimmer configuration may be done via the `Glimmer::Config` module.
 
 ### logger
 
-Glimmer supports logging via a Ruby Logger configurable with the `Glimmer::Config.logger` config option.
-It is disabled by default to ensure not affecting desktop app performance.
-It may be enabled via `Glimmer::Config.enable_logging`
-When enabled, the Glimmer logger level defaults to `:warn` (aka `Logger::WARN`)
-It may be configured to show a different level of logging via `Glimmer::Config.logger.level` just ike with any Ruby Logger.
+The Glimmer DSL engine supports logging via a standard `STDOUT` Ruby `Logger` configured in the `Glimmer::Config.logger` config option.
+It is set to level Logger::ERROR by default. 
+Log level may be adjusted via `Glimmer::Config.logger.level` just like any other Ruby Logger.
 
 Example:
 
 ```ruby
-Glimmer::Config.enable_logging
-Glimmer::Config.logger.level = Logger::DEBUG
+Glimmer::Config.logger.level = :debug
 ```
 This results in more verbose debug loggging to `STDOUT`, which is very helpful in troubleshooting Glimmer DSL syntax when needed.
 
@@ -2479,6 +3117,55 @@ D, [2017-07-21T19:23:12.878434 #35707] DEBUG -- : WidgetCommandHandler will hand
 D, [2017-07-21T19:23:12.878798 #35707] DEBUG -- : widget styles are: [:multi]
 ```
 
+The `logger` instance may be replaced with a custom logger via `Glimmer::Config.logger = custom_logger`
+
+To reset `logger` to the default instance, you may call `Glimmer::Config.reset_logger!`
+
+All logging is done lazily via blocks (e.g. `logger.debug {message}`) to avoid affecting app performance with logging when below the configured logging level threshold.
+
+[Glimmer DSL for SWT](https://github.com/AndyObtiva/glimmer-dsl-swt) enhances Glimmer default logging support via the Ruby [`logging`](https://github.com/TwP/logging) gem, enabling buffered asynchronous logging in a separate thread, thus completely unhindering normal desktop app performance.
+
+Other config options related to the [`logging`](https://github.com/TwP/logging) gem are mentioned below.
+
+#### logging_devices
+
+This is an array of these possible values: `:stdout` (default), `:stderr`, `:file`, `:syslog` (default), `:stringio`
+
+It defaults to `[:stdout, :syslog]`
+
+When `:file` is included, Glimmer creates a 'log' directory directly below the Glimmer app local directory. 
+It may also be customized further via the `logging_device_file_options` option.
+This is useful on Windows as an alternative to `syslog`, which is not available on Windows by default.
+
+#### logging_device_file_options
+
+This is a hash of [`logging`](https://github.com/TwP/logging) gem options for the `:file` logging device. 
+
+Default: `{size: 1_000_000, age: 'daily', roll_by: 'number'}`
+
+That ensures splitting log files at the 1MB size and daily, rolling them by unique number.
+
+#### logging_appender_options
+
+Appender options is a hash passed as options to every appender (logging device) used in the [`logging`](https://github.com/TwP/logging) gem.
+
+Default: `{async: true, auto_flushing: 500, write_size: 500, flush_period: 60, immediate_at: [:error, :fatal], layout: logging_layout}`
+
+That ensures asynchronous buffered logging that is flushed every 500 messages and 60 seconds, or immediately at error and fatal log levels
+
+#### logging_layout
+
+This is a [`logging`](https://github.com/TwP/logging) gem layout that formats the logging output.
+
+Default: 
+
+```
+Logging.layouts.pattern(
+  pattern: '[%d] %-5l %c: %m\n',
+  date_pattern: '%Y-%m-%d %H:%M:%S'
+)
+```
+
 ### import_swt_packages
 
 Glimmer automatically imports all SWT Java packages upon adding `include Glimmer`, `include Glimmer::UI::CustomWidget`, or `include Glimmer::UI::CustomShell` to a class or module. It relies on JRuby's `include_package` for lazy-importing upon first reference of a Java class.
@@ -2538,6 +3225,33 @@ The max limit can be changed via the `Glimmer::Config::loop_max_count=(count)` c
 
 Infinite loop detection may be disabled altogether if needed by setting `Glimmer::Config::loop_max_count` to `-1`
 
+### excluded_keyword_checkers
+
+Glimmer permits consumers to exclude keywords from DSL processing by its engine via the `excluded_keyword_checkers` config option.
+
+To do so, add a proc to it that returns a boolean indicating if a keyword is excluded or not.
+
+Note that this proc runs within the context of the Glimmer object (as in the object mixing in the Glimmer module), so checker can can pretend to run there with its `self` object assumption.
+
+Example of keywords excluded by [glimmer-dsl-swt](https://github.com/AndyObtiva/glimmer-dsl-swt):
+
+```ruby
+Glimmer::Config.excluded_keyword_checkers << lambda do |method_symbol, *args|
+  method = method_symbol.to_s
+  result = false
+  result ||= method.start_with?('on_swt_') && is_a?(Glimmer::UI::CustomWidget) && respond_to?(method)
+  result ||= method == 'dispose' && is_a?(Glimmer::UI::CustomWidget) && respond_to?(method)
+  result ||= ['drag_source_proxy', 'drop_target_proxy'].include?(method) && is_a?(Glimmer::UI::CustomWidget)
+  result ||= method == 'post_initialize_child'
+  result ||= method.end_with?('=')
+  result ||= ['finish_edit!', 'search', 'all_tree_items', 'depth_first_search'].include?(method) && is_a?(Glimmer::UI::CustomWidget) && body_root.respond_to?(method)
+end
+```
+
+### log_excluded_keywords
+
+This just tells Glimmer whether to log excluded keywords or not (at the debug level). It is off by default.
+
 ## Glimmer Style Guide
 
 - Widgets are declared with underscored lowercase versions of their SWT names minus the SWT package name.
@@ -2805,6 +3519,8 @@ This sample demonstrates a full MVC application, including GUI layout, text and
 
 Code:
 
+(Please note that on some Linux instances where the display x-axis is set to double-scale, you need to set the `shell` `minimum_size` to `300, 178` instead of `150, 178`)
+
 [samples/elaborate/tic_tac_toe.rb](https://github.com/AndyObtiva/glimmer-dsl-swt/blob/master/samples/elaborate/tic_tac_toe.rb)
 
 Run:
@@ -2817,7 +3533,7 @@ glimmer samples/elaborate/tic_tac_toe.rb
 ![Tic Tac Toe In Progress](images/glimmer-tic-tac-toe-in-progress.png)
 ![Tic Tac Toe Game Over](images/glimmer-tic-tac-toe-game-over.png)
 
-#### Contact Manager
+#### Contact Manager Sample
 
 This sample demonstrates table data-binding, sorting, filtering, GUI layout, MVP pattern, and test-driven development (has [specs](https://github.com/AndyObtiva/glimmer-dsl-swt/blob/master/spec/samples/elaborate/contact_manager/contact_manager_presenter_spec.rb)).
 
@@ -2855,7 +3571,7 @@ Contact Manager - Edit Done
 
 #### Glimmer Calculator
 
-[<img alt="Glimmer Calculator Icon" src="https://raw.githubusercontent.com/AndyObtiva/glimmer-cs-calculator/master/glimmer-cs-calculator-icon.png" height=40 /> Glimmer Calculator](https://github.com/AndyObtiva/glimmer-cs-calculator) is a basic calculator sample project demonstrating data-binding and TDD (test-driven-development) with Glimmer following the MVP pattern (Model-View-Presenter).
+[<img alt="Glimmer Calculator Icon" src="https://raw.githubusercontent.com/AndyObtiva/glimmer-cs-calculator/master/glimmer-cs-calculator-icon.png" height=40 /> Glimmer Calculator](https://github.com/AndyObtiva/glimmer-cs-calculator) is a basic calculator sample app demonstrating data-binding and TDD (test-driven-development) with Glimmer following the MVP pattern (Model-View-Presenter).
 
 [<img src="https://raw.githubusercontent.com/AndyObtiva/glimmer-cs-calculator/master/glimmer-cs-calculator-screenshot.png" />](https://github.com/AndyObtiva/glimmer-cs-calculator)
 
@@ -2876,10 +3592,18 @@ Gladiator is a good demonstration of:
 - Custom Shell
 - Custom widget
 
+#### Timer
+
+[<img alt="Glimmer Timer Icon" src="https://raw.githubusercontent.com/AndyObtiva/glimmer-cs-timer/master/images/glimmer-timer-logo.png" height=40 /> Timer](https://github.com/AndyObtiva/glimmer-cs-timer) is a sample app demonstrating data-binding and multi-threading in a desktop application.
+
+[<img src="https://raw.githubusercontent.com/AndyObtiva/glimmer-cs-timer/master/glimmer-timer-screenshot.png" />](https://github.com/AndyObtiva/glimmer-cs-timer)
+
 ## In Production
 
 The following production apps have been built with Glimmer.
 
+If you have a Glimmer app you would like referenced here, please mention in a Pull Request. 
+
 ### Math Bowling
 
 [<img alt="Math Bowling Logo" src="https://raw.githubusercontent.com/AndyObtiva/MathBowling/master/images/math-bowling-logo.png" width="40" />Math Bowling](https://github.com/AndyObtiva/MathBowling): an educational math game for elementary level kids
@@ -2888,23 +3612,45 @@ The following production apps have been built with Glimmer.
 
 [<img alt="Are We There Yet Logo" src="https://raw.githubusercontent.com/AndyObtiva/are-we-there-yet/master/are-we-there-yet-logo.svg" width="40" />Are We There Yet?](https://github.com/AndyObtiva/are-we-there-yet): A tool that helps you learn when your small projects will finish
 
-If you have a Glimmer app you would like referenced here, please mention in a Pull Request. 
+### Garderie Rainbow Daily Agenda
 
-## Packaging & Distribution
+[<img alt="Garderie Rainbow Daily Agenda Logo" src="https://github.com/AndyObtiva/garderie_rainbow_daily_agenda/raw/master/images/garderie_rainbow_daily_agenda_logo.png" width="40" />Garderie Rainbow Daily Agenda](https://github.com/AndyObtiva/garderie_rainbow_daily_agenda): A child nursery daily agenda reporting desktop app
 
-Glimmer apps may be packaged and distributed on the Mac, Windows, and Linux via these tools:
-- Warbler (https://github.com/jruby/warbler): Enables bundling a Glimmer app into a JAR file
-- javapackager (https://docs.oracle.com/javase/8/docs/technotes/tools/unix/javapackager.html): Enables packaging a JAR file as a DMG file on Mac, EXE on Windows, and multiple Linux supported formats on Linux.
+## Packaging & Distribution
 
-Glimmer simplifies the process of Mac packaging via the `glimmer package` command. It works out of the box for any application generated by [Glimmer Scaffolding](#scaffolding):
+Glimmer simplifies the process of native-executable packaging and distribution on Mac and Windows via a single `glimmer package` command:
 
 ```
 glimmer package
 ```
 
-This will automatically generate a JAR file under `./dist` directory using Warbler, which is then used to automatically generate a DMG file (and pkg/app) under `./packages/bundles` using `javapackager`. 
-JAR file name will match your application local directory name (e.g. `MathBowling.jar` for `~/code/MathBowling`)
-DMG file name will match the humanized local directory name + dash + application version (e.g. `Math Bowling-1.0.dmg` for `~/code/MathBowling` with version 1.0 or unspecified)
+It works out of the box for any application scaffolded by [Glimmer Scaffolding](#scaffolding), generating all available packaging types on the current platform (e.g. `DMG`, `PKG`, `APP` on the Mac) and displaying a message indicating what pre-requisite setup tools are needed if not installed already (e.g. [Wix Toolset](https://wixtoolset.org/) to generate MSI files on Windows)
+
+You may choose to generate a specific type of packaging instead by addionally passing in the `[type]` option. For example, this generates an MSI setup file on Windows:
+
+```
+glimmer package[msi]
+```
+
+- Available Mac packaging types are `dmg`, `pkg`, and `image` (image means a pure Mac `app` without a setup program)
+- Available Windows packaging types are `msi`, `exe`, and `image` (image means a Windows application directory without a setup program). Learn more about Windows packaging are [over here](#windows-application-packaging).
+
+Note: if you are using Glimmer manually, to make the `glimmer package` command available, you must add the following line to your application `Rakefile` (automatically done for you if you scaffold an app or gem with `glimmer scaffold[AppName]` or `glimmer scaffold:gem:customshell[GemName]`):
+
+```ruby
+require 'glimmer/rake_task'
+```
+
+The Glimmer packaging process done in the `glimmer package` command consists of the following steps:
+1. Generate gemspec via Jeweler (`rake gemspec:generate`): Having a gemspec is required by the [`jar-dependencies`](https://github.com/mkristian/jar-dependencies) JRuby gem, used by JRuby libraries to declare JAR dependencies.
+1. Lock JAR versions (`glimmer package:lock_jars`): This locks versions of JAR dependencies leveraged by the `jar-dependencies` JRuby gem, downloading them into the `./vendor` directory so they would get inside the top-level Glimmer app/gem JAR file.
+1. Generate [Warbler](https://github.com/jruby/warbler) config (`glimmer package:config`): Generates initial Warbler config file (under `./config/warble.rb`) to use for generating JAR file.
+1. Generate JAR file using [Warbler](https://github.com/jruby/warbler) (`glimmer package:jar`): Enables bundling a Glimmer app into a JAR file under the `./dist` directory
+1. Generate native executable using [javapackager](https://docs.oracle.com/javase/8/docs/technotes/tools/unix/javapackager.html) (`glimmer package:native`): Enables packaging a JAR file as a DMG/PKG/APP file on Mac, MSI/EXE/APP on Windows, and DEB/RPM/APP on Linux (Glimmer does not officially support Linux with the `glimmer package` command yet, but it generates the JAR file successfully, and you could use `javapackager` manually afterwards if needed).
+
+Those steps automatically ensure generating a JAR file under the `./dist` directory using [Warbler](https://github.com/jruby/warbler), which is then used to automatically generate a DMG/MSI file (and other executables) under the `./packages/bundles` directory using `javapackager`. 
+The JAR file name will match your application local directory name (e.g. `MathBowling.jar` for `~/code/MathBowling`)
+The DMG file name will match the humanized local directory name + dash + application version (e.g. `Math Bowling-1.0.dmg` for `~/code/MathBowling` with version 1.0 or unspecified)
 
 The `glimmer package` command will automatically set "mac.CFBundleIdentifier" to ="org.#{project_name}.application.#{project_name}". 
 You may override by configuring as an extra argument for javapackger (e.g. Glimmer::Package.javapackager_extra_args = " -Bmac.CFBundleIdentifier=org.andymaleh.application.MathBowling")
@@ -2932,6 +3678,7 @@ This will generate `config/warble.rb`, which you may configure and then run `gli
 require_relative '../app/my_application.rb'
 ```
 - Include Icon (Optional): If you'd like to include an icon for your app (.icns format on the Mac), place it under `package/macosx` matching the humanized application local directory name (e.g. 'Math Bowling.icns' [containing space] for MathBowling or math_bowling). You may generate your Mac icon easily using tools like Image2Icon (http://www.img2icnsapp.com/) or manually using the Mac terminal command `iconutil` (iconutil guide: https://applehelpwriter.com/tag/iconutil/)
+- Include DMG Background Icon (Optional): Simply place a .png file under `package/macosx/{HumanAppName}-background.png`
 - Include Version (Optional): Create a `VERSION` file in your application and fill it your app version on one line (e.g. `1.1.0`)
 - Include License (Optional): Create a `LICENSE.txt` file in your application and fill it up with your license (e.g. MIT). It will show up to people when installing your app. Note that, you may optionally also specify license type, but you'd have to do so manually via `-BlicenseType=MIT` shown in an [example below](#javapackager-extra-arguments).
 - Extra args (Optional): You may optionally add the following to `Rakefile` to configure extra arguments for javapackager: `Glimmer::Packager.javapackager_extra_args = "..."` (Useful to avoid re-entering extra arguments on every run of rake task.). Read about them in [their section below](#javapackager-extra-arguments).
@@ -2969,6 +3716,18 @@ JAVAPACKAGER_EXTRA_ARGS='-Bmac.CFBundleName="Math Bowling Game"' glimmer package
 
 That overrides the default application display name.
 
+### Verbose Mode
+
+Pass `-v` to javapackager in `Glimmer::Package.javapackager_extra_args` or by running `glimmer package:native[type] -v` to learn more about further available customizations for the installer you are requesting to generate.
+
+### Windows Application Packaging
+
+Windows offers two options for setup packaging: 
+- `msi` (recommended): simpler packaging option. Requires [WiX Toolset](https://wixtoolset.org/) and [.NET Framework](https://dotnet.microsoft.com/download/dotnet-framework). Simply run `glimmer package[msi]` (or `glimmer package:native[msi]` if it's not your first time) and it will give you more details on the pre-requisites you need to install (e.g. [WiX Toolset](https://wixtoolset.org/) and [.NET Framework 3.5 SP1](https://dotnet.microsoft.com/download/dotnet-framework/net35-sp1)).
+- `exe`: more advanced packaging option. Requires [Inno Setup](https://jrsoftware.org/isinfo.php). Simply run `glimmer package[exe]` (or `glimmer package:native[exe]` if it's not your first time) and it will tell you what you need to install.
+
+If you just want to test out packaging into a native Windows app that is not packaged for Windows setup, just pass `image` to generate a native Windows app only.
+
 ### Mac Application Distribution
 
 Recent macOS versions (starting with Catalina) have very stringent security requirements requiring all applications to be signed before running (unless the user goes to System Preferences -> Privacy -> General tab and clicks "Open Anyway" after failing to open application the first time they run it). So, to release a desktop application on the Mac, it is recommended to enroll in the [Apple Developer Program](https://developer.apple.com/programs/) to distribute on the [Mac App Store](https://developer.apple.com/distribute/) or otherwise request [app notarization from Apple](https://developer.apple.com/documentation/xcode/notarizing_macos_software_before_distribution) to distribute independently.
@@ -3034,6 +3793,30 @@ By the way, keep in mind that during normal operation, it does also indicate a f
 Exec failed with code 2 command [[/usr/bin/SetFile, -c, icnC, /var/folders/4_/g1sw__tx6mjdgyh3mky7vydc0000gp/T/fxbundler4076750801763032201/images/MathBowling/.VolumeIcon.icns] in unspecified directory
 ```
 
+## App Updates
+
+Glimmer already supports automatic (and manual) app updates via the Mac App Store for Mac apps. Simply run the `glimmer package` command with the Mac App Store keys configured as per [Mac Application Distribution](mac-application-distribution) instructions and you get automatic (and manual) app update support courtesy of the Mac App Store.
+
+## Glimmer Supporting Libraries
+
+Here is a list of notable 3rd party gems used by Glimmer:
+- [jeweler](https://github.com/technicalpickles/jeweler): generates app gems during [Glimmer Scaffolding](#scaffolding)
+- [logging](https://github.com/TwP/logging): provides extra logging capabilities not available in Ruby Logger such as multi-threaded buffered asynchronous logging (to avoid affecting app performance) and support for multiple appenders such as stdout, syslog, and log files (the last one is needed on Windows where syslog is not supported)
+- [nested_inherited_jruby_include_package](https://github.com/AndyObtiva/nested_inherited_jruby_include_package): makes included [SWT](https://www.eclipse.org/swt/)/[Java](https://www.java.com/en/) packages available to all classes/modules that mix in the Glimmer module without having to manually reimport
+- [os](https://github.com/rdp/os): provides OS detection capabilities (e.g. `OS.mac?` or `OS.windows?`) to write cross-platform code inexpensively
+- [puts_debuggerer](https://github.com/AndyObtiva/puts_debuggerer): helps in troubleshooting when adding `require 'pd'` and using the `pd` command instead of `puts` or `p` (also `#pd_inspect` or `#pdi` instead of `#inspect`)
+- [rake](https://github.com/ruby/rake): used to implement and execute `glimmer` commands
+- [rake-tui](https://github.com/AndyObtiva/rake-tui): Rake Text-based User Interface. Allows navigating rake tasks with arrow keys and filtering task list by typing to quickly find an run a rake task.
+- [super_module](https://github.com/AndyObtiva/super_module): used to cleanly write the Glimmer::UI:CustomWidget and Glimmer::UI::CustomShell modules
+- [text-table](https://github.com/aptinio/text-table): renders textual data in a textual table for the command-line interface of Glimmer
+- [warbler](https://github.com/jruby/warbler): converts a Glimmer app into a Java JAR file during packaging
+
+## Glimmer Process
+
+[Glimmer Process](PROCESS.md) is the lightweight software development process used for building Glimmer libraries and Glimmer apps, which goes beyond Agile, rendering all Agile processes obsolete. [Glimmer Process](PROCESS.md) is simply made up of 7 guidelines to pick and choose as necessary until software development needs are satisfied. 
+
+Learn more by reading the [GPG](PROCESS.md) (Glimmer Process Guidelines)
+
 ## Resources
 
 * [Code Master Blog](http://andymaleh.blogspot.com/search/label/Glimmer)
@@ -3067,13 +3850,15 @@ Glimmer DSL Engine specific tasks are at:
 
 ## Change Log
 
+[glimmer-dsl-swt/CHANGELOG.md](https://github.com/AndyObtiva/glimmer-dsl-swt/blob/master/CHANGELOG.md)
+
 [CHANGELOG.md](CHANGELOG.md)
 
 ## Contributing
 
 **Contributors Wanted!**
 
-If you would like to contribute to Glimmer, please study up on Glimmer and [SWT](#swt-reference), run all Glimmer [samples](#samples), and build a small sample app to add to [glimmer-dsl-swt](https://github.com/AndyObtiva/glimmer-dsl-swt) Hello or Elaborate samples via a Pull Request. Once done, contact me on [Chat](#chat).
+If you would like to contribute to Glimmer, please study up on Glimmer and [SWT](#swt-reference), run all Glimmer [samples](#samples), and build a small sample app (perhaps from [this TODO list](https://github.com/AndyObtiva/glimmer-dsl-swt/blob/master/TODO.md#samples)) to add to [glimmer-dsl-swt](https://github.com/AndyObtiva/glimmer-dsl-swt) Hello or Elaborate samples via a Pull Request. Once done, contact me on [Chat](#chat).
 
 You may apply for contributing to any of these Glimmer DSL gems whether you prefer to focus on the desktop or web:
 - [glimmer-dsl-swt](https://github.com/AndyObtiva/glimmer-dsl-swt): Glimmer DSL for SWT (Desktop GUI)
@@ -3096,7 +3881,11 @@ If your company would like to invest fulltime in further development of the Glim
 
 ## License
 
-Copyright (c) 2007-2020 Andy Maleh.
-See LICENSE.txt for further details.
+[MIT](https://opensource.org/licenses/MIT)
+
+Copyright (c) 2007-2020 - Andy Maleh. 
+See [LICENSE.txt](LICENSE.txt) for further details.
+
+--
 
 Glimmer logo was made by <a href="https://www.flaticon.com/authors/freepik" title="Freepik">Freepik</a> from <a href="https://www.flaticon.com/" title="Flaticon"> www.flaticon.com</a>