RubyGems - glimmer-dsl-swt - Versions diffs - 4.17.5.0 → 4.17.8.2 - Mend

glimmer-dsl-swt 4.17.5.0 → 4.17.8.2

Files changed (41) hide show

checksums.yaml +4 -4
data/CHANGELOG.md +30 -2
data/README.md +250 -83
data/VERSION +1 -1
data/glimmer-dsl-swt.gemspec +20 -5
data/lib/glimmer/data_binding/tree_items_binding.rb +20 -2
data/lib/glimmer/dsl/swt/checkbox_group_selection_data_binding_expression.rb +61 -0
data/lib/glimmer/dsl/swt/custom_widget_expression.rb +2 -0
data/lib/glimmer/dsl/swt/dialog_expression.rb +1 -0
data/lib/glimmer/dsl/swt/directory_dialog_expression.rb +48 -0
data/lib/glimmer/dsl/swt/dsl.rb +2 -0
data/lib/glimmer/dsl/swt/file_dialog_expression.rb +48 -0
data/lib/glimmer/dsl/swt/radio_group_selection_data_binding_expression.rb +61 -0
data/lib/glimmer/dsl/swt/shell_expression.rb +3 -3
data/lib/glimmer/dsl/swt/widget_expression.rb +8 -8
data/lib/glimmer/swt/custom/checkbox_group.rb +181 -0
data/lib/glimmer/swt/custom/code_text.rb +39 -31
data/lib/glimmer/swt/custom/radio_group.rb +176 -0
data/lib/glimmer/swt/directory_dialog_proxy.rb +65 -0
data/lib/glimmer/swt/expand_item_proxy.rb +0 -1
data/lib/glimmer/swt/file_dialog_proxy.rb +66 -0
data/lib/glimmer/swt/menu_proxy.rb +4 -4
data/lib/glimmer/swt/shell_proxy.rb +5 -5
data/lib/glimmer/swt/tab_item_proxy.rb +3 -3
data/lib/glimmer/swt/widget_proxy.rb +27 -27
data/lib/glimmer/ui/custom_shell.rb +3 -3
data/lib/glimmer/ui/custom_widget.rb +3 -0
data/samples/elaborate/meta_sample.rb +24 -19
data/samples/hello/hello_checkbox.rb +85 -0
data/samples/hello/hello_checkbox_group.rb +68 -0
data/samples/hello/hello_combo.rb +12 -12
data/samples/hello/hello_directory_dialog.rb +60 -0
data/samples/hello/hello_expand_bar.rb +3 -1
data/samples/hello/hello_file_dialog.rb +60 -0
data/samples/hello/hello_group.rb +104 -0
data/samples/hello/hello_list_multi_selection.rb +23 -23
data/samples/hello/hello_list_single_selection.rb +18 -17
data/samples/hello/hello_radio.rb +108 -0
data/samples/hello/hello_radio_group.rb +84 -0
data/samples/hello/hello_world.rb +3 -3
metadata +19 -4

checksums.yaml CHANGED

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: a2111fbe2df8040f64a319e5e62b15982cdc4749a6cd0c548b97f2b37f01b276
-  data.tar.gz: 283eb8a7a8faedde6ab6224ebe06fda3fca7cdff44ec99b32baca35da9df7d04
+  metadata.gz: 517e5bcedc06e71150e504d4c8ad484adb383e839df9b09e9683d9ebcce72ce8
+  data.tar.gz: b9792dd4d60cdb642b187848f9cc07d2d33c5bb1801bf2cb961a59f1247d9713
 SHA512:
-  metadata.gz: 2cb656a29e5d9da0759b295bc5dba9f1a174e8a83a1ffa2921c4b5efb6fd10542f0a46e475807cbd884c7f14270afa0983b5e49b392f97e9ddd41a6a4ecbbf30
-  data.tar.gz: 9283a302b3aaa99f5ec50f0d0996b951bb72ce0309ae9ca978429621d81f14c4005251286229d3555f31754c0e9a727db2f15f9245fab28f902ef1456e1fa07e
+  metadata.gz: 74eae56731cba0eba1092b9a926cd995cc23190b78126436d5dff8454dc0b0a75e5a70ecc4c5a864d3580bb8f2ad4d003a3ef18bba4d7bb5b0a4f4a44eb5afe3
+  data.tar.gz: 41b95e7e364eab995e026fec0c442162fefa138b504a48a95ba0e93f39e460b676e635a64228a8c51559ea4c0468afa09695fa1be63f375d6788c7914c6609fc

data/CHANGELOG.md CHANGED

@@ -1,5 +1,33 @@
 # Change Log
+### 4.17.8.1
+- Fixed an issue in Windows with code_text
+### 4.17.8.0
+- Officially Support SWT FileDialog with the `file_dialog` keyword (was unofficially supported before via standard SWT)
+- Officially Support SWT DirectoryDialog with the `directory_dialog` keyword (was unofficially supported before via standard SWT)
+- Hello, File Dialog! Sample
+- Hello, Directory Dialog! Sample
+- Prevent tree items data-binding from updating if no tree data change occurred
+- Performance optimization for `code_text` syntax highlighting through caching
+### 4.17.7.0
+- `checkbox_group` built-in custom widget
+- Hello, Checkbox Group! Sample
+- Refactor `radio_group` to render labels instead of relying on radio button text since they are better stylable
+- Refactor Glimmer Meta-Sample to use `radio_group` instead of `radio`
+- Fix issue with ExpandBar fill_layout with the extra element at the end (remove it)
+### 4.17.6.0
+- New `radio_group` built-in Glimmer custom widget
+- Hello, Radio! Sample
+- Hello, Radio Group! Sample
+- Hello, Checkbox! Sample
 ### 4.17.5.0
 - Support auto-scaling by aspect ratio of width and height (write specs)
@@ -123,7 +151,7 @@
 - Add User Profile sample from DZone article
 - Colored Ruby syntax highlighting for sample:code and sample:run tasks courtesy of tty-markdown
-- Support `check` as alias to `checkbox` DSL keyword for Button widget with :check style.
+- Support `check` as alias to `checkbox` DSL keyword for Button widget with :check style.
 - Validate scaffolded custom shell gem name to ensure it doesn't clash with a built in Ruby method
 - GLIMMER_LOGGER_ASYNC env var for disabling async logging when needed for immediate troubleshooting purposes
 - Fix issue with table equivalent sort edge case (that is two sorts that are equivalent causing an infinite loop of resorting since the table is not correctly identified as sorted already)
@@ -322,7 +350,7 @@
 ## 0.1.3
 - Added 'org.eclipse.swt.dnd' to glimmer auto-included Java packages
-- Updated Tic Tac Toe sample to use new `message_box` keyword
+- Updated Tic Tac Toe sample to use new `message_box` keyword
 - Add DragSource and DropTarget transfer expression that takes a symbol or symbol array representing one or more of the following: FileTransfer, HTMLTransfer, ImageTransfer, RTFTransfer, TextTransfer, URLTransfer
 - Set default style DND::DROP_COPY in DragSource and DropTarget widgets
 - Support Glimmer::SWT::DNDProxy for handling Drop & Drop styles

data/README.md CHANGED

@@ -1,4 +1,4 @@
-# [<img src="https://raw.githubusercontent.com/AndyObtiva/glimmer/master/images/glimmer-logo-hi-res.png" height=85 />](https://github.com/AndyObtiva/glimmer) Glimmer DSL for SWT 4.17.5.0
+# [<img src="https://raw.githubusercontent.com/AndyObtiva/glimmer/master/images/glimmer-logo-hi-res.png" height=85 />](https://github.com/AndyObtiva/glimmer) Glimmer DSL for SWT 4.17.8.2
 ## JRuby Desktop Development GUI Library
 [![Gem Version](https://badge.fury.io/rb/glimmer-dsl-swt.svg)](http://badge.fury.io/rb/glimmer-dsl-swt)
 [![Travis CI](https://travis-ci.com/AndyObtiva/glimmer-dsl-swt.svg?branch=master)](https://travis-ci.com/github/AndyObtiva/glimmer-dsl-swt)
@@ -14,7 +14,11 @@
 [Glimmer receives two updates per month](https://rubygems.org/gems/glimmer-dsl-swt/versions). You can trust [Glimmer](https://rubygems.org/gems/glimmer) with your Ruby desktop GUI development needs. Please make [Glimmer](https://rubygems.org/gems/glimmer) even better by providing feedback and [contributing](#contributing) when possible.
-[<img src="https://covers.oreillystatic.com/images/9780596519650/lrg.jpg" width=105 /><br />
+Gem version numbers are in sync with the SWT library versions. The first two digits represent the SWT version number. The last two digits represent the minor and patch versions of Glimmer DSL for SWT.
+[Glimmer DSL for SWT](https://rubygems.org/gems/glimmer-dsl-swt) versions 4.17.x.y come with [SWT 4.17](https://download.eclipse.org/eclipse/downloads/drops4/R-4.17-202009021800/), which was released on September 2, 2020.
+[<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:
@@ -343,6 +347,13 @@ Glimmer App:
       - [Hello, Sash Form!](#hello-sash-form)
       - [Hello, Styled Text!](#hello-styled-text)
       - [Hello, Expand Bar!](#hello-expand-bar)
+      - [Hello, Radio!](#hello-radio)
+      - [Hello, Radio Group!](#hello-radio-group)
+      - [Hello, Group!](#hello-group)
+      - [Hello, Checkbox!](#hello-checkbox)
+      - [Hello, Checkbox Group!](#hello-checkbox-group)
+      - [Hello, Directory Dialog!](#hello-directory-dialog)
+      - [Hello, File Dialog!](#hello-file-dialog)
     - [Elaborate Samples](#elaborate-samples)
       - [User Profile](#user-profile)
       - [Login](#login)
@@ -426,7 +437,7 @@ Otherwise, Option 2 ([Bundler](#option-2-bundler)) can be followed in rare cases
 Note: if you encounter any [issues](https://github.com/AndyObtiva/glimmer-dsl-swt/issues), please [report](https://github.com/AndyObtiva/glimmer-dsl-swt/issues) and then install a previous version instead from the list of [Glimmer Releases](https://rubygems.org/gems/glimmer-dsl-swt/versions).
-### Option 1: Direct Install
+### Option 1: Direct Install
 (Use for [Scaffolding](#scaffolding))
 Run this command to install directly:
@@ -436,12 +447,10 @@ jgem install glimmer-dsl-swt
 Or this command if you want a specific version:
 ```
-jgem install glimmer-dsl-swt -v 4.17.5.0
+jgem install glimmer-dsl-swt -v 4.17.8.2
 ```
-Note: Gem version numbers are in sync with the SWT library versions. The first two digits represent the SWT version number. The last two digits represent the minor and patch versions of Glimmer DSL for SWT.
-`jgem` is JRuby's version of `gem` command.
+`jgem` is JRuby's version of `gem` command.
 RVM allows running `gem install` directly as an alias.
 Otherwise, you may also run `jruby -S gem install ...`
@@ -451,7 +460,7 @@ Otherwise, if you are ready to build a Glimmer app, you can jump to the [Glimmer
 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
+### Option 2: Bundler
 (Use for Manual App Creation)
 Add the following to `Gemfile`:
@@ -478,7 +487,7 @@ You can bring up usage instructions by running the `glimmer` command without arg
 glimmer
 ```
-On Mac and Linux, it additionally brings up a TUI (Text-based User Interface) for interactive navigation and execution of Glimmer tasks (courtesy of [rake-tui](https://github.com/AndyObtiva/rake-tui)).
+On Mac and Linux, it additionally brings up a TUI (Text-based User Interface) for interactive navigation and execution of Glimmer tasks (courtesy of [rake-tui](https://github.com/AndyObtiva/rake-tui)).
 On Windows, it simply lists the available Glimmer tasks at the end (courtsey of [rake](https://github.com/ruby/rake)).
@@ -514,13 +523,13 @@ bin/glimmer samples
 Below are the full usage instructions that come up when running `glimmer` without args.
 ```
-Glimmer (Ruby Desktop Development GUI Library) - JRuby Gem: glimmer-dsl-swt v4.17.5.0
+Glimmer (Ruby Desktop Development GUI Library) - JRuby Gem: glimmer-dsl-swt v4.17.8.2
 Usage: glimmer [--bundler] [--pd] [--quiet] [--debug] [--log-level=VALUE] [[ENV_VAR=VALUE]...] [[-jruby-option]...] (application.rb or task[task_args]) [[application2.rb]...]
-Runs Glimmer applications and tasks.
+Runs Glimmer applications and tasks.
-When applications are specified, they are run using JRuby,
+When applications are specified, they are run using JRuby,
 automatically preloading the glimmer Ruby gem and SWT jar dependency.
 Optionally, extra Glimmer options, JRuby options, and/or environment variables may be passed in.
@@ -543,11 +552,11 @@ Select a Glimmer task to run: (Press ↑/↓ arrow to move, Enter to select and
   glimmer package[type]                                      # Package app for distribution (generating config, jar, and native files) (type is optional)
   glimmer package:clean                                      # Clean by removing "dist" and "packages" directories
   glimmer package:config                                     # Generate JAR config file
-  glimmer package:gemspec                                    # Generate gemspec
+  glimmer package:gemspec                                    # Generate gemspec
   glimmer package:jar                                        # Generate JAR file
   glimmer package:lock_jars                                  # Lock JARs
   glimmer package:native[type]                               # Generate Native files
-  glimmer run[app_path]                                      # Runs Glimmer app or custom shell gem in the current directory, unless app_path is specified, then runs it instead (app_path is optional)
+  glimmer run[app_path]                                      # Runs Glimmer app or custom shell gem in the current directory, unless app_path is specified, then runs it instead (app_path is optional)
   glimmer samples                                            # Brings up the Glimmer Meta-Sample app to allow browsing, running, and viewing code of Glimmer samples
   glimmer scaffold[app_name]                                 # Scaffold Glimmer application directory structure to build a new app
   glimmer scaffold:customshell[name,namespace]               # Scaffold Glimmer::UI::CustomShell subclass (full window view) under app/views (namespace is optional) [alt: scaffold:cs]
@@ -587,10 +596,10 @@ This brings up the [Glimmer Meta-Sample (The Sample of Samples)](#samples):
 Glimmer borrows from Rails the idea of Scaffolding, that is generating a structure for your app files that
 helps you get started just like true building scaffolding helps construction workers, civil engineers, and architects.
-Glimmer scaffolding goes beyond just scaffolding the app files that Rails does. It also packages it and launches it,
+Glimmer scaffolding goes beyond just scaffolding the app files that Rails does. It also packages it and launches it,
 getting you to a running and delivered state of an advanced "Hello, World!" Glimmer application right off the bat.
-This should greatly facilitate building a new Glimmer app by helping you be productive and focus on app details while
+This should greatly facilitate building a new Glimmer app by helping you be productive and focus on app details while
 letting Glimmer scaffolding take care of initial app file structure concerns, such as adding:
 - Main application class that includes Glimmer (`app/{app_name}.rb`)
 - Main application view that houses main window content, menu, about dialog, and preferences dialog
@@ -605,7 +614,7 @@ You need to have your Git `user.name` and `github.user` configured before scaffo
 #### App
-Before you start, make sure you are in a JRuby environment with Glimmer gem installed as per "Direct Install" pre-requisites.
+Before you start, make sure you are in a JRuby environment with Glimmer gem installed as per "Direct Install" pre-requisites.
 To scaffold a Glimmer app from scratch, run the following command:
@@ -699,7 +708,7 @@ The app even remembers your cookies if you log into the website, close the app,
 Note that on Linux, the default SWT browser, which runs on webkit, does not support HTML5 Video out of the box. If you need video support, open `Gemfile` after scaffolding and enable the line that has the `glimmer-cw-browser-chromium` gem then replace the `browser` in "app/views/snowboard_utah/app_view.rb" with `browser(:chromium)`
-Before you start, make sure you are in a JRuby environment with Glimmer gem installed as per "Direct Install" pre-requisites.
+Before you start, make sure you are in a JRuby environment with Glimmer gem installed as per "Direct Install" pre-requisites.
 To scaffold a Glimmer desktopify app from scratch, run the following command:
@@ -814,8 +823,8 @@ glimmer scaffold:cw[name]
 #### Custom Shell Gem
-Custom shell gems are self-contained Glimmer apps as well as reusable custom shells.
-They have everything scaffolded Glimmer apps come with in addition to gem content like a [Juwelier](https://rubygems.org/gems/juwelier) Rakefile that can build gemspec and release gems.
+Custom shell gems are self-contained Glimmer apps as well as reusable custom shells.
+They have everything scaffolded Glimmer apps come with in addition to gem content like a [Juwelier](https://rubygems.org/gems/juwelier) Rakefile that can build gemspec and release gems.
 Unlike scaffolded Glimmer apps, custom shell gem content lives under the `lib` directory (not `app`).
 They can be packaged as both a native executable (e.g. Mac DMG/PKG/APP) and a Ruby gem.
 Of course, you can just build a Ruby gem and disregard native executable packaging if you do not need it.
@@ -842,7 +851,7 @@ Since custom shell gems are both an app and a gem, they provide two ways to run:
 - Run the `glimmer` command and pass it the generated script under the `bin` directory that matches the gem name (e.g. run `glimmer bin/glimmer-cs-calculator`)
 - Run the executable shell script that ships with the gem directly (does not need the `glimmer` command). It intentionally has a shorter name for convenience since it is meant to be used on the command line (not in a package), so you can leave out the `glimmer-cs-` prefix (e.g. run `bin/calculator` directly). This is also used as the main way of running custom shell gems on Linux.
-Examples:
+Examples:
 - [glimmer-cs-gladiator](https://github.com/AndyObtiva/glimmer-cs-gladiator): Gladiator (Glimmer Editor)
 - [glimmer-cs-calculator](https://github.com/AndyObtiva/glimmer-cs-calculator): Glimmer Calculator
@@ -868,7 +877,7 @@ 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)
-Examples:
+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
@@ -903,11 +912,11 @@ Output:
   Glimmer Custom Shell Gems at rubygems.org:
-     Name               Gem            Version     Author                        Description
+     Name               Gem            Version     Author                        Description
-  Calculator   glimmer-cs-calculator   1.0.2     Andy Maleh   Calculator - Glimmer Custom Shell
-  Gladiator    glimmer-cs-gladiator    0.2.4     Andy Maleh   Gladiator (Glimmer Editor) - Glimmer Custom Shell
-  Timer        glimmer-cs-timer        1.0.0     Andy Maleh   Timer - Glimmer Custom Shell
+  Calculator   glimmer-cs-calculator   1.0.2     Andy Maleh   Calculator - Glimmer Custom Shell
+  Gladiator    glimmer-cs-gladiator    0.2.4     Andy Maleh   Gladiator (Glimmer Editor) - Glimmer Custom Shell
+  Timer        glimmer-cs-timer        1.0.0     Andy Maleh   Timer - Glimmer Custom Shell
 ```
@@ -939,9 +948,9 @@ Output:
   Glimmer Custom Widget Gems matching [video] at rubygems.org:
-  Name          Gem          Version     Author              Description
+  Name          Gem          Version     Author              Description
-  Video   glimmer-cw-video   1.0.0     Andy Maleh   Glimmer Custom Widget - Video
+  Video   glimmer-cw-video   1.0.0     Andy Maleh   Glimmer Custom Widget - Video
 ```
@@ -959,11 +968,11 @@ Output:
   Glimmer Custom Widget Gems at rubygems.org:
-         Name                      Gem                Version      Author                       Description
+         Name                      Gem                Version      Author                       Description
-  Browser (Chromium)   glimmer-cw-browser-chromium   1.0.0       Andy Maleh   Chromium Browser - Glimmer Custom Widget
-  Cdatetime (Nebula)   glimmer-cw-cdatetime-nebula   1.5.0.0.1   Andy Maleh   Nebula CDateTime Widget - Glimmer Custom Widget
-  Video                glimmer-cw-video              1.0.0       Andy Maleh   Glimmer Custom Widget - Video
+  Browser (Chromium)   glimmer-cw-browser-chromium   1.0.0       Andy Maleh   Chromium Browser - Glimmer Custom Widget
+  Cdatetime (Nebula)   glimmer-cw-cdatetime-nebula   1.5.0.0.1   Andy Maleh   Nebula CDateTime Widget - Glimmer Custom Widget
+  Video                glimmer-cw-video              1.0.0       Andy Maleh   Glimmer Custom Widget - Video
 ```
@@ -987,13 +996,13 @@ Output:
   Glimmer DSL Gems at rubygems.org:
-  Name         Gem          Version    Author          Description
+  Name         Gem          Version    Author          Description
-  Css    glimmer-dsl-css    1.1.0     AndyMaleh    Glimmer DSL for CSS
-  Opal   glimmer-dsl-opal   0.4.0     AndyMaleh    Glimmer DSL for Opal
-  Swt    glimmer-dsl-swt    4.17.5.0  AndyMaleh    Glimmer DSL for SWT
-  Tk     glimmer-dsl-tk     0.0.6     AndyMaleh    Glimmer DSL for Tk
-  Xml    glimmer-dsl-xml    1.1.0     AndyMaleh    Glimmer DSL for XML
+  Css    glimmer-dsl-css    1.1.0     AndyMaleh    Glimmer DSL for CSS
+  Opal   glimmer-dsl-opal   0.4.0     AndyMaleh    Glimmer DSL for Opal
+  Swt    glimmer-dsl-swt    4.17.8.2  AndyMaleh    Glimmer DSL for SWT
+  Tk     glimmer-dsl-tk     0.0.6     AndyMaleh    Glimmer DSL for Tk
+  Xml    glimmer-dsl-xml    1.1.0     AndyMaleh    Glimmer DSL for XML
 ```
 ### Packaging
@@ -1136,7 +1145,7 @@ Static keywords are pre-identified keywords in the Glimmer DSL, such as `shell`,
 Dynamic keywords are dynamically figured out from currently imported (aka required/loaded) SWT widgets and custom widgets. Examples are: `label`, `combo`, and `list` for SWT widgets and `c_date_time`, `video`, and `gantt_chart` for custom widgets.
-The only reason to distinguish between the two is to realize that importing new Glimmer [custom widgets](#custom-widgets) and Java SWT custom widget libraries automatically expands Glimmer's DSL vocabulary with new dynamic keywords.
+The only reason to distinguish between the two is to realize that importing new Glimmer [custom widgets](#custom-widgets) and Java SWT custom widget libraries automatically expands Glimmer's DSL vocabulary with new dynamic keywords.
 For example, if a project adds this custom Java SWT library from the [Nebula Project](https://www.eclipse.org/nebula/):
@@ -1388,10 +1397,10 @@ message_box {
 #### Display
-The SWT `Display` class is a singleton in Glimmer. It is used in SWT to represent your display device, allowing you to manage GUI globally
+The SWT `Display` class is a singleton in Glimmer. It is used in SWT to represent your display device, allowing you to manage GUI globally
 and access available monitors. Additionally, it is responsible for the SWT event loop, which runs on the first thread the Glimmer application starts on. In multi-threaded programming, `Display` provides the methods `async_exec` and `sync_exec` to enable enqueuing GUI changes asynchronously or synchronously from threads other than the main (first) thread since direct GUI changes are forbidden from other threads by design.
-`Display` is automatically instantiated upon first instantiation of a `shell` widget.
+`Display` is automatically instantiated upon first instantiation of a `shell` widget.
 Alternatively, for advanced use cases, a `Display` can be created explicitly with the Glimmer `display` keyword. When a `shell` is later declared, it
 automatically uses the `display` created earlier without having to explicitly hook it.
@@ -1407,7 +1416,7 @@ automatically uses the `display` created earlier without having to explicitly ho
 @shell = shell { # uses display created above
 }
 ```
-The benefit of instantiating an SWT Display explicitly is to set [Properties](#widget-properties) or [Observers](#observer).
+The benefit of instantiating an SWT Display explicitly is to set [Properties](#widget-properties) or [Observers](#observer).
 Although SWT Display is not technically a widget, it has similar APIs and DSL support.
 #### Multi-Threading
@@ -1629,8 +1638,8 @@ https://help.eclipse.org/2019-12/nftopic/org.eclipse.platform.doc.isv/reference/
 When building a widget-related SWT object manually (e.g. `GridData.new(...)`), you are expected to use `SWT::CONSTANT` directly or BIT-OR a few SWT constants together like `SWT::BORDER | SWT::V_SCROLL`.
-Glimmer facilitates that with `swt` keyword by allowing you to pass multiple styles as an argument array of symbols instead of dealing with BIT-OR.
-Example:
+Glimmer facilitates that with `swt` keyword by allowing you to pass multiple styles as an argument array of symbols instead of dealing with BIT-OR.
+Example:
 ```ruby
 style = swt(:border, :v_scroll)
@@ -1638,7 +1647,7 @@ style = swt(:border, :v_scroll)
 #### Negative SWT Style Bits
-In rare occasions, you might need to apply & with a negative (not) style bit to negate it from another style bit that includes it.
+In rare occasions, you might need to apply & with a negative (not) style bit to negate it from another style bit that includes it.
 Glimmer facilitates that by declaring the negative style bit via postfixing a symbol with `!`.
 Example:
@@ -1647,13 +1656,13 @@ Example:
 style = swt(:shell_trim, :max!) # creates a shell trim style without the maximize button (negated)
 ```
-#### Extra SWT Styles
+#### Extra SWT Styles
 ##### Non-resizable Window
 SWT Shell widget by default is resizable. To make it non-resizable, one must pass a complicated style bit concoction like `swt(:shell_trim, :resize!, :max!)`.
-Glimmer makes this easier by alternatively offering a `:no_resize` extra SWT style, added for convenience.
+Glimmer makes this easier by alternatively offering a `:no_resize` extra SWT style, added for convenience.
 This makes declaring a non-resizable window as easy as:
 ```ruby
@@ -1816,7 +1825,7 @@ Example:
 ```ruby
 shell {
-  minimum_size 128, 128
+  minimum_size 128, 128
   cursor :appstarting
 }
 ```
@@ -2205,7 +2214,7 @@ It assumes you have defined the table columns via `table_column` widget.
 Example:
 ```ruby
-shell {
+shell {
   @table = table {
     table_column {
       text "Name"
@@ -2223,13 +2232,13 @@ shell {
     selection bind(group, :selected_person)
     on_mouse_up { |event|
       @table.edit_table_item(event.table_item, event.column_index)
-    }
+    }
   }
 }
 ```
 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 `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.)
@@ -2246,16 +2255,16 @@ found_array = @table.search { |table_item| table_item.getData == company.owner }
 This finds a person. The array is a Java array. This enables easy passing of it to SWT `Table#setSelection` method, which expects a Java array of `TableItem` objects.
-To edit a table, you must invoke `TableProxy#edit_selected_table_item(column_index, before_write: nil, after_write: nil, after_cancel: nil)` or `TableProxy#edit_table_item(table_item, column_index, before_write: nil, after_write: nil, after_cancel: nil)`.
-This automatically leverages the SWT TableEditor custom class behind the scenes, displaying a text widget to the user to change the selected or
-passed table item text into something else.
+To edit a table, you must invoke `TableProxy#edit_selected_table_item(column_index, before_write: nil, after_write: nil, after_cancel: nil)` or `TableProxy#edit_table_item(table_item, column_index, before_write: nil, after_write: nil, after_cancel: nil)`.
+This automatically leverages the SWT TableEditor custom class behind the scenes, displaying a text widget to the user to change the selected or
+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.
+Glimmer automatically adds sorting support to the SWT `Table` widget.
-Check out the [Contact Manager](#contact-manager) sample for an example.
+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.
@@ -2263,7 +2272,7 @@ Glimmer automatic table sorting supports `String`, `Integer`, and `Float` column
 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_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.
@@ -2323,7 +2332,7 @@ This involves using the `bind` keyword mentioned above in addition to a special
 Example:
 ```ruby
-shell {
+shell {
   @tree = tree {
     items bind(company, :owner), tree_properties(children: :coworkers, text: :name)
     selection bind(company, :selected_coworker)
@@ -2332,7 +2341,7 @@ shell {
 ```
 The code above includes two data-bindings:
-- Tree `items`, which first bind to the root node (company.owner), and then dig down via `coworkers` `children` method, using the `name` `text` attribute for displaying each tree item.
+- Tree `items`, which first bind to the root node (company.owner), and then dig down via `coworkers` `children` method, using the `name` `text` attribute for displaying each tree item.
 - Tree `selection`, which binds the single tree item selected by the user to the attribute denoted by the `bind` keyword
 Additionally, Tree `items` data-binding automatically stores each node model unto the SWT TreeItem object via `setData` method. This enables things like searchability.
@@ -2386,7 +2395,7 @@ Let's revisit the Tic Tac Toe example shown near the beginning of the page:
 shell {
   text "Tic-Tac-Toe"
   minimum_size 150, 178
-  composite {
+  composite {
     grid_layout 3, true
     (1..3).each { |row|
       (1..3).each { |column|
@@ -2436,7 +2445,7 @@ shell {
       @button1.swt_widget.setVisible(false)
     }
     on_widget_selected {
-      @button1.swt_widget.setVisible(true)
+      @button1.swt_widget.setVisible(true)
     }
   }
 }.open
@@ -2458,7 +2467,7 @@ Example (you may copy/paste in [`girb`](#girb-glimmer-irb-command)):
 }
 @shell.on_shell_iconified {
   @shell.close
-}
+}
 @shell.open
 ```
@@ -2580,7 +2589,7 @@ Usage:
 ```ruby
 shell {
   red_label(:center) {
-    text 'Red Label'
+    text 'Red Label'
     foreground :green
   }
 }.open
@@ -2647,7 +2656,7 @@ Additionally, custom widgets can call the following class methods:
 - `::options(*option_names)`: declares a list of options by taking an option name array (symbols/strings). This generates option attribute accessors (e.g. `options :orientation, :bg_color` generates `#orientation`, `#orientation=(v)`, `#bg_color`, and `#bg_color=(v)` attribute accessors)
 - `::option(option_name, default: nil)`: declares a single option taking option name and default value as arguments (also generates attribute accessors just like `::options`)
-#### Content/Options Example
+#### Content/Options Example
 (you may copy/paste in [`girb`](#girb-glimmer-irb-command))
@@ -2779,7 +2788,7 @@ shell { |app_shell|
           app_shell.hide
           @wizard_steps[@current_step_number - 1].open
         end
-      }
+      }
     }
   }
   button {
@@ -3073,6 +3082,55 @@ shell(:no_resize) {
 Also, you may invoke `Display.setAppVersion('1.0.0')` if needed for OS app version identification reasons during development, replacing `'1.0.0'` with your application version.
+#### Checkbox Group Widget
+`checkbox_group` (or alias `check_group`) is a Glimmer built-in custom widget that displays a list of `checkbox` buttons (`button(:check)`) based on its `items` property.
+`checkbox_group` consists of a root `composite` (with `grid_layout 1, false` by default) that holds nested `checkbox` (`button(:check)`) widgets.
+The `selection` property determines which `checkbox` buttons are checked. It expects an `Array` of `String` objects
+The `selection_indices` property determines which `checkbox` button indices are checked. It expects an `Array` of index `Integer` objects that are zero-based.
+The `checkboxes` property returns the list of nested `checkbox` widgets.
+When data-binding `selection`, the model property should have a matching property with `_options` suffix (e.g. `activities_options` for `activities`) to provide an `Array` of `String` objects for `checkbox` buttons.
+You may see an example at the [Hello, Checkbox Group!](#hello-checkbox-group) sample.
+![Hello Checkbox Group](images/glimmer-hello-checkbox-group.png)
+#### Radio Group Widget
+`radio_group` is a Glimmer built-in custom widget that displays a list of `radio` buttons (`button(:radio)`) based on its `items` property, which expects an `Array` of `String` objects.
+`radio_group` consists of a root `composite` (with `grid_layout 1, false` by default) that holds nested `radio` widgets.
+The `selection` property determines which `radio` button is selected. It expects a `String`
+The `selection_index` property determines which `radio` button index is selected. It expects an index integer that is zero-based.
+The `radios` property returns the list of nested `radio` widgets.
+When data-binding `selection`, the model property should have a matching property with `_options` suffix (e.g. `country_options` for `country`) to provide text for `radio` buttons.
+This custom widget is used in the [Glimmer Meta-Sample (The Sample of Samples)](#samples):
+![Glimmer Meta-Sample](images/glimmer-meta-sample.png)
+Glimmer Meta-Sample Code Example:
+```ruby
+# ...
+radio_group { |radio_group_proxy|
+  row_layout(:vertical) {
+    fill true
+  }
+  selection bind(sample_directory, :selected_sample_name)
+  font height: 24
+}
+# ...
+```
+You may see another example at the [Hello, Radio Group!](#hello-radio-group) sample.
 #### Code Text Widget
 `code_text` is a Glimmer built-in custom widget that displays syntax highlighted Ruby code in a customized SWT [StyledText](https://help.eclipse.org/2020-09/topic/org.eclipse.platform.doc.isv/reference/api/org/eclipse/swt/custom/StyledText.html) widget.
@@ -3099,7 +3157,7 @@ To use, simply use `code_text` in place of `text` or `styled_text` widget. If yo
 [![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.
+Glimmer supports a [video custom widget](https://github.com/AndyObtiva/glimmer-cw-video) not in SWT.
 You may obtain via `glimmer-cw-video` gem.
@@ -3202,7 +3260,7 @@ Glimmer configuration may be done via the `Glimmer::Config` 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.
+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:
@@ -3244,13 +3302,13 @@ This is an array of these possible values: `:stdout` (default), `:stderr`, `:fil
 It defaults to `[:stdout, :syslog]`
-When `:file` is included, Glimmer creates a 'log' directory directly below the Glimmer app local directory.
+When `:file` is included, Glimmer creates a 'log' directory directly below the Glimmer app local directory.
 It may also be customized further via the `logging_device_file_options` option.
 This is useful on Windows as an alternative to `syslog`, which is not available on Windows by default.
 #### logging_device_file_options
-This is a hash of [`logging`](https://github.com/TwP/logging) gem options for the `:file` logging device.
+This is a hash of [`logging`](https://github.com/TwP/logging) gem options for the `:file` logging device.
 Default: `{size: 1_000_000, age: 'daily', roll_by: 'number'}`
@@ -3268,7 +3326,7 @@ That ensures asynchronous buffered logging that is flushed every 500 messages an
 This is a [`logging`](https://github.com/TwP/logging) gem layout that formats the logging output.
-Default:
+Default:
 ```
 Logging.layouts.pattern(
@@ -3328,8 +3386,8 @@ 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.
+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.
@@ -3643,6 +3701,114 @@ Hello, Expand Bar! Reading Expanded
 ![Hello Expand Bar Reading Expanded](images/glimmer-hello-expand-bar-reading-expanded.png)
+#### Hello, Radio!
+This sample demonstrates the use of a `radio` (aka `button(:radio)`) in Glimmer.
+Code:
+[samples/hello/hello_radio.rb](https://github.com/AndyObtiva/glimmer-dsl-swt/blob/master/samples/hello/hello_radio.rb)
+Hello, Radio!
+![Hello Radio](images/glimmer-hello-radio.png)
+#### Hello, Radio Group!
+This sample demonstrates the use of a `radio_group` in Glimmer, which provides terser syntax for representing multiple radio buttons by relying on data-binding to automatically spawn the `radio` widgets based on available options on the model.
+Code:
+[samples/hello/hello_radio_group.rb](https://github.com/AndyObtiva/glimmer-dsl-swt/blob/master/samples/hello/hello_radio_group.rb)
+Hello, Radio Group!
+![Hello Radio Group](images/glimmer-hello-radio-group.png)
+#### Hello, Checkbox!
+This sample demonstrates the use of a `checkbox` (aka `check` or `button(:check)`) in Glimmer.
+Code:
+[samples/hello/hello_checkbox.rb](https://github.com/AndyObtiva/glimmer-dsl-swt/blob/master/samples/hello/hello_checkbox.rb)
+#### Hello, Group!
+This sample demonstrates the use of a `group` in Glimmer (not to be confused with the logical radio group custom widget, this is just an alternative to `composite` that provides a border around content).
+Code:
+[samples/hello/hello_group.rb](https://github.com/AndyObtiva/glimmer-dsl-swt/blob/master/samples/hello/hello_group.rb)
+Hello, Group!
+![Hello Group](images/glimmer-hello-group.png)
+#### Hello, Checkbox!
+This sample demonstrates the use of a `checkbox` (aka `check` or `button(:check)`) in Glimmer.
+Code:
+[samples/hello/hello_checkbox.rb](https://github.com/AndyObtiva/glimmer-dsl-swt/blob/master/samples/hello/hello_checkbox.rb)
+Hello, Checkbox!
+![Hello Checkbox](images/glimmer-hello-checkbox.png)
+#### Hello, Checkbox Group!
+This sample demonstrates the use of a `checkbox_group` (aka `check_group`) in Glimmer, which provides terser syntax for representing multiple checkbox buttons (`button(:check)`) by relying on data-binding to automatically spawn the `checkbox` widgets (`button(:check)`) based on available options on the model.
+Code:
+[samples/hello/hello_checkbox_group.rb](https://github.com/AndyObtiva/glimmer-dsl-swt/blob/master/samples/hello/hello_checkbox_group.rb)
+Hello, Checkbox Group!
+![Hello Checkbox Group](images/glimmer-hello-checkbox-group.png)
+#### Hello, Directory Dialog!
+This sample demonstrates the use of a `directory_dialog` in Glimmer.
+Code:
+[samples/hello/hello_directory_dialog.rb](https://github.com/AndyObtiva/glimmer-dsl-swt/blob/master/samples/hello/hello_directory_dialog.rb)
+Hello, Directory Dialog!
+![Hello Directory Dialog](images/glimmer-hello-directory-dialog.png)
+Hello, Directory Dialog! Browse...
+![Hello Directory Dialog](images/glimmer-hello-directory-dialog-browse.png)
+Hello, Directory Dialog! Selected Directory
+![Hello Directory Dialog](images/glimmer-hello-directory-dialog-selected-directory.png)
+#### Hello, File Dialog!
+This sample demonstrates the use of a `file_dialog` in Glimmer.
+Code:
+[samples/hello/hello_file_dialog.rb](https://github.com/AndyObtiva/glimmer-dsl-swt/blob/master/samples/hello/hello_file_dialog.rb)
+Hello, File Dialog!
+![Hello File Dialog](images/glimmer-hello-file-dialog.png)
+Hello, File Dialog! Browse...
+![Hello File Dialog](images/glimmer-hello-file-dialog-browse.png)
+Hello, File Dialog! Selected File
+![Hello File Dialog](images/glimmer-hello-file-dialog-selected-file.png)
 ### Elaborate Samples
 For more elaborate samples, check the following:
@@ -3748,7 +3914,7 @@ Gladiator is a good demonstration of:
 The following production apps have been built with Glimmer.
-If you have a Glimmer app you would like referenced here, please mention in a Pull Request.
+If you have a Glimmer app you would like referenced here, please mention in a Pull Request.
 ### Math Bowling
@@ -3796,11 +3962,11 @@ The Glimmer packaging process done in the `glimmer package` command consists of
 1. Generate JAR file using [Warbler](https://github.com/jruby/warbler) (`glimmer package:jar`): Enables bundling a Glimmer app into a JAR file under the `./dist` directory
 1. Generate native executable using [javapackager](https://docs.oracle.com/javase/8/docs/technotes/tools/unix/javapackager.html) (`glimmer package:native`): Enables packaging a JAR file as a DMG/PKG/APP file on Mac, MSI/EXE/APP on Windows, and DEB/RPM/APP on Linux (Glimmer does not officially support Linux with the `glimmer package` command yet, but it generates the JAR file successfully, and you could use `javapackager` manually afterwards if needed).
-Those steps automatically ensure generating a JAR file under the `./dist` directory using [Warbler](https://github.com/jruby/warbler), which is then used to automatically generate a DMG/MSI file (and other executables) under the `./packages/bundles` directory using `javapackager`.
+Those steps automatically ensure generating a JAR file under the `./dist` directory using [Warbler](https://github.com/jruby/warbler), which is then used to automatically generate a DMG/MSI file (and other executables) under the `./packages/bundles` directory using `javapackager`.
 The JAR file name will match your application local directory name (e.g. `MathBowling.jar` for `~/code/MathBowling`)
 The DMG file name will match the humanized local directory name + dash + application version (e.g. `Math Bowling-1.0.dmg` for `~/code/MathBowling` with version 1.0 or unspecified)
-The `glimmer package` command will automatically set "mac.CFBundleIdentifier" to ="org.#{project_name}.application.#{project_name}".
+The `glimmer package` command will automatically set "mac.CFBundleIdentifier" to ="org.#{project_name}.application.#{project_name}".
 You may override by configuring as an extra argument for javapackger (e.g. Glimmer::RakeTask::Package.javapackager_extra_args = " -Bmac.CFBundleIdentifier=org.andymaleh.application.MathBowling")
 ### Packaging Defaults
@@ -3852,9 +4018,9 @@ require 'glimmer/rake_task'
 Glimmer::RakeTask::Package.javapackager_extra_args = '-BlicenseType="MIT" -Bmac.category="public.app-category.business" -Bmac.signing-key-developer-id-app="Andy Maleh"'
 ```
-Note that `mac.category` defaults to "public.app-category.business", but can be overridden with one of the category UTI values mentioned here:
+Note that `mac.category` defaults to "public.app-category.business", but can be overridden with one of the category UTI values mentioned here:
-https://developer.apple.com/library/archive/releasenotes/General/SubmittingToMacAppStore/index.html#//apple_ref/doc/uid/TP40010572-CH16-SW8
+https://developer.apple.com/library/archive/releasenotes/General/SubmittingToMacAppStore/index.html#//apple_ref/doc/uid/TP40010572-CH16-SW8
 Example (env var):
@@ -3870,7 +4036,7 @@ Pass `-v` to javapackager in `Glimmer::RakeTask::Package.javapackager_extra_args
 ### Windows Application Packaging
-Windows offers two options for setup packaging:
+Windows offers two options for setup packaging:
 - `msi` (recommended): simpler packaging option. Requires [WiX Toolset](https://wixtoolset.org/) and [.NET Framework](https://dotnet.microsoft.com/download/dotnet-framework). Simply run `glimmer package[msi]` (or `glimmer package:native[msi]` if it's not your first time) and it will give you more details on the pre-requisites you need to install (e.g. [WiX Toolset](https://wixtoolset.org/) and [.NET Framework 3.5 SP1](https://dotnet.microsoft.com/download/dotnet-framework/net35-sp1)).
 - `exe`: more advanced packaging option. Requires [Inno Setup](https://jrsoftware.org/isinfo.php). Simply run `glimmer package[exe]` (or `glimmer package:native[exe]` if it's not your first time) and it will tell you what you need to install.
@@ -3922,7 +4088,7 @@ Now, when you run `glimmer package`, it builds a self-signed DMG file. When you
 1. Specifying License File
-The javapackager documentation states that a license file may be specified with "-BlicenseFile" javapackager option. However, in order for that to work, one must specify as a source file via "-srcfiles" javapackager option.
+The javapackager documentation states that a license file may be specified with "-BlicenseFile" javapackager option. However, in order for that to work, one must specify as a source file via "-srcfiles" javapackager option.
 Keep that in mind if you are not going to rely on the default `LICENSE.txt` support.
 Example:
@@ -3935,7 +4101,7 @@ Glimmer::RakeTask::Package.javapackager_extra_args = '-srcfiles "ACME.txt" -Blic
 If you run `glimmer package` multiple times, sometimes it leaves a mounted DMG project in your finder. Unmount before you run the command again or it might fail with an error saying: "Error: Bundler "DMG Installer" (dmg) failed to produce a bundle."
-By the way, keep in mind that during normal operation, it does also indicate a false-negative while completing successfully similar to the following (please ignore):
+By the way, keep in mind that during normal operation, it does also indicate a false-negative while completing successfully similar to the following (please ignore):
 ```
 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
@@ -3955,13 +4121,14 @@ Here is a list of notable 3rd party gems used by Glimmer:
 - [puts_debuggerer](https://github.com/AndyObtiva/puts_debuggerer): helps in troubleshooting when adding `require 'pd'` and using the `pd` command instead of `puts` or `p` (also `#pd_inspect` or `#pdi` instead of `#inspect`)
 - [rake](https://github.com/ruby/rake): used to implement and execute `glimmer` commands
 - [rake-tui](https://github.com/AndyObtiva/rake-tui): Rake Text-based User Interface. Allows navigating rake tasks with arrow keys and filtering task list by typing to quickly find an run a rake task.
+- [rouge](https://github.com/rouge-ruby/rouge): Ruby syntax highlighter used in the `code_text` [Glimmer DSL for SWT custom widget](#custom-widgets) leveraged by the [Glimmer Meta-Sample](#samples)
 - [super_module](https://github.com/AndyObtiva/super_module): used to cleanly write the Glimmer::UI:CustomWidget and Glimmer::UI::CustomShell modules
 - [text-table](https://github.com/aptinio/text-table): renders textual data in a textual table for the command-line interface of Glimmer
 - [warbler](https://github.com/jruby/warbler): converts a Glimmer app into a Java JAR file during packaging
 ## Glimmer Process
-[Glimmer Process](https://github.com/AndyObtiva/glimmer/blob/master/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.
+[Glimmer Process](https://github.com/AndyObtiva/glimmer/blob/master/PROCESS.md) is the lightweight software development process used for building Glimmer libraries and Glimmer apps, which goes beyond Agile, rendering all Agile processes obsolete. [Glimmer Process](PROCESS.md) is simply made up of 7 guidelines to pick and choose as necessary until software development needs are satisfied.
 Learn more by reading the [GPG](https://github.com/AndyObtiva/glimmer/blob/master/PROCESS.md) (Glimmer Process Guidelines)
@@ -3984,7 +4151,7 @@ You may submit [issues](https://github.com/AndyObtiva/glimmer-dsl-swt/issues) on
 ### Chat
-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)
+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
@@ -4031,7 +4198,7 @@ If your company would like to invest fulltime in further development of the Glim
 [MIT](LICENSE.txt)
-Copyright (c) 2007-2020 - Andy Maleh.
+Copyright (c) 2007-2020 - Andy Maleh.
 --