glimmer 0.9.1 → 0.10.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 9a0e5867d64de61a6733bb4946eb3b366ae854a72bf99cdc048707c00cd9c276
-  data.tar.gz: b3735c7bff7ee61219f822378b59077e00f9957ed1031b09fd1e3f461eb90868
+  metadata.gz: 5c67def84181cab028446e3087c2c22d091bb0b17d02aa91e3948a8d7b176113
+  data.tar.gz: a2613dc9b58d1ef2d048b93f695e2aef799b06c46ec85999a78ecb48a6c5d469
 SHA512:
-  metadata.gz: b5e181bff40082c4620fc6ad1a306af61c7d59e24a30c13c6038606f008d9480da5532d07a704d0c39563318c23935efb909f958f596b7c49c5f2a6843ace165
-  data.tar.gz: 0562d569471bb792943cac85d0c3a79462573074e1ad634fb0aac1f1e9b53bbe9121d8534f9ea1ce94f5b30b0c47947618e73938e38d72695cecbfba48684210
+  metadata.gz: cbab9c4d0212aa47f46dd73394c05a47ebb95d1b18afb1b76b7400c72ae188f849776f411e3808b3fbd75537d3c7ca416fe3bcf90c08aba17e3058a8bccbc228
+  data.tar.gz: f913e477fa27d42e46614470e3e9e3c18fafd08e2a8fb6eb65c579b6a5894884e61da5203fc0df1d41fd4860f5dc4b435c123c6b5822a4056f6c01bfb4854ff2

data/README.md

@@ -1,12 +1,24 @@
-# 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;" /> 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)
+[![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)
+[![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.
 
 [<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)
 
+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
+
 ## Examples
 
 ### Hello, World!
@@ -67,15 +79,13 @@ glimmer samples/elaborate/tic_tac_toe.rb
 
 Glimmer app:
 
-![Tic Tac Toe](images/glimmer-tic-tac-toe.png)
+![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.
 
-Ruby is a dynamically-typed object-oriented language, which provides great productivity gains due to its powerful expressive syntax and dynamic nature. While it is proven by the Ruby on Rails framework for web development, it currently lacks a robust platform-independent framework for building desktop applications. Given that Java libraries can now be utilized in Ruby code through JRuby, Eclipse technologies, such as SWT, JFace, and RCP can help fill the gap of desktop application development with Ruby.
-
 ## Table of contents
 
-- [Glimmer - Ruby Desktop Development GUI Library](#glimmer---ruby-desktop-development-gui-library)
+- [Glimmer (Ruby Desktop Development GUI Library)](#-glimmer-ruby-desktop-development-gui-library)
   - [Examples](#examples)
     - [Hello, World!](#hello-world)
     - [Tic Tac Toe](#tic-tac-toe)
@@ -94,6 +104,13 @@ Ruby is a dynamically-typed object-oriented language, which provides great produ
       - [Custom Widget](#custom-widget)
       - [Custom Shell Gem](#custom-shell-gem)
       - [Custom Widget Gem](#custom-widget-gem)
+    - [Gem Listing](#gem-listing)
+      - [Listing Custom Shell Gems](#listing-custom-shell-gems)
+      - [Listing Custom Widget Gems](#listing-custom-widget-gems)
+      - [Listing DSL Gems](#listing-dsl-gems)
+    - [Packaging](#packaging)
+    - [Raw JRuby Command](#raw-jruby-command)
+      - [Mac Support](#mac-support)
   - [Girb (Glimmer irb) Command](#girb-glimmer-irb-command)
   - [Glimmer DSL Syntax](#glimmer-dsl-syntax)
     - [Widgets](#widgets)
@@ -101,6 +118,7 @@ Ruby is a dynamically-typed object-oriented language, which provides great produ
       - [SWT Proxies](#swt-proxies)
       - [Dialog](#dialog)
       - [Menus](#menus)
+      - [ScrolledComposite](#scrolledcomposite)
     - [Widget Styles](#widget-styles)
       - [Explicit SWT Style Bit](#explicit-swt-style-bit)
       - [Negative SWT Style Bits](#negative-swt-style-bits)
@@ -121,29 +139,49 @@ Ruby is a dynamically-typed object-oriented language, which provides great produ
       - [Observing Models](#observing-models)
     - [Custom Widgets](#custom-widgets)
       - [Simple Example](#simple-example)
-      - [Hook Example](#hook-example)
+      - [Lifecycle Hook Example](#lifecycle-hook-example)
+      - [Custom Widget API](#custom-widget-api)
       - [Content/Options Example](#contentoptions-example)
+      - [Custom Widget Lifecycle Hooks](#custom-widget-lifecycle-hooks)
       - [Gotcha](#gotcha)
+      - [Final Notes](#final-notes)
     - [Custom Shells](#custom-shells)
+    - [Drag and Drop](#drag-and-drop)
     - [Miscellaneous](#miscellaneous)
       - [Multi-DSL Support](#multi-dsl-support)
       - [Application Menu Items (About/Preferences)](#application-menu-items-aboutpreferences)
       - [App Name and Version](#app-name-and-version)
       - [Video Widget](#video-widget)
       - [Browser Widget](#browser-widget)
+  - [Glimmer Configuration](#glimmer-configuration)
+    - [logger](#logger)
+    - [import_swt_packages](#importswtpackages)
+    - [loop_max_count](#loopmaxcount)
   - [Glimmer Style Guide](#glimmer-style-guide)
+  - [SWT Reference](#swt-reference)
   - [Samples](#samples)
     - [Hello Samples](#hello-samples)
+      - [Hello, World! Sample](#hello-world-sample)
+      - [Hello, Tab!](#hello-tab)
+      - [Hello, Combo!](#hello-combo)
+      - [Hello, List Single Selection!](#hello-list-single-selection)
+      - [Hello, List Multi Selection!](#hello-list-multi-selection)
+      - [Hello, Computed!](#hello-computed)
+      - [Hello, Message Box!](#hello-message-box)
+      - [Hello, Browser!](#hello-browser)
+      - [Hello, Drag and Drop!](#hello-drag-and-drop)
+      - [Hello, Menu Bar!](#hello-menu-bar)
+      - [Hello, Pop Up Context Menu!](#hello-pop-up-context-menu)
     - [Elaborate Samples](#elaborate-samples)
+      - [Login](#login)
+      - [Tic Tac Toe Sample](#tic-tac-toe-sample)
+      - [Contact Manager](#contact-manager)
     - [External Samples](#external-samples)
       - [Glimmer Calculator](#glimmer-calculator)
       - [Gladiator](#gladiator)
   - [In Production](#in-production)
-  - [SWT Reference](#swt-reference)
-  - [SWT Packages](#swt-packages)
-  - [Logging](#logging)
-  - [Raw JRuby Command](#raw-jruby-command)
-    - [Mac Support](#mac-support)
+    - [Math Bowling](#math-bowling)
+    - [Are We There Yet?](#are-we-there-yet)
   - [Packaging & Distribution](#packaging--distribution)
     - [Packaging Defaults](#packaging-defaults)
     - [Packaging Configuration](#packaging-configuration)
@@ -154,11 +192,12 @@ Ruby is a dynamically-typed object-oriented language, which provides great produ
   - [Resources](#resources)
   - [Help](#help)
     - [Issues](#issues)
-    - [IRC Channel](#irc-channel)
+    - [Chat](#chat)
   - [Feature Suggestions](#feature-suggestions)
   - [Change Log](#change-log)
   - [Contributing](#contributing)
   - [Contributors](#contributors)
+  - [Hire Me](#hire-me)
   - [License](#license)
 
 ## Background
@@ -185,38 +224,52 @@ https://www.eclipse.org/swt/faq.php
 ## Pre-requisites
 
 - SWT 4.15 (comes included in Glimmer gem)
-- JRuby 9.2.11.1 (supporting Ruby 2.5.x syntax) (find at [https://www.jruby.org/download](https://www.jruby.org/download))
+- 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/))
 
 On **Mac** and **Linux**, an easy way to obtain JRuby is through [RVM](http://rvm.io) by running:
 
 ```bash
-rvm install jruby-9.2.11.1
+rvm install jruby-9.2.12.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.
 
 ## Setup
 
-Please follow these instructions to make the `glimmer` command available on your system.
+Please follow these instructions to make the `glimmer` command available on your system via the [`glimmer-dsl-swt`](https://github.com/AndyObtiva/glimmer-dsl-swt) gem.
 
-### Option 1: Direct Install
+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).
+
+Otherwise, Option 2 ([Bundler](#option-2-bundler)) is recommended for building Glimmer apps on other platforms (Windows and Linux).
+
+### Option 1: Direct Install 
+(Use for [Scaffolding](#scaffolding) on the Mac)
 
 Run this command to install directly:
 ```
-jgem install glimmer-dsl-swt -v 0.1.0
+jgem install glimmer-dsl-swt -v 0.4.1
 ```
 
 `jgem` is JRuby's version of `gem` command. 
 RVM allows running `gem` as an alias.
 Otherwise, you may also run `jruby -S gem install ...`
 
-### Option 2: Bundler
+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.
+
+Otherwise, if you are ready to build a Glimmer app on the Mac, you can jump to the [Glimmer Scaffolding](https://github.com/AndyObtiva/glimmer#scaffolding) section next.
+
+Note: if you're using activerecord or activesupport, keep in mind that Glimmer unhooks ActiveSupport::Dependencies as it does not rely on it.
+
+### Option 2: Bundler 
+(Use for Manual App Creation)
 
 Add the following to `Gemfile`:
 ```
-gem 'glimmer-dsl-swt', '~> 0.1.0'
+gem 'glimmer-dsl-swt', '~> 0.4.1'
 ```
 
 And, then run:
@@ -224,10 +277,16 @@ And, then run:
 jruby -S bundle install
 ```
 
-You may learn more about other Glimmer related gems at [Multi-DSL Support](#multi-dsl-support)
+Note: if you're using activerecord or activesupport, keep in mind that Glimmer unhooks ActiveSupport::Dependencies as it does not rely on it.
+
+You may learn more about other Glimmer related gems ([`glimmer-dsl-opal`](https://github.com/AndyObtiva/glimmer-dsl-opal), [`glimmer-dsl-xml`](https://github.com/AndyObtiva/glimmer-dsl-xml), and [`glimmer-dsl-css`](https://github.com/AndyObtiva/glimmer-dsl-css)) at [Multi-DSL Support](#multi-dsl-support)
 
 ## Glimmer Command
 
+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).
+
 ### Basic Usage
 
 ```
@@ -264,7 +323,11 @@ 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)
@@ -362,6 +425,10 @@ Eventually, it will launch an advanced "Hello, World!" app window having the tit
 
 ![Glimmer Scaffold App](images/glimmer-scaffolding-app.png)
 
+On the Mac, it also comes with a boilerplate Preferences dialog.
+
+![Glimmer Scaffold App Preferences](images/glimmer-scaffolding-app-preferences.png)
+
 #### Custom Shell
 
 To scaffold a Glimmer custom shell (full window view) for an existing Glimmer app, run the following command:
@@ -417,11 +484,133 @@ The Ruby gem name will follow the convention "glimmer-cw-customwidgetname-namesp
 
 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
+
+The `glimmer` command comes with tasks for listing Glimmer related gems to make it easy to find Glimmer Custom Shells, Custom Widgets, and DSLs published by others in the Glimmer community on [rubygems.org](http://www.rubygems.org).
+
+#### Listing Custom Shell Gems
+
+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)
+```
+
+Example:
+
+```
+glimmer list:custom_shell_gems
+```
+
+Output:
+
+```
+
+  Glimmer Custom Shell Gems at rubygems.org:
+                                                                                                                 
+     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  
+                                                                                                                 
+```
+
+#### Listing Custom Widget Gems
+
+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)
+```
+
+Example:
+
+Check if there is a custom video widget for Glimmer.
+
+```
+glimmer list:custom_widget_gems[video]
+```
+
+Output:
+
+```
+
+  Glimmer Custom Widget Gems matching [video] at rubygems.org:
+                                                                                   
+  Name          Gem          Version     Author              Description           
+                                                                                   
+  Video   glimmer-cw-video   0.1.1     Andy Maleh   Glimmer Custom Widget - Video  
+                                                                                   
+```
+
+#### Listing DSL Gems
+
+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)
+```
+
+Example:
+
+```
+glimmer list:dsl_gems
+```
+
+Output:
+
+```
+
+  Glimmer DSL Gems at rubygems.org:
+                                                                         
+  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.4.1     AndyMaleh   Glimmer DSL for SWT    
+  Xml    glimmer-dsl-xml    0.1.0     AndyMaleh   Glimmer DSL for XML    
+                                                                         
+```
+
+### Packaging
+
+Glimmer packaging tasks are detailed under [Packaging & Distribution](#packaging--distribution).
+
+### Raw JRuby Command
+
+If there is a need to run Glimmer directly via the `jruby` command, you
+may run the following:
+
+```
+jruby -J-classpath "path_to/swt.jar" -r glimmer -S application.rb
+```
+
+The `-J-classpath` option specifies the `swt.jar` file path, which can be a
+manually downloaded version of SWT, or otherwise the one included in the gem. You can lookup the one included in the gem by running `jgem which glimmer` to find the gem path and then look through the `vendor` directory.
+
+The `-r` option preloads (requires) the `glimmer` library in Ruby.
+
+The `-S` option specifies a script to run.
+
+#### Mac Support
+
+The Mac is well supported with the `glimmer` command. The advice below is not needed if you are using it.
+
+However, if there is a reason to use the raw `jruby` command directly instead of the `glimmer` command, you need to pass an extra option (`-J-XstartOnFirstThread`) to JRuby on the Mac (Glimmer automatically passes it for you when using the `glimmer` command).
+
+Example:
+```
+jruby -J-XstartOnFirstThread -J-classpath "path_to/swt.jar" -r glimmer -S application.rb
+```
 
 ## Girb (Glimmer irb) Command
 
-With Glimmer installed, you may want to run `girb` instead of standard `irb` to have SWT preloaded and the Glimmer library required and included for quick Glimmer coding/testing.
+With `glimmer-dsl-swt` installed, you may want to run `girb` instead of standard `irb` to have SWT preloaded and the Glimmer library required and included for quick Glimmer coding/testing.
 
 ```
 girb
@@ -441,13 +630,13 @@ Keep in mind that all samples live under [https://github.com/AndyObtiva/glimmer-
 
 Glimmer DSL syntax consists of static keywords and dynamic keywords to build and bind user-interface objects.
 
-Static keywords are pre-identified keywords in the Glimmer DSL, such as `shell`, `rgb`, and `bind`.
+Static keywords are pre-identified keywords in the Glimmer DSL, such as `shell`, `message_box`, `async_exec`, and `bind`.
 
-Dynamic keywords are dynamically figured out from available SWT widgets, custom widgets, and properties. Examples are: `label`, `combo`, and `text`.
+Dynamic keywords are dynamically figured out from available SWT widgets, custom widgets, and properties. Examples are: `label`, `combo`, and `list`.
 
-The only reason to distinguish between both types of Glimmer DSL keywords is to realize that importing new Java SWT custom widget libraries and Ruby custom widgets automatically expands Glimmer's available DSL syntax via new dynamic keywords.
+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 SWT library:
+For example, if a project adds this custom Java SWT library:
 
 https://www.eclipse.org/nebula/widgets/cdatetime/cdatetime.php?page=operation
 
@@ -540,22 +729,22 @@ Check out the [samples](samples) directory for more examples.
 
 Example from [hello_tab.rb](samples/hello/hello_tab.rb) sample (you may copy/paste in [`girb`](#girb-glimmer-irb-command)):
 
-![Hello Tab 1](images/glimmer-hello-tab1.png)
+![Hello Tab English](images/glimmer-hello-tab-english.png)
 
-![Hello Tab 2](images/glimmer-hello-tab2.png)
+![Hello Tab French](images/glimmer-hello-tab-french.png)
 
 ```ruby
 shell {
-  text "SWT"
+  text "Hello, Tab!"
   tab_folder {
     tab_item {
-      text "Tab 1"
+      text "English"
       label {
         text "Hello, World!"
       }
     }
     tab_item {
-      text "Tab 2"
+      text "French"
       label {
         text "Bonjour Univers!"
       }
@@ -575,7 +764,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 {
     # ...
   }
   # ...
@@ -627,27 +816,34 @@ Example (you may copy/paste in [`girb`](#girb-glimmer-irb-command)):
 @shell.open
 ```
 
-##### `#swt_widget`
+##### `message_box`
 
-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.
+The Glimmer DSL `message_box` keyword is similar to `shell`, but renders a modal dialog with a title `text` property and main body `message` property. It may also be opened via the `#open` method.
 
 Example (you may copy/paste in [`girb`](#girb-glimmer-irb-command)):
 
 ```ruby
+include Glimmer
+
 @shell = shell {
+  text 'Hello, Message Box!'
   button {
-    text "Press Me"
+    text 'Please Click To Win a Surprise'
     on_widget_selected {
-      message_box = MessageBox.new(@shell.swt_widget) # passing SWT Shell widget
-      message_box.setText("Surprise")
-      message_box.setMessage("You have won $1,000,000!")
-      message_box.open      
+      message_box(@shell) {
+        text 'Surprise'
+        message "Congratulations!\n\nYou have won $1,000,000!"
+      }.open
     }
   }
 }
 @shell.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.
+
 ##### Shell widget proxy methods
 
 Shell widget proxy has extra methods specific to SWT Shell:
@@ -675,7 +871,7 @@ Glimmer DSL provides support for SWT Menu and MenuItem widgets.
 
 There are 2 main types of menus in SWT:
 - Menu Bar (shows up on top)
-- Pop Up Menu (shows up when right-clicking a widget)
+- Pop Up Context Menu (shows up when right-clicking a widget)
 
 Underneath both types, there can be a 3rd menu type called Drop Down.
 
@@ -683,39 +879,63 @@ Glimmer provides special support for Drop Down menus as it automatically instant
 
 The ampersand symbol indicates the keyboard shortcut key for the menu item (e.g. '&Help' can be triggered on Windows by hitting ALT+H)
 
-Example [Menu Bar] (you may copy/paste in [`girb`](#girb-glimmer-irb-command)):
+Example of a Menu Bar (you may copy/paste in [`girb`](#girb-glimmer-irb-command)):
 
 ```ruby
-shell {
+shell { |shell_proxy|
+  text 'Hello, Menu Bar!'
+  grid_layout
+  label(:center) {
+    font height: 16
+    text 'Check Out The File Menu and History Menu in The Menu Bar Above!'
+  }
   menu_bar {
     menu {
-      text "&File"
+      text '&File'
       menu_item {
-        text "E&xit"
+        text 'E&xit'
       }
       menu_item(0) {
-        text "&New"
+        text '&New'
+        on_widget_selected {
+          message_box(shell_proxy) {
+            text 'New File'
+            message 'New File Contents'
+          }.open
+        }
       }
       menu(1) {
-        text "&Options"
+        text '&Options'
         menu_item(:radio) {
-          text "Option 1"
+          text 'Option 1'
         }
         menu_item(:separator)
         menu_item(:check) {
-          text "Option 3"
+          text 'Option 3'
         }
       }
     }
     menu {
-      text "&History"
+      text '&History'
       menu {
-        text "&Recent"
+        text '&Recent'
         menu_item {
-          text "File 1"
+          text 'File 1'
+          on_widget_selected {
+            message_box(shell_proxy) {
+              text 'File 1'
+              message 'File 1 Contents'
+            }.open
+          }
         }
         menu_item {
-          text "File 2"
+          text 'File 2'
+          on_widget_selected {
+            message_box(shell_proxy) {
+              text 'File 2'
+              message 'File 2 Contents'
+            }.open
+          }
         }
       }
     }
@@ -723,22 +943,37 @@ shell {
 }.open
 ```
 
-Example [Pop Up Menu] (you may copy/paste in [`girb`](#girb-glimmer-irb-command)):
+Example of a Pop Up Context Menu (you may copy/paste in [`girb`](#girb-glimmer-irb-command)):
 
 ```ruby
-shell {
+shell { |shell_proxy|
+  text 'Hello, Pop Up Context Menu!'
+  grid_layout
   label {
-    text 'Right-Click Me'
+    font height: 16
+    text 'Right-Click To Pop Up a Context Menu'
     menu {
       menu {
         text '&History'
         menu {
-          text "&Recent"
+          text '&Recent'
           menu_item {
-            text "File 1"
+            text 'File 1'
+            on_widget_selected {
+              message_box(shell_proxy) {
+                text 'File 1'
+                message 'File 1 Contents'
+              }.open
+            }
           }
           menu_item {
-            text "File 2"
+            text 'File 2'
+            on_widget_selected {
+              message_box(shell_proxy) {
+                text 'File 2'
+                message 'File 2 Contents'
+              }.open
+            }
           }
         }
       }
@@ -747,6 +982,13 @@ shell {
 }.open
 ```
 
+#### ScrolledComposite
+
+Glimmer provides smart defaults for the `scrolled_composite` widget by:
+- Automatically setting the nested widget as its content (meaning use can just like a plain old `composite` to add scrolling)
+- Automatically setting the :h_scroll and :v_scroll SWT styles (can be set manually if only one of either :h_scroll or :v_scroll is desired )
+- Automatically setting the expand horizontal and expand vertical SWT properties to `true`
+
 ### Widget Styles
 
 SWT widgets receive `SWT` styles in their constructor as per this guide:
@@ -992,9 +1234,12 @@ composite {
 ```
 
 Here is a more sophisticated example taken from [hello_computed.rb](samples/hello/hello_computed.rb) sample:
+
+![Hello Computed](images/glimmer-hello-computed.png)
+
 ```ruby
 shell {
-  text "Hello Computed"
+  text 'Hello, Computed!'
   composite {
     grid_layout {
       num_columns 2
@@ -1002,44 +1247,44 @@ shell {
       horizontal_spacing 20
       vertical_spacing 10
     }
-    label {text "First &Name: "}
+    label {text 'First &Name: '}
     text {
       text bind(@contact, :first_name)
       layout_data {
-        horizontalAlignment :fill
-        grabExcessHorizontalSpace true
+        horizontal_alignment :fill
+        grab_excess_horizontal_space true
       }
     }
-    label {text "&Last Name: "}
+    label {text '&Last Name: '}
     text {
       text bind(@contact, :last_name)
       layout_data {
-        horizontalAlignment :fill
-        grabExcessHorizontalSpace true
+        horizontal_alignment :fill
+        grab_excess_horizontal_space true
       }
     }
-    label {text "&Year of Birth: "}
+    label {text '&Year of Birth: '}
     text {
       text bind(@contact, :year_of_birth)
       layout_data {
-        horizontalAlignment :fill
-        grabExcessHorizontalSpace true
+        horizontal_alignment :fill
+        grab_excess_horizontal_space true
       }
     }
-    label {text "Name: "}
+    label {text 'Name: '}
     label {
       text bind(@contact, :name, computed_by: [:first_name, :last_name])
       layout_data {
-        horizontalAlignment :fill
-        grabExcessHorizontalSpace true
+        horizontal_alignment :fill
+        grab_excess_horizontal_space true
       }
     }
-    label {text "Age: "}
+    label {text 'Age: '}
     label {
       text bind(@contact, :age, on_write: :to_i, computed_by: [:year_of_birth])
       layout_data {
-        horizontalAlignment :fill
-        grabExcessHorizontalSpace true
+        horizontal_alignment :fill
+        grab_excess_horizontal_space true
       }
     }
   }
@@ -1182,6 +1427,10 @@ Example from [samples/hello/hello_combo.rb](samples/hello_combo.rb) sample (you
 
 #### Combo
 
+The `combo` widget provides a dropdown of options. By default, it also allows typing in a new option. To disable that behavior, you may use with the `:read_only` SWT style.
+
+When data-binding a `combo` widget, Glimmer can automatically deduce available options from data-bound model by convention: `{attribute_name}_options` method.
+
 ![Hello Combo](images/glimmer-hello-combo.png)
 
 ![Hello Combo](images/glimmer-hello-combo-expanded.png)
@@ -1223,7 +1472,7 @@ end
 HelloCombo.new.launch
 ```
 
-`combo` widget is data-bound to the country of a person. Note that it expects `person` object to have `:country` attribute and `:country_options` attribute containing all available countries.
+`combo` widget is data-bound to the country of a person. Note that it expects the `person` object to have the `:country` attribute and `:country_options` attribute containing all available countries (aka options). Glimmer reads these attributes by convention.
 
 #### List
 
@@ -1337,6 +1586,9 @@ shell {
     }
     items bind(group, :people), column_properties(:name, :age, :adult)
     selection bind(group, :selected_person)
+    on_mouse_up { |event|
+      @table.edit_table_item(event.table_item, event.column_index)
+    }    
   }
 }
 ```
@@ -1344,6 +1596,7 @@ shell {
 The code above includes two data-bindings:
 - Table `items`, which first bind to the model collection property (group.people), and then maps each column property (name, age, adult) for displaying each table item column. 
 - Table `selection`, which binds the single table item selected by the user to the attribute denoted by the `bind` keyword (or binds multiple table items selected for a table with `:multi` SWT style)
+- The `on_mouse_up` event handler invokes `@table.edit_table_item(event.table_item, event.column_index)` to start edit mode on the clicked table item cell, and then saves or cancel depending on whether the user hits ENTER or ESC once done editing (or focus-out after either making a change or not making any changes.)
 
 Additionally, Table `items` data-binding automatically stores each node model unto the SWT TableItem object via `setData` method. This enables things like searchability.
 
@@ -1363,6 +1616,67 @@ This automatically leverages the SWT TableEditor custom class behind the scenes,
 passed table item text into something else. 
 It automatically persists the change to `items` data-bound model on ENTER/FOCUS-OUT or cancels on ESC/NO-CHANGE.
 
+##### Table Sorting
+
+Glimmer automatically adds sorting support to the SWT `Table` widget. 
+
+Check out the [Contact Manager](#contact-manager) sample for an example. 
+You may click on any column and it will sort by ascending order first and descending if you click again.
+
+Glimmer automatic table sorting supports `String`, `Integer`, and `Float` columns out of the box as well as any column data that is comparable.
+
+In cases where data is nil, depending on the data-type, it is automatically converted to `Float` with `to_f`, `Integer` with `to_i`, or `String` with `to_s`.
+
+Should you have a special data type that could not be compared automatically, Glimmer offers the following 3 alternatives for custom sorting:
+- `sort_property`: this may be set to an alternative property to the one data-bound to the table column. For example, a table column called 'adult', which returns `true` or `false` may be sorted with `sort_property :dob` instead. This also support multi-property (aka multi-column) sorting (e.g. `sort_property :dob, :name`). 
+- `sort_by(&block)`: this works just like Ruby `Enumerable` `sort_by`. The block receives the table column data as argument.
+- `sort(&comparator)`: this works just like Ruby `Enumerable` `sort`. The comparator block receives two objects from the table column data.
+
+You may also set `additional_sort_properties` on the parent `table` widget to have secondary sorting applied. For example, if you set `additional_sort_properties :name, :project_name`, then whenever you sort by `:name`, it additionally sorts by `:project_name` afterwards, and vice versa. This only works for columns that either have no custom sort set or have a `sort_property` with one property only (but no sort or sort_by block)
+
+Example:
+
+```ruby
+# ...
+  table {
+    table_column {
+      text 'Task'
+      width 120
+    }
+    table_column {
+      text 'Project'
+      width 120
+    }
+    table_column {
+      text 'Duration (hours)'
+      width 120
+      sort_property :duration_in_hours
+    }
+    table_column {
+      text 'Priority'
+      width 120
+      sort_by { |value| ['High', 'Medium', 'Low'].index(value) }
+    }
+    table_column {
+      text 'Start Date'
+      width 120
+      sort { |d1, d2| d1.to_date <=> d2.to_date }
+    }
+    additional_sort_properties :project_name, :duration_in_hours, :name
+    items bind(Task, :list), column_properties(:name, :project_name, :duration, :priority, :start_date)
+    # ...
+  }
+# ...
+```
+
+Here is an explanation of the example above:
+- Task and Project table columns are data-bound to the `:name` and `:project_name` properties and sorted through them automatically
+- Task Duration table column is data-bound to the `:duration` property, but sorted via the `:duration_in_hours` property instead
+- Task Priority table column has a custom sort_by block
+- Task Start Date table column has a custom sort comparator block
+- Additional (secondary) sort properties are applied when sorting by Task, Project, or Duration in the order specified
+
+
 #### Tree
 
 The SWT Tree widget visualizes a tree data-structure, such as an employment or composition hierarchy.
@@ -1410,10 +1724,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.
@@ -1458,21 +1772,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 {
@@ -1482,7 +1796,7 @@ shell {
   @button2 = button {
     text "Show 1st Button"
     visible false
-    on_event_show {
+    on_swt_show {
       @button1.swt_widget.setVisible(false)
     }
     on_widget_selected {
@@ -1492,7 +1806,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
 
@@ -1535,7 +1849,7 @@ class TicTacToe
 end
 ```
 
-Observers can be a good mechanism for displaying dialog messages in Glimmer (using SWT's `MessageBox`).
+Observers can be a good mechanism for displaying dialog messages in Glimmer (using SWT's [`MessageBox`](https://help.eclipse.org/2020-06/topic/org.eclipse.platform.doc.isv/reference/api/org/eclipse/swt/widgets/MessageBox.html) class).
 
 Look at [`samples/elaborate/tictactoe/tic_tac_toe.rb`](samples/tictactoe/tic_tac_toe.rb) for more details starting with the code included below.
 
@@ -1561,10 +1875,10 @@ class TicTacToe
   end
 
   def display_game_over_message(message)
-    message_box = MessageBox.new(@shell.swt_widget)
-    message_box.setText("Game Over")
-    message_box.setMessage(message)
-    message_box.open
+    message_box(@shell) {
+      text 'Game Over'
+      message message_text
+    }.open
     @tic_tac_toe_board.reset
   end
   # ...
@@ -1605,7 +1919,7 @@ shell {
 
 As you can see, `RedLabel` became Glimmer DSL keyword: `red_label`
 
-#### Hook Example
+#### Lifecycle Hook Example
 
 (you may copy/paste in [`girb`](#girb-glimmer-irb-command))
 
@@ -1640,10 +1954,12 @@ shell {
 }.open
 ```
 
-Notice how `Red::Composite` became `red__composite` with double-underscore, which is how Glimmer Custom Widgets signify namespaces by convention. Additionally, `before_body` hook was utilized to set a `@color` variable and use inside the `body`.
+Notice how `Red::Composite` became `red__composite` with double-underscore, which is how Glimmer Custom Widgets signify namespaces by convention. Additionally, the `before_body` lifecycle hook was utilized to set a `@color` variable and use inside the `body`.
 
 Keep in mind that namespaces are not needed to be specified if the Custom Widget class has a unique name, not clashing with a basic SWT widget or another custom widget name.
 
+#### Custom Widget API
+
 Custom Widgets have the following attributes available to call from inside the `#body` method:
 - `#parent`: Glimmer object parenting custom widget
 - `#swt_style`: SWT style integer. Can be useful if you want to allow consumers to customize a widget inside the custom widget body
@@ -1698,7 +2014,9 @@ shell {
 
 Notice how `:no_focus` was the `swt_style` value, followed by the `options` hash `{orientation: :horizontal, bg_color: :white}`, and finally the `content` block containing the label with `'SANDWICH CONTENT'`
 
-Last but not least, these are the available hooks:
+#### Custom Widget Lifecycle Hooks
+
+Last but not least, these are the available lifecycle hooks:
 - `before_body`: takes a block that executes in the custom widget instance scope before calling `body`. Useful for initializing variables to later use in `body`
 - `after_body`: takes a block that executes in the custom widget instance scope after calling `body`. Useful for setting up observers on widgets built in `body` (set in instance variables) and linking to other shells.
 
@@ -1732,6 +2050,11 @@ body {
 
 The `text` method invoked in the custom widget body will call the one you defined above it. To avoid this gotcha, simply name the text property above something else, like `custom_text`.
 
+#### Final Notes
+
+This [Eclipse guide](https://www.eclipse.org/articles/Article-Writing%20Your%20Own%20Widget/Writing%20Your%20Own%20Widget.htm) for how to write custom SWT widgets is also applicable to Glimmer Custom Widgets written in Ruby. I recommend reading it:
+[https://www.eclipse.org/articles/Article-Writing%20Your%20Own%20Widget/Writing%20Your%20Own%20Widget.htm](https://www.eclipse.org/articles/Article-Writing%20Your%20Own%20Widget/Writing%20Your%20Own%20Widget.htm)
+
 ### Custom Shells
 
 Custom shells are a kind of custom widgets that have shells only as the body root. They can be self-contained applications that may be opened and hidden/closed independently of the main app.
@@ -1777,7 +2100,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
@@ -1797,6 +2120,62 @@ shell { |app_shell|
 }.open
 ```
 
+### Drag and Drop
+
+Glimmer offers Drag and Drop support, thanks to [SWT](https://www.eclipse.org/swt/) and Glimmer's lightweight [DSL syntax](#glimmer-dsl-syntax).
+
+You may learn more about SWT Drag and Drop support over here: [https://www.eclipse.org/articles/Article-SWT-DND/DND-in-SWT.html](https://www.eclipse.org/articles/Article-SWT-DND/DND-in-SWT.html)
+
+To get started, simply follow these steps:
+1. On the drag source widget, add `on_drag_set_data` [DragSourceListener](https://help.eclipse.org/2020-03/topic/org.eclipse.platform.doc.isv/reference/api/org/eclipse/swt/dnd/DragSourceListener.html) event handler block at minimum (you may also add `on_drag_start` and `on_drag_finished` if needed)
+1. Set `event.data` to transfer via drag and drop inside the `on_drag_set_data` event handler block (defaults to `transfer` type of `:text`, as in a Ruby String)
+1. On the drop target widget, add `on_drop` [DropTargetListener](https://help.eclipse.org/2020-03/topic/org.eclipse.platform.doc.isv/reference/api/org/eclipse/swt/dnd/DropTargetListener.html) event handler block at minimum (you may also add `on_drag_enter` [must set [`event.detail`](https://help.eclipse.org/2020-06/topic/org.eclipse.platform.doc.isv/reference/api/org/eclipse/swt/dnd/DropTargetEvent.html#detail) if added], `on_drag_over`, `on_drag_leave`, `on_drag_operation_changed` and `on_drop_accept` if needed)
+1. Read `event.data` and consume it (e.g. change widget text) inside the `on_drop` event handler block.
+
+Example (taken from [samples/hello/hello_drag_and_drop.rb](#hello-drag-and-drop) / you may copy/paste in [`girb`](#girb-glimmer-irb-command)):
+
+```ruby
+class Location
+  attr_accessor :country
+  
+  def country_options
+    %w[USA Canada Mexico Columbia UK Australia Germany Italy Spain]
+  end
+end
+
+@location = Location.new
+
+include Glimmer
+
+shell {
+  text 'Hello, Drag and Drop!'
+  list {
+    selection bind(@location, :country)
+    on_drag_set_data { |event|
+      list = event.widget.getControl
+      event.data = list.getSelection.first
+    }
+  }
+  label(:center) {
+    text 'Drag a country here!'
+    font height: 20
+    on_drop { |event|
+      event.widget.getControl.setText(event.data)
+    }
+  }
+}.open
+```
+
+![Hello Drag and Drop](images/glimmer-hello-drag-and-drop.gif)
+
+Optional steps:
+- Set a `transfer` property (defaults to `:text`). Values may be: :text (default), :html :image, :rtf, :url, and :file, or an array of multiple values. The `transfer` property will automatically convert your option into a [Transfer](https://help.eclipse.org/2020-03/topic/org.eclipse.platform.doc.isv/reference/api/org/eclipse/swt/dnd/Transfer.html) object as per the SWT API.
+- Specify `drag_source_style` operation (may be: :drop_copy (default), :drop_link, :drop_move, :drop_none, or an array of multiple operations)
+- Specify `drag_source_effect` (Check [DragSourceEffect](https://help.eclipse.org/2020-06/topic/org.eclipse.platform.doc.isv/reference/api/org/eclipse/swt/dnd/DragSourceEffect.html) SWT API for details)
+- Specify `drop_target_style` operation (may be: :drop_copy (default), :drop_link, :drop_move, :drop_none, or an array of multiple operations)
+- Specify `drop_target_effect` (Check [DropTargetEffect](https://help.eclipse.org/2020-06/topic/org.eclipse.platform.doc.isv/reference/api/org/eclipse/swt/dnd/DropTargetEffect.html) SWT API for details)
+- Set drag operation in `event.detail` (e.g. DND::DROP_COPY) inside `on_drag_enter`
+
 ### Miscellaneous
 
 #### Multi-DSL Support
@@ -1952,10 +2331,10 @@ class Example
   def initialize
     display {
       on_about {
-        message_box = MessageBox.new(@shell_proxy.swt_widget)
-        message_box.setText("About")
-        message_box.setMessage("About Application")
-        message_box.open
+        message_box(@shell_proxy) {
+          text 'About'
+          message 'About Application'
+        }.open
       }
       on_preferences {
         preferences_dialog = dialog {
@@ -2021,7 +2400,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. 
 
@@ -2029,7 +2408,9 @@ You may obtain via `glimmer-cw-video` gem.
 
 #### Browser Widget
 
-Glimmer supports SWT Browser widget, which can load URLs or render HTML. It can even be instrumented with JavaScript when needed (though highly discouraged in Glimmer except for rare cases when leveraging a pre-existing web codebase in a desktop app).
+![Hello Browser](images/glimmer-hello-browser.png)
+
+Glimmer supports the SWT Browser widget, which can load URLs or render HTML. It can even be instrumented with JavaScript when needed (though highly discouraged since it defeats the purpose of using Ruby except in very rare cases like leveraging a pre-existing web codebase in a desktop app).
 
 Example loading a URL (you may copy/paste in [`girb`](#girb-glimmer-irb-command)):
 
@@ -2065,6 +2446,100 @@ shell {
 
 This relies on Glimmer's [Multi-DSL Support](#multi-dsl-support) for building the HTML text using [Glimmer XML DSL](https://github.com/AndyObtiva/glimmer-dsl-xml).
 
+## Glimmer Configuration
+
+Glimmer configuration may be done via the `Glimmer::Config` module.
+
+### logger
+
+Glimmer 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.
+It may be replaced with a custom logger via `Glimmer::Config.logger = custom_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.
+
+Example:
+
+```ruby
+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.
+
+Example log:
+```
+D, [2017-07-21T19:23:12.587870 #35707] DEBUG -- : method: shell and args: []
+D, [2017-07-21T19:23:12.594405 #35707] DEBUG -- : ShellCommandHandler will handle command: shell with arguments []
+D, [2017-07-21T19:23:12.844775 #35707] DEBUG -- : method: composite and args: []
+D, [2017-07-21T19:23:12.845388 #35707] DEBUG -- : parent is a widget: true
+D, [2017-07-21T19:23:12.845833 #35707] DEBUG -- : on listener?: false
+D, [2017-07-21T19:23:12.864395 #35707] DEBUG -- : WidgetCommandHandler will handle command: composite with arguments []
+D, [2017-07-21T19:23:12.864893 #35707] DEBUG -- : widget styles are: []
+D, [2017-07-21T19:23:12.874296 #35707] DEBUG -- : method: list and args: [:multi]
+D, [2017-07-21T19:23:12.874969 #35707] DEBUG -- : parent is a widget: true
+D, [2017-07-21T19:23:12.875452 #35707] DEBUG -- : on listener?: false
+D, [2017-07-21T19:23:12.878434 #35707] DEBUG -- : WidgetCommandHandler will handle command: list with arguments [:multi]
+D, [2017-07-21T19:23:12.878798 #35707] DEBUG -- : widget styles are: [:multi]
+```
+
+### 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.
+
+As a result, you may call SWT Java classes from Glimmer Ruby code without mentioning Java package references explicitly.
+
+For example, `org.eclipse.swt.graphics.Color` can be referenced as just `Color`
+
+The Java packages imported come from the [`Glimmer::Config.import_swt_packages`](https://github.com/AndyObtiva/glimmer-dsl-swt/blob/master/lib/ext/glimmer/config.rb) config option, which defaults to `Glimmer::Config::DEFAULT_IMPORT_SWT_PACKAGES`, importing the following Java packages:
+```
+org.eclipse.swt.*
+org.eclipse.swt.widgets.*
+org.eclipse.swt.layout.*
+org.eclipse.swt.graphics.*
+org.eclipse.swt.browser.*
+org.eclipse.swt.custom.*
+org.eclipse.swt.dnd.*
+```
+
+If you need to import additional Java packages as extra Glimmer widgets, you may add more packages to [`Glimmer::Config.import_swt_packages`](https://github.com/AndyObtiva/glimmer-dsl-swt/blob/master/lib/ext/glimmer/config.rb) by using the `+=` operator (or alternatively limit to certain packages via `=` operator).
+
+Example:
+
+```ruby
+Glimmer::Config.import_swt_packages += [
+  'org.eclipse.nebula.widgets.ganttchart'
+]
+```
+
+Another alternative is to simply add a `java_import` call to your code (e.g. `java_import 'org.eclipse.nebula.widgets.ganttchart.GanttChart'`). Glimmer will automatically take advantage of it (e.g. when invoking `gantt_chart` keyword)
+
+Nonetheless, you can disable automatic Java package import if needed via this Glimmer configuration option:
+
+```ruby
+Glimmer::Config.import_swt_packages = false
+```
+
+Once disabled, to import SWT Java packages manually, you may simply:
+
+1. `include Glimmer::SWT::Packages`: lazily imports all SWT Java packages to your class, lazy-loading SWT Java class constants on first reference.
+
+2. `java_import swt_package_class_string`: immediately imports a specific Java class where `swt_package_class_string` is the Java full package reference of a Java class (e.g. `java_import 'org.eclipse.swt.SWT'`)
+
+Note: Glimmer relies on [`nested_imported_jruby_include_package`](https://github.com/AndyObtiva/nested_inherited_jruby_include_package), which automatically brings packages to nested-modules/nested-classes and sub-modules/sub-classes.
+
+You can learn more about importing Java packages into Ruby code at this JRuby WIKI page:
+
+https://github.com/jruby/jruby/wiki/CallingJavaFromJRuby
+
+### loop_max_count
+
+Glimmer has infinite loop detection support. 
+It can detect when an infinite loop is about to occur in method_missing and stops it. 
+It detects potential infinite loops when the same keyword and args repeat more than 100 times, which is unusual in a GUI app.
+
+The max limit can be changed via the `Glimmer::Config::loop_max_count=(count)` config option.
+
+Infinite loop detection may be disabled altogether if needed by setting `Glimmer::Config::loop_max_count` to `-1`
+
 ## Glimmer Style Guide
 
 - Widgets are declared with underscored lowercase versions of their SWT names minus the SWT package name.
@@ -2080,11 +2555,43 @@ This relies on Glimmer's [Multi-DSL Support](#multi-dsl-support) for building th
 - Custom widget body, before_body, and after_body blocks open their blocks and close them with curly braces.
 - Custom widgets receive additional arguments to SWT style called options. These are passed as the last argument inside the parentheses, a hash of option names pointing to values.
 
+## SWT Reference
+
+https://www.eclipse.org/swt/docs.php
+
+Here is the SWT API:
+
+https://help.eclipse.org/2019-12/nftopic/org.eclipse.platform.doc.isv/reference/api/index.html
+
+Here is a visual list of SWT widgets:
+
+https://www.eclipse.org/swt/widgets/
+
+Here is a textual list of SWT widgets:
+
+https://help.eclipse.org/2019-12/topic/org.eclipse.platform.doc.isv/guide/swt_widgets_controls.htm?cp=2_0_7_0_0
+
+Here is a list of SWT style bits as used in widget declaration:
+
+https://wiki.eclipse.org/SWT_Widget_Style_Bits
+
+Here is a SWT style bit constant reference:
+
+https://help.eclipse.org/2019-12/nftopic/org.eclipse.platform.doc.isv/reference/api/org/eclipse/swt/SWT.html
+
+Here is an SWT Drag and Drop guide:
+
+https://www.eclipse.org/articles/Article-SWT-DND/DND-in-SWT.html
+
+Here is an SWT Custom Widget guide:
+
+https://www.eclipse.org/articles/Article-Writing%20Your%20Own%20Widget/Writing%20Your%20Own%20Widget.htm
+
 ## Samples
 
-Check the [samples](samples) directory for examples on how to write Glimmer applications. To run a sample, make sure to install the `glimmer` gem first and then use the `glimmer` command to run it (alternatively, you may clone the repo, follow [CONTRIBUTING.md](CONTRIBUTING.md) instructions, and run samples locally with development glimmer command: `bin/glimmer`).
+Check the [samples](samples) directory in [glimmer-dsl-swt](https://github.com/AndyObtiva/glimmer-dsl-swt) for examples on how to write Glimmer applications. To run a sample, make sure to install the `glimmer` gem first and then use the `glimmer` command to run it (alternatively, you may clone the repo, follow [CONTRIBUTING.md](CONTRIBUTING.md) instructions, and run samples locally with development glimmer command: `bin/glimmer`).
 
-If you cloned the project and followed [CONTRIBUTING.md](CONTRIBUTING.md) instructions, you may run all samples at once via `samples/launch` command:
+If you cloned the project and followed [CONTRIBUTING.md](CONTRIBUTING.md) instructions, you may run all samples in [glimmer-dsl-swt](https://github.com/AndyObtiva/glimmer-dsl-swt) at once via `samples/launch` command:
 
 ```
 samples/launch
@@ -2092,168 +2599,306 @@ samples/launch
 
 ### Hello Samples
 
-For "Hello, World!" type samples, check the following:
+For hello-type simple samples, check the following.
+
+#### Hello, World! Sample
+
+Code:
+
+[samples/hello/hello_world.rb](https://github.com/AndyObtiva/glimmer-dsl-swt/blob/master/samples/hello/hello_world.rb)
+
+Run:
 
 ```
 glimmer samples/hello/hello_world.rb
-glimmer samples/hello/hello_browser.rb # demonstrates browser widget
-glimmer samples/hello/hello_tab.rb # demonstrates tabs
-glimmer samples/hello/hello_combo.rb # demonstrates combo data-binding
-glimmer samples/hello/hello_list_single_selection.rb # demonstrates list single-selection data-binding
-glimmer samples/hello/hello_list_multi_selection.rb # demonstrates list multi-selection data-binding
-glimmer samples/hello/hello_computed.rb # demonstrates computed data-binding
 ```
 
-### Elaborate Samples
+![Hello World](images/glimmer-hello-world.png)
 
-For more elaborate samples, check the following:
+#### Hello, Tab!
+
+Code:
+
+[samples/hello/hello_tab.rb](https://github.com/AndyObtiva/glimmer-dsl-swt/blob/master/samples/hello/hello_tab.rb)
+
+Run:
 
 ```
-glimmer samples/elaborate/login.rb # demonstrates basic data-binding
-glimmer samples/elaborate/contact_manager.rb # demonstrates table data-binding
-glimmer samples/elaborate/tic_tac_toe.rb # demonstrates a full MVC application
+glimmer samples/hello/hello_tab.rb
 ```
 
-### External Samples
+![Hello Tab English](images/glimmer-hello-tab-english.png)
+![Hello Tab French](images/glimmer-hello-tab-french.png)
 
-#### Glimmer Calculator
+#### Hello, Combo!
 
-[<img src="https://raw.githubusercontent.com/AndyObtiva/glimmer-cs-calculator/v1.0.0/glimmer-cs-calculator-screenshot.png" />](https://github.com/AndyObtiva/glimmer-cs-calculator)
+This sample demonstrates combo data-binding.
 
-[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).
+Code:
 
-#### Gladiator
+[samples/hello/hello_combo.rb](https://github.com/AndyObtiva/glimmer-dsl-swt/blob/master/samples/hello/hello_combo.rb)
 
-[<img src="https://raw.githubusercontent.com/AndyObtiva/glimmer-cs-gladiator/v0.1.5/images/glimmer-gladiator.png" />](https://github.com/AndyObtiva/glimmer-cs-gladiator)
+Run:
 
-[Gladiator](https://github.com/AndyObtiva/glimmer-cs-gladiator) (short for Glimmer Editor) is a Glimmer sample project under on-going development.
-You may check it out to learn how to build a Glimmer Custom Shell gem.
+```
+glimmer samples/hello/hello_combo.rb
+```
 
-## In Production
+![Hello Combo](images/glimmer-hello-combo.png)
+![Hello Combo Expanded](images/glimmer-hello-combo-expanded.png)
 
-The following production apps have been built with Glimmer:
+#### Hello, List Single Selection!
 
-[<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
+This sample demonstrates list single-selection data-binding.
 
-## SWT Reference
+Code:
 
-https://www.eclipse.org/swt/docs.php
+[samples/hello/hello_list_single_selection.rb](https://github.com/AndyObtiva/glimmer-dsl-swt/blob/master/samples/hello/hello_list_single_selection.rb)
 
-Here is the SWT API:
+Run:
 
-https://help.eclipse.org/2019-12/nftopic/org.eclipse.platform.doc.isv/reference/api/index.html
+```
+glimmer samples/hello/hello_list_single_selection.rb
+```
 
-Here is a visual list of SWT widgets:
+![Hello List Single Selection](images/glimmer-hello-list-single-selection.png)
 
-https://www.eclipse.org/swt/widgets/
+#### Hello, List Multi Selection!
 
-Here is a textual list of SWT widgets:
+This sample demonstrates list multi-selection data-binding.
 
-https://help.eclipse.org/2019-12/topic/org.eclipse.platform.doc.isv/guide/swt_widgets_controls.htm?cp=2_0_7_0_0
+Code:
 
-Here is a list of SWT style bits as used in widget declaration:
+[samples/hello/hello_list_multi_selection.rb](https://github.com/AndyObtiva/glimmer-dsl-swt/blob/master/samples/hello/hello_list_multi_selection.rb)
 
-https://wiki.eclipse.org/SWT_Widget_Style_Bits
+Run:
 
-Here is a SWT style bit constant reference:
+```
+glimmer samples/hello/hello_list_multi_selection.rb
+```
 
-https://help.eclipse.org/2019-12/nftopic/org.eclipse.platform.doc.isv/reference/api/org/eclipse/swt/SWT.html
+![Hello List Multi Selection](images/glimmer-hello-list-multi-selection.png)
+
+#### Hello, Computed!
 
-## SWT Packages
+This sample demonstrates computed data-binding.
 
-Glimmer automatically imports all SWT Java packages upon adding `include Glimmer` to a class or module.
+Code:
+
+[samples/hello/hello_computed.rb](https://github.com/AndyObtiva/glimmer-dsl-swt/blob/master/samples/hello/hello_computed.rb)
+
+Run:
 
-Here are the Java packages imported:
 ```
-org.eclipse.swt.*
-org.eclipse.swt.widgets.*
-org.eclipse.swt.layout.*
-org.eclipse.swt.graphics.*
-org.eclipse.swt.browser.*
-org.eclipse.swt.custom.*
+glimmer samples/hello/hello_computed.rb
 ```
 
-This allows you to call SWT Java classes from Ruby without mentioning Java package references.
+![Hello Browser](images/glimmer-hello-computed.png)
 
-For example, after imports, `org.eclipse.swt.graphics.Color` can be referenced by just `Color`
+#### Hello, Message Box!
 
-Nonetheless, you can disable automatic import if needed via this Glimmer configuration option:
+This sample demonstrates a `message_box` dialog.
 
-```ruby
-Glimmer::Config.import_swt_packages = false
+Code:
+
+[samples/hello/hello_message_box.rb](https://github.com/AndyObtiva/glimmer-dsl-swt/blob/master/samples/hello/hello_message_box.rb)
+
+Run:
+
+```
+glimmer samples/hello/hello_message_box.rb
 ```
 
-To import SWT Java packages manually instead, you have 2 options:
+![Hello Message Box](images/glimmer-hello-message-box.png)
+![Hello Message Box Dialog](images/glimmer-hello-message-box-dialog.png)
 
-1. `include Glimmer::SwtPackages`: lazily imports all SWT Java packages to your class, lazy-loading SWT Java class constants on first reference.
+#### Hello, Browser!
 
-2. `java_import swt_package_class_string`: immediately imports a specific Java class where `swt_package_class_string` is the Java full package reference of a Java class (e.g. `java_import 'org.eclipse.swt.SWT'`)
+This sample demonstrates the `browser` widget.
 
-Note: Glimmer relies on [`nested_imported_jruby_include_package`](https://github.com/AndyObtiva/nested_inherited_jruby_include_package), which automatically brings packages to nested-modules/nested-classes and sub-modules/sub-classes.
+Code:
 
-You can learn more about importing Java packages into Ruby code at this JRuby WIKI page:
+[samples/hello/hello_browser.rb](https://github.com/AndyObtiva/glimmer-dsl-swt/blob/master/samples/hello/hello_browser.rb)
 
-https://github.com/jruby/jruby/wiki/CallingJavaFromJRuby
+Run:
 
-## Logging
+```
+glimmer samples/hello/hello_browser.rb
+```
 
-Glimmer comes with a Ruby Logger accessible via `Glimmer::Config.logger`
-Its level of logging defaults to `Logger::WARN`
-It may be configured to show a different level of logging as follows:
-```ruby
-Glimmer::Config.enable_logging
-Glimmer::Config.logger.level = Logger::DEBUG
+![Hello Browser](images/glimmer-hello-browser.png)
+
+#### Hello, Drag and Drop!
+
+This sample demonstrates drag and drop in Glimmer.
+
+Code:
+
+[samples/hello/hello_drag_and_drop.rb](https://github.com/AndyObtiva/glimmer-dsl-swt/blob/master/samples/hello/hello_drag_and_drop.rb)
+
+Run:
+
+```
+glimmer samples/hello/hello_drag_and_drop.rb
 ```
-This results in more verbose debugging log to `STDOUT`, which is helpful in troubleshooting Glimmer DSL syntax when needed.
 
-Example log:
+![Hello Drag and Drop](images/glimmer-hello-drag-and-drop.gif)
+
+#### Hello, Menu Bar!
+
+This sample demonstrates menus in Glimmer.
+
+Code:
+
+[samples/hello/hello_menu_bar.rb](https://github.com/AndyObtiva/glimmer-dsl-swt/blob/master/samples/hello/hello_menu_bar.rb)
+
+Run:
+
 ```
-D, [2017-07-21T19:23:12.587870 #35707] DEBUG -- : method: shell and args: []
-D, [2017-07-21T19:23:12.594405 #35707] DEBUG -- : ShellCommandHandler will handle command: shell with arguments []
-D, [2017-07-21T19:23:12.844775 #35707] DEBUG -- : method: composite and args: []
-D, [2017-07-21T19:23:12.845388 #35707] DEBUG -- : parent is a widget: true
-D, [2017-07-21T19:23:12.845833 #35707] DEBUG -- : on listener?: false
-D, [2017-07-21T19:23:12.864395 #35707] DEBUG -- : WidgetCommandHandler will handle command: composite with arguments []
-D, [2017-07-21T19:23:12.864893 #35707] DEBUG -- : widget styles are: []
-D, [2017-07-21T19:23:12.874296 #35707] DEBUG -- : method: list and args: [:multi]
-D, [2017-07-21T19:23:12.874969 #35707] DEBUG -- : parent is a widget: true
-D, [2017-07-21T19:23:12.875452 #35707] DEBUG -- : on listener?: false
-D, [2017-07-21T19:23:12.878434 #35707] DEBUG -- : WidgetCommandHandler will handle command: list with arguments [:multi]
-D, [2017-07-21T19:23:12.878798 #35707] DEBUG -- : widget styles are: [:multi]
+glimmer samples/hello/hello_menu_bar.rb
 ```
 
-## Raw JRuby Command
+![Hello Menu Bar](images/glimmer-hello-menu-bar.png)
+![Hello Menu Bar File Menu](images/glimmer-hello-menu-bar-file-menu.png)
+![Hello Menu Bar History Menu](images/glimmer-hello-menu-bar-history-menu.png)
 
-If there is a need to run Glimmer directly via the `jruby` command, you
-may run the following:
+#### Hello, Pop Up Context Menu!
+
+This sample demonstrates pop up context menus in Glimmer.
+
+Code:
+
+[samples/hello/hello_pop_up_context_menu.rb](https://github.com/AndyObtiva/glimmer-dsl-swt/blob/master/samples/hello/hello_pop_up_context_menu.rb)
+
+Run:
 
 ```
-jruby -J-classpath "path_to/swt.jar" -r glimmer -S application.rb
+glimmer samples/hello/hello_pop_up_context_menu.rb
 ```
 
-The `-J-classpath` option specifies the `swt.jar` file path, which can be a
-manually downloaded version of SWT, or otherwise the one included in the gem. You can lookup the one included in the gem by running `jgem which glimmer` to find the gem path and then look through the `vendor` directory.
+![Hello Pop Up Context Menu](images/glimmer-hello-pop-up-context-menu.png)
+![Hello Pop Up Context Menu Popped Up](images/glimmer-hello-pop-up-context-menu-popped-up.png)
 
-The `-r` option preloads (requires) the `glimmer` library in Ruby.
+### Elaborate Samples
 
-The `-S` option specifies a script to run.
+For more elaborate samples, check the following:
 
-### Mac Support
+#### Login
 
-Mac is well supported with the `glimmer` command. However, if there is a reason to use the raw jruby command, you need to pass an extra option (`-J-XstartOnFirstThread`) to JRuby on the Mac.
+This sample demonstrates basic data-binding, password and text fields, and field enablement data-binding.
+
+Code:
+
+[samples/elaborate/login.rb](https://github.com/AndyObtiva/glimmer-dsl-swt/blob/master/samples/elaborate/login.rb)
+
+Run:
 
-Example:
 ```
-jruby -J-XstartOnFirstThread -J-classpath "path_to/swt.jar" -r glimmer -S application.rb
+glimmer samples/elaborate/login.rb
+```
+
+![Login](images/glimmer-login.png)
+![Login Filled In](images/glimmer-login-filled-in.png)
+![Login Logged In](images/glimmer-login-logged-in.png)
+
+#### Tic Tac Toe Sample
+
+This sample demonstrates a full MVC application, including GUI layout, text and enablement data-binding, and test-driven development (has [specs](https://github.com/AndyObtiva/glimmer-dsl-swt/blob/master/spec/samples/elaborate/tic_tac_toe/board_spec.rb)).
+
+Code:
+
+[samples/elaborate/tic_tac_toe.rb](https://github.com/AndyObtiva/glimmer-dsl-swt/blob/master/samples/elaborate/tic_tac_toe.rb)
+
+Run:
+
+```
+glimmer samples/elaborate/tic_tac_toe.rb
 ```
 
+![Tic Tac Toe](images/glimmer-tic-tac-toe.png)
+![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
+
+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)).
+
+Code:
+
+[samples/elaborate/contact_manager.rb](https://github.com/AndyObtiva/glimmer-dsl-swt/blob/master/samples/elaborate/contact_manager.rb)
+
+Run:
+
+```
+glimmer samples/elaborate/contact_manager.rb
+```
+
+Contact Manager
+
+![Contact Manager](images/glimmer-contact-manager.png)
+
+Contact Manager - Find
+
+![Contact Manager](images/glimmer-contact-manager-find.png)
+
+Contact Manager - Edit Started
+
+![Contact Manager](images/glimmer-contact-manager-edit-started.png)
+
+Contact Manager - Edit In Progress
+
+![Contact Manager](images/glimmer-contact-manager-edit-in-progress.png)
+
+Contact Manager - Edit Done
+
+![Contact Manager](images/glimmer-contact-manager-edit-done.png)
+
+### External Samples
+
+#### 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 src="https://raw.githubusercontent.com/AndyObtiva/glimmer-cs-calculator/master/glimmer-cs-calculator-screenshot.png" />](https://github.com/AndyObtiva/glimmer-cs-calculator)
+
+#### Gladiator
+
+[<img src='https://raw.githubusercontent.com/AndyObtiva/glimmer-cs-gladiator/master/images/glimmer-cs-gladiator-logo.svg' height=40 /> Gladiator](https://github.com/AndyObtiva/glimmer-cs-gladiator) (short for Glimmer Editor) is a Glimmer sample project under on-going development.
+You may check it out to learn how to build a Glimmer Custom Shell gem.
+
+[<img src="https://raw.githubusercontent.com/AndyObtiva/glimmer-cs-gladiator/master/images/glimmer-gladiator.png" />](https://github.com/AndyObtiva/glimmer-cs-gladiator)
+
+Gladiator is a good demonstration of:
+- MVP Pattern
+- Tree data-binding
+- List data-binding
+- Text selection data-binding
+- Tabs
+- Context menus
+- Custom Shell
+- Custom widget
+
+## In Production
+
+The following production apps have been built with Glimmer.
+
+### 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
+
+### Are We There Yet?
+
+[<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. 
+
 ## Packaging & Distribution
 
 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.
 
-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](https://github.com/AndyObtiva/glimmer/blob/master/README.md#scaffolding):
+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 package
@@ -2391,10 +3036,6 @@ 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
 ```
 
-## Limitations
-
-- Glimmer apps have a long startup up time and can take anywhere between 12 and 30 seconds to start depending on the app and the machine. Once started, Glimmer apps run very fast and perform very responsively since Ruby is more than fast and capable for handling desktop GUIs. In any case, one idea to address this limitation is to include a background service (daemon) that can launch Glimmer apps instantly or near instantly by keeping a JRuby runtime started and ready at all times.
-
 ## Resources
 
 * [Code Master Blog](http://andymaleh.blogspot.com/search/label/Glimmer)
@@ -2412,24 +3053,38 @@ You may submit [issues](https://github.com/AndyObtiva/glimmer/issues) on [GitHub
 
 [Click here to submit an issue.](https://github.com/AndyObtiva/glimmer/issues)
 
-### IRC Channel
+### Chat
 
-If you need live help, try the [#glimmer](http://widget.mibbit.com/?settings=7514b8a196f8f1de939a351245db7aa8&server=irc.mibbit.net&channel=%23glimmer) IRC channel on [irc.mibbit.net](http://widget.mibbit.com/?settings=7514b8a196f8f1de939a351245db7aa8&server=irc.mibbit.net&channel=%23glimmer). If no one was available, you may [leave a GitHub issue](https://github.com/AndyObtiva/glimmer/issues) to schedule a meetup on IRC. 
-
-[Click here to connect to #glimmer IRC channel immediately via a web interface.](http://widget.mibbit.com/?settings=7514b8a196f8f1de939a351245db7aa8&server=irc.mibbit.net&channel=%23glimmer)
+If you need live help, try to [![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) 
 
 ## Feature Suggestions
 
 These features have been suggested. You might see them in a future version of Glimmer. You are welcome to contribute more feature suggestions.
 
-[TODO.md](https://github.com/AndyObtiva/glimmer-dsl-swt/blob/master/TODO.md)
+[glimmer-dsl-swt/TODO.md](https://github.com/AndyObtiva/glimmer-dsl-swt/blob/master/TODO.md)
+
+Glimmer DSL Engine specific tasks are at:
+
+[TODO.md](TODO.md)
 
 ## 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 (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)
+- [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)
+
 [CONTRIBUTING.md](CONTRIBUTING.md)
 
 ## Contributors
@@ -2439,7 +3094,17 @@ These features have been suggested. You might see them in a future version of Gl
 
 [Click here to view contributor commits.](https://github.com/AndyObtiva/glimmer/graphs/contributors)
 
+## Hire Me
+
+If your company would like to invest fulltime in further development of the Glimmer open-source project, [hire me](https://www.linkedin.com/in/andymaleh/).
+
 ## 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>