glimmer 1.1.0 → 1.3.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: c181d967c5d8c834867570a112937498dd4d45c9585f357a683368de979967c1
-  data.tar.gz: 50a1ed33fd43a34e500de9ce2954d02ffc511204108c8d80b99eb31b885c8f1a
+  metadata.gz: 351035b802dcf014c087c908f8481dbbf13d8479fdd1766b47e25be2177ffc98
+  data.tar.gz: 7960514819570b96106dcde2c71889feb0bd706dbe5803e3e62bf02c28f4c1f1
 SHA512:
-  metadata.gz: 8a1d46f0e7f051000acbcf5756dd3c15a892583557388a181d47186e74a39f4eeb27c3c05b94780cae47c67f8b5a3e4c8a237cd5ce94c551cbb0eec8a6494af3
-  data.tar.gz: 54ce9ae27a6f5f4b320783ec1e107cde725435da3e3bb3199bb6ff44a89f647de81339654be98d06a903aed3feb4caf096bbc80d9c9e9df8ef194e3c9789b8a4
+  metadata.gz: f127846dc71e67d3667cd738a96f11d667718d93f28494e31414a29a6e93b323f04af33bcc022bb8a4cc96e413622209589f1f2ab2ba5efc10bf5bce6baf33f7
+  data.tar.gz: 6a300696cb179c0d01173fd4a652d6ef78219ad944ff2af9ef7fbfec19e9a853365631f92bae5c7b2353946a2c2e498d178f14f96ee357f61a02b872b1e17537

data/CHANGELOG.md

@@ -3,6 +3,27 @@
 Related Change Logs:
 - [glimmer-dsl-swt/CHANGELOG.md](https://github.com/AndyObtiva/glimmer-dsl-swt/blob/master/CHANGELOG.md)
 
+### 1.3.1
+
+- Use `Concurrent::Array` instead of `Array` in `Glimmer::DataBinding::ModelBinding`
+
+### 1.3.0
+
+- Support the `Expression#around` hook, which executes code around both `interpret` and `add_content`
+
+## 1.2.0
+
+- Alter `Engine`/`Expression`/`ParentExpression` API to pass `keyword` and `args` to `#add_content` method. This enables consumers to vary behavior based on `keyword` and `args`, not just `parent` and presence of `block`.
+
+## 1.1.2
+
+- Add more logging for which DSL is assumed before interpreting expressions
+- Switch DSL Engine puts statement to a log statement for the error about no DSLs available
+
+## 1.1.1
+
+- Ensured after_read hook truly happens after notifying observers in ModelBinding
+
 ## 1.1.0
 
 - ModelBinding hooks for before_read, after_read, before_write, after_write

data/README.md

@@ -1,4 +1,4 @@
-# [<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 1.1.0 - DSL Framework for GUI and More
+# [<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 - DSL Framework for Ruby GUI and More
 [![Gem Version](https://badge.fury.io/rb/glimmer.svg)](http://badge.fury.io/rb/glimmer)
 [![rspec](https://github.com/AndyObtiva/glimmer/workflows/rspec/badge.svg)](https://github.com/AndyObtiva/glimmer/actions?query=workflow%3Arspec)
 [![Coverage Status](https://coveralls.io/repos/github/AndyObtiva/glimmer/badge.svg?branch=master)](https://coveralls.io/github/AndyObtiva/glimmer?branch=master)
@@ -7,7 +7,7 @@
 
 **[Contributors Wanted! (Submit a Glimmer App Sample to Get Started)](#contributing)**
 
-**(The Original Glimmer Library Since 2007. Beware of Imitators!)**
+**(The Original Glimmer Library Handling the World’s Ruby GUI Needs Since 2007. Beware of Imitators!)**
 
 [**Glimmer**](https://rubygems.org/gems/glimmer) started out as a [GUI Library](https://github.com/AndyObtiva/glimmer-dsl-swt) and grew into a full-fledged [DSL Framework](#dsl-engine) with support for multiple GUI DSLs. Glimmer's namesake is referring to the Glimmer of Ruby in Graphical User Interfaces (contrary to [popular myth](http://blog.headius.com/2007/11/tab-sweep.html) perpetrated by [Charles Nutter](http://blog.headius.com/2007/11/tab-sweep.html), Glimmer has nothing to do with the ill-fated Whitney Houston movie, which does not in fact share the same name)
 
@@ -27,6 +27,8 @@ Featured in JRuby Cookbook](http://shop.oreilly.com/product/9780596519650.do) an
 - Multiple DSLs may be [mixed](#multi-dsl-support) together safely to achieve maximum expressability, composability, and productivity.
 - DSLs are fully configurable, so you may activate and deactivate DSLs as per your current needs only.
 
+Start by checking out Glimmer's original GUI DSL, which got extracted into its own gem: [Glimmer DSL for SWT](https://github.com/AndyObtiva/glimmer-dsl-swt)
+
 [**Glimmer**](https://rubygems.org/gems/glimmer) supports the following DSLs:
 - [glimmer-dsl-swt](https://github.com/AndyObtiva/glimmer-dsl-swt): Glimmer DSL for SWT (JRuby Desktop Development GUI Framework)
 - [glimmer-dsl-opal](https://github.com/AndyObtiva/glimmer-dsl-opal): Glimmer DSL for Opal (Pure Ruby Web GUI and Auto-Webifier of Desktop Apps)
@@ -38,15 +40,17 @@ Featured in JRuby Cookbook](http://shop.oreilly.com/product/9780596519650.do) an
 
 ## Table of Contents
 
-- [Glimmer 1.1.0](#-glimmer-110---dsl-framework-for-gui-and-more)
-  - [Official DSLs](#official-dsls)
-    - [Glimmer DSL for SWT (JRuby Desktop Development GUI Framework)](#glimmer-dsl-for-swt-jruby-desktop-development-gui-framework)
-    - [Glimmer DSL for Opal (Pure Ruby Web GUI and Auto-Webifier of Desktop Apps)](#glimmer-dsl-for-opal-pure-ruby-web-gui-and-auto-webifier-of-desktop-apps)
-    - [Glimmer DSL for XML (& HTML)](#glimmer-dsl-for-xml--html)
-    - [Glimmer DSL for CSS](#glimmer-dsl-for-css)
-    - [Glimmer DSL for Tk (MRI Ruby Desktop Development GUI Library)](#glimmer-dsl-for-tk-mri-ruby-desktop-development-gui-library)
+- [Glimmer](#-glimmer---dsl-framework-for-ruby-gui-and-more)
   - [DSL Engine](#dsl-engine)
+    - [Setup](#setup)
+    - [Configuration](#configuration)
     - [Multi-DSL Support](#multi-dsl-support)
+    - [Official DSLs](#official-dsls)
+      - [Glimmer DSL for SWT (JRuby Desktop Development GUI Framework)](#glimmer-dsl-for-swt-jruby-desktop-development-gui-framework)
+      - [Glimmer DSL for Opal (Pure Ruby Web GUI and Auto-Webifier of Desktop Apps)](#glimmer-dsl-for-opal-pure-ruby-web-gui-and-auto-webifier-of-desktop-apps)
+      - [Glimmer DSL for XML (& HTML)](#glimmer-dsl-for-xml--html)
+      - [Glimmer DSL for CSS](#glimmer-dsl-for-css)
+      - [Glimmer DSL for Tk (MRI Ruby Desktop Development GUI Library)](#glimmer-dsl-for-tk-mri-ruby-desktop-development-gui-library)
   - [Data-Binding Library](#data-binding-library)
   - [Glimmer Process](#glimmer-process)
   - [Resources](#resources)
@@ -60,21 +64,301 @@ Featured in JRuby Cookbook](http://shop.oreilly.com/product/9780596519650.do) an
   - [Hire Me](#hire-me)
   - [License](#license)
 
-## Official DSLs
+## DSL Engine
+
+Glimmer is fundamentally a DSL Engine that can support any number of DSLs like the official Glimmer DSLs (gems starting with the `glimmer-dsl-` prefix like `glimmer-dsl-swt`) or any DSLs for that matter.
+
+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)
+
+The Glimmer DSL Engine's architecture is based on the following Design Patterns and Data Structures:
+- **Interpreter Design Pattern**: to define interpretable expressions of DSL keywords
+- **Chain of Responsibility Design Pattern / Queue Data Structure**: to chain expression handlers in order of importance for processing DSL keywords
+- **Adapter Design Pattern**: to adapt expressions into handlers in a chain of responsibility
+- **Stack Data Structure**: to handle processing parent/child nesting of DSL keyword expressions in the correct order
+
+Glimmer's use of the **Interpreter Design Pattern** in processing DSLs is also known as the **Virtual Machine Architectural Style**. After all, DSL expressions are virtual machine opcodes that process nested keywords stored in a stack. I built Glimmer's original DSL back in 2007 without knowing the **Virtual Machine Architectural Style** (except perhaps as an esoteric technology powering Java), but stumbled upon it anyways through following the Gang of Four Design Patterns mentioned above, chiefly the **Interpreter Design Pattern**.
+
+Every keyword in a Glimmer DSL is represented by a DSL expression that is processed by an `Expression` subclass selected from a chain of expressions (interpreters) pre-configured in a DSL chain of responsibility via `Glimmer::DSL::Engine.add_dynamic_expressions(DSLNameModule, expression_names_array)`.
+
+Expressions are either:
+- **Static** (subclass of `StaticExpression`, which is a subclass of `Expression`): if they represent a single pre-identified keyword (e.g. `color` or `display`)
+- **Dynamic** (subclass of `Expression`): if they represent keywords calculated on the fly during processing (e.g. an SWT widget like `label` or a random XML element called `folder` representing `<folder></folder>`)
+
+Optionally, expressions can be parent expressions that contain other expressions, and must include the `ParentExpression` mixin module as such.
+
+Additionally, every expression that serves as a top-level entry point into the DSL must mixin `TopLevelExpression`
+
+Static expressions are optimized in performance since they pre-define methods on the `Glimmer` module matching the static keywords they represent (e.g. `color` causes creating a `Glimmer#color` method for processing `color` expressions) and completely bypass as a result the Glimmer DSL Engine Chain of Responsibility. That said, they must be avoided if the same keyword might occur multiple times, but with different requirements for arguments, block, and parenthood type.
+
+Every `Expression` sublcass must specify two methods at least:
+- `can_interpret?(parent, keyword, *args, &block)`: to quickly test if the keyword and arg/block/parent combination qualifies for interpretation by the current `Expression` or to otherwise delegate to the next expression in the chain of responsibility.
+- `interpret(parent, keyword, *args, &block)`: to go ahead and interpret a DSL expression that qualified for interpretation
+
+`StaticExpression` sublcasses may skip the `can_interpret?` method since they include a default implementation for it that matches the name of the keyword from the class name by convention. For example, a `color` keyword would have a `ColorExpression` class, so `color` is inferred automatically from class name and used in deciding whether the class can handle a `color` keyword or not.
+
+`ParentExpression` subclasses can optionally override this extra method, which is included by default and simply invokes the parent's passed block to process its children:
+- `add_content(parent, keyword, *args, &block)`
+
+For example, some parent widgets use their block for other reasons or process their children at very specific times, so they may override that method and disable it, or otherwise call `super` and do additional work.
+
+Otherwise, all expressions support the `around` hook method:
+- `around(parent, keyword, args, block, &interpret_and_add_content)`: a hook for executing code around both `interpret` and `add_content`. Clients may invoke `interpret_and_add_content.call` or `yield` when ready for interpretation. `parent`, `keyword`, `args`, and `block` are supplied in case they are needed in the `around` logic.
+
+Example of a dynamic expression:
+
+```ruby
+module Glimmer
+  module DSL
+    module SWT
+      class WidgetExpression < Expression
+        include ParentExpression
+
+        EXCLUDED_KEYWORDS = %w[shell display tab_item]
+
+        def can_interpret?(parent, keyword, *args, &block)
+          !EXCLUDED_KEYWORDS.include?(keyword) and
+            parent.respond_to?(:swt_widget) and
+            Glimmer::SWT::WidgetProxy.widget_exists?(keyword)
+        end
+
+        def interpret(parent, keyword, *args, &block)
+          Glimmer::SWT::WidgetProxy.create(keyword, parent, args)
+        end
+
+        def add_content(parent, keyword, *args, &block)
+          super
+          parent.post_add_content
+        end
+
+      end
+    end
+  end
+end
+```
+
+Example of a static expression (does not need `can_interpret?`):
+
+```ruby
+module Glimmer
+  module DSL
+    module Opal
+      class ColorExpression < StaticExpression
+        include TopLevelExpression
+  
+        def interpret(parent, keyword, *args, &block)
+          Glimmer::SWT::ColorProxy.new(*args)
+        end
+      end
+    end
+  end
+end
+```
+
+DSL expressions go into the `glimmer/dsl/{dsl_name}` namespace directory.
+
+Also, every DSL requires a `glimmer/dsl/{dsl_name}/dsl.rb` file, which configures the DSL into Glimmer via a call to:
+```ruby
+Glimmer::DSL::Engine.add_dynamic_expressions(DSLNameModule, expression_names_array)
+```
+
+Expression names are underscored verions of `Expression` subclass names minus the `_expression` suffix.
+
+For example, here is an SWT DSL configuration:
+
+```ruby
+require 'glimmer/launcher'
+require Glimmer::Launcher.swt_jar_file
+require 'glimmer/dsl/engine'
+Dir[File.expand_path('../*_expression.rb', __FILE__)].each {|f| require f}
+
+module Glimmer
+  module DSL
+    module SWT
+      Engine.add_dynamic_expressions(
+        SWT,
+        %w[
+          layout
+          widget_listener
+          combo_selection_data_binding
+          checkbox_group_selection_data_binding
+          radio_group_selection_data_binding
+          list_selection_data_binding
+          tree_items_data_binding
+          table_items_data_binding
+          data_binding
+          cursor
+          font
+          image
+          property
+          block_property
+          widget
+          custom_widget
+        ]
+      )
+    end
+  end
+end
+```
+
+### Setup
+
+Follow these steps to author a [Glimmer](https://rubygems.org/gems/glimmer) DSL:
+- Add `gem 'glimmer', '~> 1.3.1'` to `Gemfile` and run `bundle` or run `gem install glimmer -v1.3.1` and add `require 'glimmer'`
+- Create `glimmer/dsl/[dsl_name]/dsl.rb`, which requires and adds all dynamic expressions for the [dsl_name] Glimmer DSL module as per the code shown in the previous section (or [Official DSLs](#official-dsls) as examples)
+- Create `glimmer/dsl/[dsl_name]/[expresion_name]_expresion.rb` for every [expresion_name] expression needed, whether dynamic or static
+
+### Configuration
+
+Glimmer configuration may be done via the [`Glimmer::Config`](https://github.com/AndyObtiva/glimmer/blob/master/lib/glimmer/config.rb) module.
+
+#### 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.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]
+```
+
+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.
+
+#### 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`
+
+#### 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
+
+(default = false)
+
+This just tells Glimmer whether to log excluded keywords or not (at the debug level). It is off by default.
+
+
+### Multi-DSL Support
+
+The Glimmer [DSL Engine](#dsl-engine) allows mixing DSLs, which comes in handy when doing things like rendering a desktop GUI DSL `browser` widget additionally leveraging the HTML DSL and CSS DSL for its content.
+
+DSLs are activated by top-level keywords (expressions denoted as `TopLevelExpression`). For example, the `html` keyword activates the [Glimmer DSL for XML](https://github.com/AndyObtiva/glimmer-dsl-xml) and the `css` keyword activates the [Glimmer DSL for CSS](https://github.com/AndyObtiva/glimmer-dsl-css). Glimmer automatically recognizes top-level keywords in each DSL and activates the DSL accordingly. Once done processing a nested DSL top-level keyword, Glimmer switches back to the prior DSL automatically.
+
+By default, all loaded DSLs (required glimmer DSL gems) are enabled.
+
+For example, this shows "Hello, World!" inside a [Glimmer DSL for SWT](https://github.com/AndyObtiva/glimmer-dsl-swt) desktop app `browser` widget using `html` and `css` from [Glimmer DSL for XML](https://github.com/AndyObtiva/glimmer-dsl-xml) and [Glimmer DSL for CSS](https://github.com/AndyObtiva/glimmer-dsl-css):
+
+```ruby
+require 'glimmer-dsl-swt'
+require 'glimmer-dsl-xml'
+require 'glimmer-dsl-css'
+
+include Glimmer
+
+shell {
+  minimum_size 130, 130
+  @browser = browser {
+    text html {
+      head {
+        meta(name: "viewport", content: "width=device-width, initial-scale=2.0")
+        style {
+          css {
+            h1 {
+              background 'yellow'
+            }
+          }
+        }
+      }
+      body {
+        h1 { "Hello, World!" }
+      }
+    }
+  }
+}.open
+```
+
+**API methods to enable/disable DSLs:**
+
+`Glimmer::DSL::Engine.disable_dsl(dsl)`: disables a particular DSL
+
+Example: `Glimmer::DSL::Engine.disable_dsl(:swt)`
+
+`Glimmer::DSL::Engine.enable_dsl(dsl)`: enables a particular DSL
+
+Example: `Glimmer::DSL::Engine.disable_dsl(:swt)`
+
+`Glimmer::DSL::Engine.enabled_dsls=(dsls)`: enables only the specified DSLs, disabling all other loaded DSLs
+
+Example: `Glimmer::DSL::Engine.enabled_dsls = [:xml, :css]`
+
+### Official DSLs
 
 Here, we showcase official Glimmer DSLs; that is [gems starting with the `glimmer-dsl-` prefix](https://rubygems.org/search?query=glimmer-dsl-).
 
 (you can skip ahead if you prefer to learn more about the Glimmer [DSL Engine](#dsl-engine) or [Data-Binding Library](#data-binding-library) first)
 
-### Glimmer DSL for SWT (JRuby Desktop Development GUI Framework)
+#### Glimmer DSL for SWT (JRuby Desktop Development GUI Framework)
 
 [Glimmer DSL for SWT](https://github.com/AndyObtiva/glimmer-dsl-swt) 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](https://github.com/AndyObtiva/glimmer-dsl-swt#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 DSL for SWT](https://github.com/AndyObtiva/glimmer-dsl-swt) additionally innovates by having built-in [data-binding](https://github.com/AndyObtiva/glimmer-dsl-swt#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, or alternatively drive development GUI-first, and then write clean business models (test-first) afterwards. To get started quickly, [Glimmer DSL for SWT](https://github.com/AndyObtiva/glimmer-dsl-swt) offers [scaffolding](https://github.com/AndyObtiva/glimmer-dsl-swt#scaffolding) options for [Apps](https://github.com/AndyObtiva/glimmer-dsl-swt#in-production), [Gems](https://github.com/AndyObtiva/glimmer-dsl-swt#custom-shell-gem), and [Custom Widgets](https://github.com/AndyObtiva/glimmer-dsl-swt#custom-widgets). [Glimmer DSL for SWT](https://github.com/AndyObtiva/glimmer-dsl-swt) also includes native-executable [packaging](https://github.com/AndyObtiva/glimmer-dsl-swt#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).
 
 To get started, visit the [Glimmer DSL for SWT project page](https://github.com/AndyObtiva/glimmer-dsl-swt#pre-requisites) for instructions on installing the [glimmer-dsl-swt gem](https://rubygems.org/gems/glimmer-dsl-swt).
 
-#### Glimmer DSL for SWT Samples
+##### Glimmer DSL for SWT Samples
 
-##### Hello, World!
+###### Hello, World!
 
 ![Hello World](images/glimmer-hello-world.png)
 
@@ -90,7 +374,7 @@ shell {
 }.open
 ```
 
-##### Glimmer Tetris
+###### Glimmer Tetris
 
 ![Tetris](https://raw.githubusercontent.com/AndyObtiva/glimmer-dsl-swt/v4.18.3.1/images/glimmer-tetris.png)
 
@@ -118,15 +402,11 @@ Glimmer GUI code (from [samples/elaborate/tetris.rb](https://github.com/AndyObti
       score_lane(game: game, block_size: BLOCK_SIZE) {
         layout_data(:fill, :fill, true, true)
       }
-      
-      on_widget_disposed {
-        deregister_observers
-      }
     }
 # ...
 ```
 
-##### Hello, Table!
+###### Hello, Table!
 
 ![Hello Table](https://raw.githubusercontent.com/AndyObtiva/glimmer-dsl-swt/master/images/glimmer-hello-table.png)
 
@@ -225,7 +505,7 @@ Glimmer GUI code (from [samples/hello/hello_table.rb](https://github.com/AndyObt
 # ...
 ```
 
-#### Production Desktop Apps Built with Glimmer DSL for SWT
+##### Production Desktop Apps Built with Glimmer DSL for SWT
 
 [<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) - Small Project Tracking App
 
@@ -239,7 +519,7 @@ Glimmer GUI code (from [samples/hello/hello_table.rb](https://github.com/AndyObt
 
 [![Garderie Rainbow Daily Agenda App Screenshot](https://raw.githubusercontent.com/AndyObtiva/garderie_rainbow_daily_agenda/master/images/garderie_rainbow_daily_agenda_screenshot.png)](https://github.com/AndyObtiva/garderie_rainbow_daily_agenda)
 
-### Glimmer DSL for Opal (Pure Ruby Web GUI and Auto-Webifier of Desktop Apps)
+#### Glimmer DSL for Opal (Pure Ruby Web GUI and Auto-Webifier of Desktop Apps)
 
 [Glimmer DSL for Opal](https://github.com/AndyObtiva/glimmer-dsl-opal) is an experimental proof-of-concept web GUI adapter for [Glimmer](https://github.com/AndyObtiva/glimmer) desktop apps (i.e. apps built with [Glimmer DSL for SWT](https://github.com/AndyObtiva/glimmer-dsl-swt)). It webifies them via [Rails](https://rubyonrails.org/), allowing Ruby desktop apps to run on the web via [Opal Ruby](https://opalrb.com/) without changing a line of code. Apps may then be custom-styled for the web with standard CSS.
 
@@ -247,9 +527,9 @@ Glimmer DSL for Opal webifier successfully reuses the entire [Glimmer](https://g
 
 To get started, visit the [Glimmer DSL for Opal project page](https://github.com/AndyObtiva/glimmer-dsl-opal) for instructions on installing the [glimmer-dsl-opal gem](https://rubygems.org/gems/glimmer-dsl-opal).
 
-#### Glimmer DSL for Opal Samples
+##### Glimmer DSL for Opal Samples
 
-##### Hello, Computed!
+###### Hello, Computed!
 
 Add the following require statement to `app/assets/javascripts/application.rb`
 
@@ -368,7 +648,7 @@ You should see "Hello, Computed!"
 
 ![Glimmer DSL for Opal Hello Computed](https://raw.githubusercontent.com/AndyObtiva/glimmer-dsl-opal/master/images/glimmer-dsl-opal-hello-computed.png)
 
-##### Glimmer Calculator
+###### Glimmer Calculator
 
 Add the [glimmer-cs-calculator](https://github.com/AndyObtiva/glimmer-cs-calculator) gem to `Gemfile` (without requiring):
 
@@ -385,6 +665,7 @@ require 'glimmer-cs-calculator/launch'
 Sample GUI code (relies on custom widgets `command_button`, `operation_button`, and `number_button`):
 
 ```ruby
+# ...
 shell {
   minimum_size (OS.mac? ? 320 : (OS.windows? ? 390 : 520)), 240
   image File.join(APP_ROOT, 'package', 'windows', "Glimmer Calculator.ico") if OS.windows?
@@ -403,9 +684,9 @@ shell {
     caret nil
   }
   command_button('AC')
-  operation_button('÷')
-  operation_button('�')
-  operation_button('−')
+  operation_button('÷')
+  operation_button('×')
+  operation_button('−')
   (7..9).each { |number|
     number_button(number)
   }
@@ -420,6 +701,7 @@ shell {
   number_button(0, horizontal_span: 2)
   operation_button('.')
 }
+# ...
 ```
 
 Glimmer app on the desktop (using the [`glimmer-dsl-swt`](https://github.com/AndyObtiva/glimmer-dsl-swt) gem):
@@ -448,13 +730,13 @@ You should see "Apple Calculator Theme"
 
 [![Glimmer Calculator Opal Apple Calculator Theme](https://raw.githubusercontent.com/AndyObtiva/glimmer-cs-calculator/master/glimmer-cs-calculator-screenshot-opal-apple.png)](http://glimmer-cs-calculator-server.herokuapp.com/welcomes/apple)
 
-### Glimmer DSL for XML (& HTML)
+#### Glimmer DSL for XML (& HTML)
 
 [Glimmer DSL for XML](https://github.com/AndyObtiva/glimmer-dsl-xml) provides Ruby syntax for building XML (eXtensible Markup Language) documents.
 
 Within the context of desktop development, Glimmer DSL for XML is useful in providing XML data for the [SWT Browser widget](https://github.com/AndyObtiva/glimmer/tree/master#browser-widget).
 
-#### XML DSL
+##### XML DSL
 
 Simply start with `html` keyword and add HTML inside its block using Glimmer DSL syntax.
 Once done, you may call `to_s`, `to_xml`, or `to_html` to get the formatted HTML output.
@@ -486,13 +768,13 @@ Output:
 <html><head><meta name="viewport" content="width=device-width, initial-scale=2.0" /></head><body><h1>Hello, World!</h1></body></html>
 ```
 
-### Glimmer DSL for CSS
+#### Glimmer DSL for CSS
 
 [Glimmer DSL for CSS](https://github.com/AndyObtiva/glimmer-dsl-css) provides Ruby syntax for building CSS (Cascading Style Sheets).
 
 Within the context of [Glimmer](https://github.com/AndyObtiva/glimmer) app development, Glimmer DSL for CSS is useful in providing CSS for the [SWT Browser widget](https://github.com/AndyObtiva/glimmer/tree/master#browser-widget).
 
-#### CSS DSL
+##### CSS DSL
 
 Simply start with `css` keyword and add stylesheet rule sets inside its block using Glimmer DSL syntax.
 Once done, you may call `to_s` or `to_css` to get the formatted CSS output.
@@ -525,7 +807,7 @@ Output:
 body{font-size:1.1em;background:white}body > h1{background-color:red;font-size:2em}
 ```
 
-### Glimmer DSL for Tk (MRI Ruby Desktop Development GUI Library)
+#### Glimmer DSL for Tk (MRI Ruby Desktop Development GUI Library)
 
 [Tcl/Tk](https://www.tcl.tk/) has evolved into a practical desktop GUI toolkit due to gaining truely native looking widgets on Mac, Windows, and Linux in [Tk version 8.5](https://www.tcl.tk/software/tcltk/8.5.html#:~:text=Highlights%20of%20Tk%208.5&text=Font%20rendering%3A%20Now%20uses%20anti,and%20window%20layout%2C%20and%20more.).
 
@@ -544,9 +826,9 @@ The trade-off is that while [SWT](https://www.eclipse.org/swt/) provides a pleth
 
 To get started, visit the [Glimmer DSL for Tk project page](https://github.com/AndyObtiva/glimmer-dsl-tk#pre-requisites) for instructions on installing the [glimmer-dsl-tk gem](https://rubygems.org/gems/glimmer-dsl-tk).
 
-#### Glimmer DSL for Tk Samples
+##### Glimmer DSL for Tk Samples
 
-##### Hello, World!
+###### Hello, World!
 
 Glimmer code (from [samples/hello/hello_world.rb](https://github.com/AndyObtiva/glimmer-dsl-tk/blob/master/samples/hello/hello_world.rb)):
 
@@ -570,7 +852,7 @@ Glimmer app:
 
 ![glimmer dsl tk screenshot sample hello world](https://raw.githubusercontent.com/AndyObtiva/glimmer-dsl-tk/master/images/glimmer-dsl-tk-screenshot-sample-hello-world.png)
 
-##### Hello, Tab!
+###### Hello, Tab!
 
 Glimmer code (from [samples/hello/hello_tab.rb](https://github.com/AndyObtiva/glimmer-dsl-tk/blob/master/samples/hello/hello_tab.rb)):
 
@@ -607,7 +889,7 @@ Glimmer app:
 ![glimmer dsl tk screenshot sample hello tab English](https://raw.githubusercontent.com/AndyObtiva/glimmer-dsl-tk/master/images/glimmer-dsl-tk-screenshot-sample-hello-tab-english.png)
 ![glimmer dsl tk screenshot sample hello tab French](https://raw.githubusercontent.com/AndyObtiva/glimmer-dsl-tk/master/images/glimmer-dsl-tk-screenshot-sample-hello-tab-french.png)
 
-##### Hello, Combo!
+###### Hello, Combo!
 
 Glimmer code (from [samples/hello/hello_combo.rb](https://github.com/AndyObtiva/glimmer-dsl-tk/blob/master/samples/hello/hello_combo.rb)):
 
@@ -642,204 +924,11 @@ Glimmer app:
 ![glimmer dsl tk screenshot sample hello combo](https://raw.githubusercontent.com/AndyObtiva/glimmer-dsl-tk/master/images/glimmer-dsl-tk-screenshot-sample-hello-combo.png)
 ![glimmer dsl tk screenshot sample hello combo dropdown](https://raw.githubusercontent.com/AndyObtiva/glimmer-dsl-tk/master/images/glimmer-dsl-tk-screenshot-sample-hello-combo-dropdown.png)
 
-## DSL Engine
-
-Glimmer is fundamentally a DSL Engine that can support any number of DSLs like the official Glimmer DSLs (gems starting with the `glimmer-dsl-` prefix like `glimmer-dsl-swt`) or any DSLs for that matter.
-
-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)
-
-The Glimmer DSL Engine's architecture is based on the following Design Patterns and Data Structures:
-- **Interpreter Design Pattern**: to define interpretable expressions of DSL keywords
-- **Chain of Responsibility Design Pattern / Queue Data Structure**: to chain expression handlers in order of importance for processing DSL keywords
-- **Adapter Design Pattern**: to adapt expressions into handlers in a chain of responsibility
-- **Stack Data Structure**: to handle processing parent/child nesting of DSL keyword expressions in the correct order
-
-Glimmer's use of the **Interpreter Design Pattern** in processing DSLs is also known as the **Virtual Machine Architectural Style**. After all, DSL expressions are virtual machine opcodes that process nested keywords stored in a stack. I built Glimmer's original DSL back in 2007 without knowing the **Virtual Machine Architectural Style** (except perhaps as an esoteric technology powering Java), but stumbled upon it anyways through following the Gang of Four Design Patterns mentioned above, chiefly the **Interpreter Design Pattern**.
-
-Every keyword in a Glimmer DSL is represented by a DSL expression that is processed by an `Expression` subclass selected from a chain of expressions (interpreters) pre-configured in a DSL chain of responsibility via `Glimmer::DSL::Engine.add_dynamic_expressions(DSLNameModule, expression_names_array)`.
-
-Expressions are either:
-- **Static** (subclass of `StaticExpression`, which is a subclass of `Expression`): if they represent a single pre-identified keyword (e.g. `color` or `display`)
-- **Dynamic** (subclass of `Expression`): if they represent keywords calculated on the fly during processing (e.g. an SWT widget like `label` or a random XML element called `folder` representing `<folder></folder>`)
-
-Optionally, expressions can be parent expressions that contain other expressions, and must include the `ParentExpression` mixin module as such.
-
-Additionally, every expression that serves as a top-level entry point into the DSL must mixin `TopLevelExpression`
-
-Static expressions are optimized in performance since they pre-define methods on the `Glimmer` module matching the static keywords they represent (e.g. `color` causes creating a `Glimmer#color` method for processing `color` expressions) and completely bypass as a result the Glimmer DSL Engine Chain of Responsibility. That said, they must be avoided if the same keyword might occur multiple times, but with different requirements for arguments, block, and parenthood type.
-
-Every `Expression` sublcass must specify two methods at least:
-- `can_interpret?(parent, keyword, *args, &block)`: to quickly test if the keyword and arg/block/parent combination qualifies for interpretation by the current `Expression` or to otherwise delegate to the next expression in the chain of responsibility.
-- `interpret(parent, keyword, *args, &block)`: to go ahead and interpret a DSL expression that qualified for interpretation
-
-`StaticExpression` sublcasses may skip the `can_interpret?` method since they include a default implementation for it that matches the name of the keyword from the class name by convention. For example, a `color` keyword would have a `ColorExpression` class, so `color` is inferred automatically from class name and used in deciding whether the class can handle a `color` keyword or not.
-
-`ParentExpression` subclasses can optionally override this extra method, which is included by default and simply invokes the parent's passed block to process its children:
-- `add_content(parent, &block)`
-
-For example, some parent widgets use their block for other reasons or process their children at very specific times, so they may override that method and disable it, or otherwise call `super` and do additional work.
-
-Example of a dynamic expression:
-
-```ruby
-module Glimmer
-  module DSL
-    module SWT
-      class WidgetExpression < Expression
-        include ParentExpression
-
-        EXCLUDED_KEYWORDS = %w[shell display tab_item]
-
-        def can_interpret?(parent, keyword, *args, &block)
-          !EXCLUDED_KEYWORDS.include?(keyword) and
-            parent.respond_to?(:swt_widget) and
-            Glimmer::SWT::WidgetProxy.widget_exists?(keyword)
-        end
-
-        def interpret(parent, keyword, *args, &block)
-          Glimmer::SWT::WidgetProxy.create(keyword, parent, args)
-        end
-
-        def add_content(parent, &block)
-          super
-          parent.post_add_content
-        end
-
-      end
-    end
-  end
-end
-```
-
-Example of a static expression (does not need `can_interpret?`):
-
-```ruby
-module Glimmer
-  module DSL
-    module Opal
-      class ColorExpression < StaticExpression
-        include TopLevelExpression
-  
-        def interpret(parent, keyword, *args, &block)
-          Glimmer::SWT::ColorProxy.new(*args)
-        end
-      end
-    end
-  end
-end
-```
-
-DSL expressions go into the `glimmer/dsl/{dsl_name}` namespace directory.
-
-Also, every DSL requires a `glimmer/dsl/{dsl_name}/dsl.rb` file, which configures the DSL into Glimmer via a call to:
-```ruby
-Glimmer::DSL::Engine.add_dynamic_expressions(DSLNameModule, expression_names_array)
-```
-
-Expression names are underscored verions of `Expression` subclass names minus the `_expression` suffix.
-
-For example, here is an SWT DSL configuration:
-
-```ruby
-require 'glimmer/launcher'
-require Glimmer::Launcher.swt_jar_file
-require 'glimmer/dsl/engine'
-Dir[File.expand_path('../*_expression.rb', __FILE__)].each {|f| require f}
-
-module Glimmer
-  module DSL
-    module SWT
-      Engine.add_dynamic_expressions(
-        SWT,
-        %w[
-          layout
-          widget_listener
-          combo_selection_data_binding
-          checkbox_group_selection_data_binding
-          radio_group_selection_data_binding
-          list_selection_data_binding
-          tree_items_data_binding
-          table_items_data_binding
-          data_binding
-          cursor
-          font
-          image
-          property
-          block_property
-          widget
-          custom_widget
-        ]
-      )
-    end
-  end
-end
-```
-
-In summary, these are the files needed to author a Glimmer DSL:
-- `glimmer/dsl/[dsl_name]/dsl.rb`: requires and adds all dynamic expressions to [dsl_name] Glimmer DSL
-- `glimmer/dsl/[dsl_name]/[expresion_name]_expresion.rb`: needed for every [expresion_name] expression, whether dynamic or static
-
-### Multi-DSL Support
-
-The Glimmer [DSL Engine](#dsl-engine) allows mixing DSLs, which comes in handy when doing things like rendering a desktop GUI DSL `browser` widget additionally leveraging the HTML DSL and CSS DSL for its content.
-
-DSLs are activated by top-level keywords (expressions denoted as `TopLevelExpression`). For example, the `html` keyword activates the [Glimmer DSL for XML](https://github.com/AndyObtiva/glimmer-dsl-xml) and the `css` keyword activates the [Glimmer DSL for CSS](https://github.com/AndyObtiva/glimmer-dsl-css). Glimmer automatically recognizes top-level keywords in each DSL and activates the DSL accordingly. Once done processing a nested DSL top-level keyword, Glimmer switches back to the prior DSL automatically.
-
-By default, all loaded DSLs (required glimmer DSL gems) are enabled.
-
-For example, this shows "Hello, World!" inside a [Glimmer DSL for SWT](https://github.com/AndyObtiva/glimmer-dsl-swt) desktop app `browser` widget using `html` and `css` from [Glimmer DSL for XML](https://github.com/AndyObtiva/glimmer-dsl-xml) and [Glimmer DSL for CSS](https://github.com/AndyObtiva/glimmer-dsl-css):
-
-```ruby
-require 'glimmer-dsl-swt'
-require 'glimmer-dsl-xml'
-require 'glimmer-dsl-css'
-
-include Glimmer
-
-shell {
-  minimum_size 130, 130
-  @browser = browser {
-    text html {
-      head {
-        meta(name: "viewport", content: "width=device-width, initial-scale=2.0")
-        style {
-          css {
-            h1 {
-              background 'yellow'
-            }
-          }
-        }
-      }
-      body {
-        h1 { "Hello, World!" }
-      }
-    }
-  }
-}.open
-```
-
-**API methods to enable/disable DSLs:**
-
-`Glimmer::DSL::Engine.disable_dsl(dsl)`: disables a particular DSL
-
-Example: `Glimmer::DSL::Engine.disable_dsl(:swt)`
-
-`Glimmer::DSL::Engine.enable_dsl(dsl)`: enables a particular DSL
-
-Example: `Glimmer::DSL::Engine.disable_dsl(:swt)`
-
-`Glimmer::DSL::Engine.enabled_dsls=(dsls)`: enables only the specified DSLs, disabling all other loaded DSLs
-
-Example: `Glimmer::DSL::Engine.enabled_dsls = [:xml, :css]`
-
 ## Data-Binding Library
 
-Data-Binding enables mapping GUI properties (like text and color) to Model attributes (like name and age).
+Data-Binding enables mapping GUI properties (like text and color) to Model attributes (like name and age) for bidirectional or unidirectional synchronization and conversion as needed.
 
-Glimmer enhances observed models automatically (including array operations like `<<` and `reject!`) on first observation. As such, you get automatic observable support, including nested and computed observations. No need to change your model code to data-bind it to the view or add repetitive boilerplate modules. View data-binding is truly decoupled from model logic by being able to observe any model attribute (Ruby attribute reader/writer combo or Ruby attribute reader alone for read-only data-binding when needed)
+Glimmer enhances observed models automatically (including array operations like `<<`, `delete`, and `reject!`) on first observation. As such, you get automatic observable support, including nested and computed observations. No need to change your model code to data-bind it to the view or add repetitive boilerplate modules. View data-binding is truly decoupled from model logic by being able to observe any model attribute (Ruby attribute reader/writer combo or Ruby attribute reader alone for read-only data-binding when needed)
 
 This relies mainly on the Observer Design Pattern and the MVP (Model-View-Presenter) Architectural Pattern (a variation on MVC)
 
@@ -850,6 +939,8 @@ These are the main classes concerning data-binding:
 - `ObservableArray`: Mixin module for any observable array collection that automatically handles notifying observers upon performing array mutation operations (e.g. `push` or `delete`)
 - `ModelBinding`: a higher-level abstraction that relies on all the other observer/observable classes to support basic data-binding, nested data-binding, and computed data-binding
 
+You may learn more from [Data-Binding](https://github.com/AndyObtiva/glimmer-dsl-swt/blob/master/docs/reference/GLIMMER_GUI_DSL_SYNTAX.md#data-binding) and [Observer](https://github.com/AndyObtiva/glimmer-dsl-swt/blob/master/docs/reference/GLIMMER_GUI_DSL_SYNTAX.md#observer) usage in [Glimmer DSL for SWT](https://github.com/AndyObtiva/glimmer-dsl-swt)
+
 ## 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.