glimmer 0.10.1 → 0.10.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 4e5e05e1e5ce6544e9c0286a46f5436c82ff92e8659044b31794d3f4d9db40f2
-  data.tar.gz: 3ad9c659f81fed05328533f1af05713939d44297693af78d78799006009cad71
+  metadata.gz: f5296edf57183b7bffa288342e5c3c4ab14713dbd70af643bf8117f608314d2a
+  data.tar.gz: 5a9285de28140f0f7a94ed80ec9c6c597ae163a5fdce4f4ad8a060f5ad341775
 SHA512:
-  metadata.gz: 674f6f7ea6cf2908261b83ce3580b770bb39ac47c1069c2b26651c897d109863516349d7b09d94199c928b2efceb19719d41123453caa7fde187127bb0c3b16a
-  data.tar.gz: c5d22e44fa047b35f5aadb232f446cc074873dbb4b8638b2f83038208ae0e32535e0668cd19419994d76d1aac95e7a917b711cc8853d589ac3757e9ca90e350c
+  metadata.gz: ef36cf024e59cc0111d8f3a283c6d89134eea01390574962ef0b36ef89c75d482d6912b83fd1bfc609f40f262f72156df9ab8d8481ac41118bb799b1a718e473
+  data.tar.gz: 65c0d12d30f2ea846766d98bb91aa0b3ae86eaac11697532d6b3ed55a139816d0be797a94584297c40c949f8cff436dfa15cbc0176cbb652207bab452c148071

data/README.md

@@ -1,14 +1,17 @@
-# <img src="https://raw.githubusercontent.com/AndyObtiva/glimmer/master/images/glimmer-logo-hi-res.png" height=85 style="position: relative; top: 20px;" /> Glimmer (Ruby Desktop Development GUI Library)
+# [<img src="https://raw.githubusercontent.com/AndyObtiva/glimmer/master/images/glimmer-logo-hi-res.png" height=85 style="position: relative; top: 20px;" />](https://rubygems.org/gems/glimmer) Glimmer (Ruby Desktop Development GUI Library)
 [![Gem Version](https://badge.fury.io/rb/glimmer.svg)](http://badge.fury.io/rb/glimmer)
 [![Travis CI](https://travis-ci.com/AndyObtiva/glimmer.svg?branch=master)](https://travis-ci.com/github/AndyObtiva/glimmer) 
 [![Coverage Status](https://coveralls.io/repos/github/AndyObtiva/glimmer/badge.svg?branch=master)](https://coveralls.io/github/AndyObtiva/glimmer?branch=master)
+[![Maintainability](https://api.codeclimate.com/v1/badges/38fbc278022862794414/maintainability)](https://codeclimate.com/github/AndyObtiva/glimmer/maintainability)
 [![Join the chat at https://gitter.im/AndyObtiva/glimmer](https://badges.gitter.im/AndyObtiva/glimmer.svg)](https://gitter.im/AndyObtiva/glimmer?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
 
 **[Contributors Wanted! (Submit a Glimmer App Sample to Get Started)](#contributing)**
 
 (The Original Glimmer Library Since 2007. Beware of Imitators!)
 
-[**Glimmer**](https://rubygems.org/gems/glimmer) is a native-GUI cross-platform desktop development library written in [JRuby](https://www.jruby.org/), a highly portable faster version of [Ruby](https://www.ruby-lang.org/en/). [**Glimmer**](https://rubygems.org/gems/glimmer)'s main innovation is a declarative [Ruby DSL](#glimmer-dsl-syntax) that enables productive and efficient authoring of desktop application user-interfaces while relying on the robust [Eclipse SWT library](https://www.eclipse.org/swt/). [**Glimmer**](https://rubygems.org/gems/glimmer) additionally innovates by having built-in [data-binding](#data-binding) support, which greatly facilitates synchronizing the GUI with domain models. This achieves true decoupling of object oriented components, enabling developers to solve business problems without worrying about GUI concerns or alternatively drive development GUI-first and then write clean business models test-first afterwards. To get started quickly, [Glimmer](https://rubygems.org/gems/glimmer) offers [scaffolding](#scaffolding) options for [Apps](#in-production), [Gems](#custom-shell-gem), and [Custom Widgets](#custom-widgets). Last but not least, [Glimmer](https://rubygems.org/gems/glimmer) includes native-executable [packaging](#packaging--distribution) support, sorely lacking in competing libraries, thus enabling 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). Given that [JRuby](https://www.jruby.org/) runs on the [JVM](https://java.com/en/download/faq/whatis_java.xml) (Java Virtual Machine), unlike competing libraries like TK, it does not require recompilation of [Ruby](https://www.ruby-lang.org/en/) to use native GUI libraries on every platform. [Glimmer](https://rubygems.org/gems/glimmer) runs native GUI out of the box on every platform thanks to the [JVM](https://java.com/en/download/faq/whatis_java.xml) and [Eclipse SWT library](https://www.eclipse.org/swt/).
+[**Glimmer**](https://rubygems.org/gems/glimmer) is a native-GUI cross-platform desktop development library written in [JRuby](https://www.jruby.org/), an OS-threaded faster version of [Ruby](https://www.ruby-lang.org/en/). [Glimmer](https://rubygems.org/gems/glimmer)'s main innovation is a declarative [Ruby DSL](#glimmer-dsl-syntax) that enables productive and efficient authoring of desktop application user-interfaces while relying on the robust [Eclipse SWT library](https://www.eclipse.org/swt/). [Glimmer](https://rubygems.org/gems/glimmer) additionally innovates by having built-in [data-binding](#data-binding) support, which greatly facilitates synchronizing the GUI with domain models, thus achieving true decoupling of object oriented components and enabling developers to solve business problems (test-first) without worrying about GUI concerns. To get started quickly, [Glimmer](https://rubygems.org/gems/glimmer) offers [scaffolding](#scaffolding) options for [Apps](#in-production), [Gems](#custom-shell-gem), and [Custom Widgets](#custom-widgets). [Glimmer](https://rubygems.org/gems/glimmer) also includes native-executable [packaging](#packaging--distribution) support, sorely lacking in other libraries, thus enabling the delivery of desktop apps written in [Ruby](https://www.ruby-lang.org/en/) as truly native DMG/PKG/APP files on the [Mac](https://www.apple.com/ca/macos) + [App Store](https://developer.apple.com/macos/distribution/) and MSI/EXE files on [Windows](https://www.microsoft.com/en-ca/windows). Unlike libraries like TK, [Glimmer](https://rubygems.org/gems/glimmer) does not require recompilation of [Ruby](https://www.ruby-lang.org/en/). [Glimmer](https://rubygems.org/gems/glimmer) runs native GUI out of the box on every platform thanks to the [JVM](https://java.com/en/download/faq/whatis_java.xml), [JRuby](https://www.jruby.org/), and the [Eclipse SWT library](https://www.eclipse.org/swt/).
+
+NOTE: Glimmer is in beta mode. Please help make better by [contributing](#contributing), adopting for small or low risk projects, and providing feedback. While a lot of hard work has gone into it, it is by no means polished, and definitely has bugs waiting to be reported. The more feedback and issues you report the better.
 
 [<img src="https://covers.oreillystatic.com/images/9780596519650/lrg.jpg" width=105 /><br /> 
 Featured in<br />JRuby Cookbook](http://shop.oreilly.com/product/9780596519650.do)
@@ -171,8 +174,6 @@ Glimmer App:
 
 ![Contact Manager](images/glimmer-contact-manager.png)
 
-NOTE: Glimmer is in beta mode. Please help make better by [contributing](#contributing), adopting for small or low risk projects, and providing feedback.
-
 ## Table of contents
 
 - [Glimmer (Ruby Desktop Development GUI Library)](#-glimmer-ruby-desktop-development-gui-library)
@@ -202,7 +203,7 @@ NOTE: Glimmer is in beta mode. Please help make better by [contributing](#contri
     - [Raw JRuby Command](#raw-jruby-command)
       - [Mac Support](#mac-support)
   - [Girb (Glimmer irb) Command](#girb-glimmer-irb-command)
-  - [Glimmer DSL Syntax](#glimmer-dsl-syntax)
+  - [Glimmer GUI DSL Syntax](#glimmer-gui-dsl-syntax)
     - [Widgets](#widgets)
       - [Display](#display)
       - [SWT Proxies](#swt-proxies)
@@ -272,6 +273,7 @@ NOTE: Glimmer is in beta mode. Please help make better by [contributing](#contri
   - [In Production](#in-production)
     - [Math Bowling](#math-bowling)
     - [Are We There Yet?](#are-we-there-yet)
+    - [Garderie Rainbow Daily Agenda](#garderie-rainbow-daily-agenda)
   - [Packaging & Distribution](#packaging--distribution)
     - [Packaging Defaults](#packaging-defaults)
     - [Packaging Configuration](#packaging-configuration)
@@ -279,6 +281,7 @@ NOTE: Glimmer is in beta mode. Please help make better by [contributing](#contri
     - [Mac Application Distribution](#mac-application-distribution)
     - [Self Signed Certificate](#self-signed-certificate)
     - [Gotchas](#gotchas)
+  - [App Updates](#app-updates)    
   - [Resources](#resources)
   - [Help](#help)
     - [Issues](#issues)
@@ -313,18 +316,17 @@ https://www.eclipse.org/swt/faq.php
 
 ## Pre-requisites
 
-- SWT 4.15 (comes included in Glimmer gem)
-- JRuby 9.2.12.0 (supporting Ruby 2.5.x syntax) (find at [https://www.jruby.org/download](https://www.jruby.org/download))
-- JDK 8 (find at [https://www.oracle.com/java/technologies/javase-downloads.html](https://www.oracle.com/java/technologies/javase-downloads.html))
-- (Optional) RVM is needed for [Scaffolding](#scaffolding) only (find at [https://rvm.io/](https://rvm.io/))
+- SWT 4.16 (comes included in Glimmer gem)
+- JRuby 9.2.13.0 (supporting Ruby 2.5.x syntax) (get via [RVM](http://rvm.io) on Mac and Linux or find at [https://www.jruby.org/download](https://www.jruby.org/download) for Windows)
+- JDK 8 (find at https://www.oracle.com/java/technologies/javase/javase-jdk8-downloads.html)
 
-On **Mac** and **Linux**, an easy way to obtain JRuby is through [RVM](http://rvm.io) by running:
+To obtain JRuby through [RVM](http://rvm.io), you may run:
 
 ```bash
-rvm install jruby-9.2.12.0
+rvm install jruby-9.2.13.0
 ```
 
-Glimmer might still work on lower versions of Java, JRuby and SWT, but there are no guarantees, so it is best to stick to the pre-requisites outlined above.
+Glimmer might still work on other versions of Java, JRuby and SWT, but there are no guarantees, so it is best to stick to the pre-requisites outlined above.
 
 ## Setup
 
@@ -332,16 +334,16 @@ Please follow these instructions to make the `glimmer` command available on your
 
 If you intend to learn the basics of Glimmer but are not ready to build a Glimmer app yet, pick Option 1 ([Direct Install](#option-1-direct-install)).
 
-If you intend to build a Glimmer app from scratch on the Mac, pick Option 1 ([Direct Install](#option-1-direct-install)) to leverage [Glimmer Scaffolding](#scaffolding) (only available on the Mac).
+If you intend to build a Glimmer app from scratch with [scaffolding](#scaffolding), pick Option 1 ([Direct Install](#option-1-direct-install)) as well.
 
-Otherwise, Option 2 ([Bundler](#option-2-bundler)) is recommended for building Glimmer apps on other platforms (Windows and Linux).
+Otherwise, Option 2 ([Bundler](#option-2-bundler)) can be followed in rare cases where you want to build an app without [scaffolding](#scaffolding).
 
 ### Option 1: Direct Install 
-(Use for [Scaffolding](#scaffolding) on the Mac)
+(Use for [Scaffolding](#scaffolding))
 
 Run this command to install directly:
 ```
-jgem install glimmer-dsl-swt -v 0.4.1
+jgem install glimmer-dsl-swt -v 0.6.1
 ```
 
 `jgem` is JRuby's version of `gem` command. 
@@ -359,7 +361,7 @@ Note: if you're using activerecord or activesupport, keep in mind that Glimmer u
 
 Add the following to `Gemfile`:
 ```
-gem 'glimmer-dsl-swt', '~> 0.4.1'
+gem 'glimmer-dsl-swt', '~> 0.6.1'
 ```
 
 And, then run:
@@ -375,7 +377,7 @@ You may learn more about other Glimmer related gems ([`glimmer-dsl-opal`](https:
 
 The `glimmer` command allows you to run, scaffold, package, and list Glimmer applications/gems.
 
-If you are new to Glimmer, you may read the Basic Usage section and skip the rest until you have gone through [Girb (Glimmer irb) Command](#girb-glimmer-irb-command), [Glimmer DSL Syntax](#glimmer-dsl-syntax), and [Samples](#samples).
+If you are new to Glimmer, you may read the Basic Usage section and skip the rest until you have gone through [Girb (Glimmer irb) Command](#girb-glimmer-irb-command), [Glimmer GUI DSL Syntax](#glimmer-gui-dsl-syntax), and [Samples](#samples).
 
 ### Basic Usage
 
@@ -413,19 +415,20 @@ Either a single task or one or more applications may be specified.
 When a task is specified, it runs via rake. Some tasks take arguments in square brackets.
 
 Available tasks are below (you may also lookup by adding `require 'glimmer/rake_task'` in Rakefile and running rake -T):
-glimmer list:custom_shell_gems[query]                             # List Glimmer custom shell gems available at rubygems.org (query is optional)
-glimmer list:custom_widget_gems[query]                            # List Glimmer custom widget gems available at rubygems.org (query is optional)
-glimmer list:dsl_gems[query]                                      # List Glimmer DSL gems available at rubygems.org (query is optional)
-glimmer package                                                   # Package app for distribution (generating config, jar, and native files)
-glimmer package:clean                                             # Clean by removing "dist" and "packages" directories
-glimmer package:config                                            # Generate JAR config file
-glimmer package:jar                                               # Generate JAR file
-glimmer package:native                                            # Generate Native files (DMG/PKG/APP on the Mac)
-glimmer scaffold[app_name]                                        # Scaffold a Glimmer application directory structure to begin building a new app
-glimmer scaffold:custom_shell[custom_shell_name,namespace]        # Scaffold a Glimmer::UI::CustomShell subclass (represents a full window view) under app/views (namespace is optional)
-glimmer scaffold:custom_shell_gem[custom_shell_name,namespace]    # Scaffold a Glimmer::UI::CustomShell subclass (represents a full window view) under its own Ruby gem + app project (namespace is required)
-glimmer scaffold:custom_widget[custom_widget_name,namespace]      # Scaffold a Glimmer::UI::CustomWidget subclass (represents a part of a view) under app/views (namespace is optional)
-glimmer scaffold:custom_widget_gem[custom_widget_name,namespace]  # Scaffold a Glimmer::UI::CustomWidget subclass (represents a part of a view) under its own Ruby gem project (namespace is required)
+glimmer list:gems:customshell[query]               # List Glimmer custom shell gems available at rubygems.org (query is optional) [alt: list:gems:cs]
+glimmer list:gems:customwidget[query]              # List Glimmer custom widget gems available at rubygems.org (query is optional) [alt: list:gems:cw]
+glimmer list:gems:dsl[query]                       # List Glimmer DSL gems available at rubygems.org (query is optional)
+glimmer package[type]                              # Package app for distribution (generating config, jar, and native files) (type is optional)
+glimmer package:clean                              # Clean by removing "dist" and "packages" directories
+glimmer package:config                             # Generate JAR config file
+glimmer package:jar                                # Generate JAR file
+glimmer package:lock_jars                          # Lock JARs
+glimmer package:native[type]                       # Generate Native files (DMG/PKG/APP on the Mac, MSI/EXE/IMAGE on Windows, RPM/DEB on Linux) (type is optional)
+glimmer scaffold[app_name]                         # Scaffold Glimmer application directory structure to build a new app
+glimmer scaffold:customshell[name,namespace]       # Scaffold Glimmer::UI::CustomShell subclass (full window view) under app/views (namespace is optional) [alt: scaffold:cs]
+glimmer scaffold:customwidget[name,namespace]      # Scaffold Glimmer::UI::CustomWidget subclass (part of a view) under app/views (namespace is optional) [alt: scaffold:cw]
+glimmer scaffold:gem:customshell[name,namespace]   # Scaffold Glimmer::UI::CustomShell subclass (full window view) under its own Ruby gem + app project (namespace is required) [alt: scaffold:gem:cs]
+glimmer scaffold:gem:customwidget[name,namespace]  # Scaffold Glimmer::UI::CustomWidget subclass (part of a view) under its own Ruby gem project (namespace is required) [alt: scaffold:gem:cw]
 
 When applications are specified, they are run using JRuby, 
 automatically preloading the glimmer Ruby gem and SWT jar dependency.
@@ -467,7 +470,7 @@ getting you to a running and delivered state of an advanced "Hello, World!" Glim
 This should greatly facilitate building a new Glimmer app by helping you be productive and focus on app details while 
 letting Glimmer scaffolding take care of initial app file structure concerns, such as adding:
 - Main application class that includes Glimmer
-- Main application view that houses main window content, about dialog, and preferences dialog
+- Main application view that houses main window content, menu, about dialog, and preferences dialog
 - View and Model directories
 - Rakefile including Glimmer tasks
 - Version
@@ -475,7 +478,7 @@ letting Glimmer scaffolding take care of initial app file structure concerns, su
 - Icon
 - Bin file for starting application
 
-NOTE: Scaffolding requires RVM and currently supports Mac packaging only at the moment. 
+NOTE: Scaffolding supports Mac and Windows packaging at the moment. 
 
 #### App
 
@@ -511,20 +514,35 @@ Created CarMaker/bin/car_maker
 ...
 ```
 
-Eventually, it will launch an advanced "Hello, World!" app window having the title of your application and a Mac icon.
+Eventually, it will launch an advanced "Hello, World!" app window having the title of your application.
 
 ![Glimmer Scaffold App](images/glimmer-scaffolding-app.png)
 
-On the Mac, it also comes with a boilerplate Preferences dialog.
+It also comes with a boilerplate Preferences dialog.
 
 ![Glimmer Scaffold App Preferences](images/glimmer-scaffolding-app-preferences.png)
 
+Here is a Windows scaffolded app called Greeter:
+
+![Glimmer Scaffold App Windows](images/glimmer-scaffolding-app-windows.png)
+
+Here is the Windows version of the boilerplate Preferences dialog.
+
+![Glimmer Scaffold App Windows Preferences](images/glimmer-scaffolding-app-windows-preferences.png)
+
+
 #### Custom Shell
 
 To scaffold a Glimmer custom shell (full window view) for an existing Glimmer app, run the following command:
 
 ```
-glimmer scaffold:custom_shell[custom_shell_name]
+glimmer scaffold:customshell[name]
+```
+
+Or the following alternative abbreviation:
+
+```
+glimmer scaffold:cs[name]
 ```
 
 #### Custom Widget
@@ -532,13 +550,19 @@ glimmer scaffold:custom_shell[custom_shell_name]
 To scaffold a Glimmer custom widget (part of a view) for an existing Glimmer app, run the following command:
 
 ```
-glimmer scaffold:custom_widget[custom_widget_name]
+glimmer scaffold:customwidget[name]
+```
+
+Or the following alternative abbreviation:
+
+```
+glimmer scaffold:cw[name]
 ```
 
 #### Custom Shell Gem
 
 Custom shell gems are self-contained Glimmer apps as well as reusable custom shells. 
-They have everything scaffolded Glimmer apps come with in addition to gem content like a Jeweler Rakefile that can build gemspec and release gems. 
+They have everything scaffolded Glimmer apps come with in addition to gem content like a [jeweler](https://github.com/technicalpickles/jeweler) Rakefile that can build gemspec and release gems. 
 Unlike scaffolded Glimmer apps, custom shell gem content lives under the `lib` directory (not `app`).
 They can be packaged as both a native executable (e.g. Mac DMG/PKG/APP) and a Ruby gem.
 Of course, you can just build a Ruby gem and disregard native executable packaging if you do not need it.
@@ -546,7 +570,13 @@ Of course, you can just build a Ruby gem and disregard native executable packagi
 To scaffold a Glimmer custom shell gem (full window view distributed as a Ruby gem), run the following command:
 
 ```
-glimmer scaffold:custom_shell_gem[custom_shell_name, namespace]
+glimmer scaffold:gem:customshell[name,namespace]
+```
+
+Or the following alternative abbreviation:
+
+```
+glimmer scaffold:gem:cs[name,namespace]
 ```
 
 It is important to specify a namespace to avoid having your gem clash with existing gems.
@@ -565,9 +595,16 @@ Examples:
 To scaffold a Glimmer custom widget gem (part of a view distributed as a Ruby gem), run the following command:
 
 ```
-glimmer scaffold:custom_widget_gem[custom_widget_name, namespace]
+glimmer scaffold:gem:customwidget[name,namespace]
+```
+
+Or the following alternative abbreviation:
+
+```
+glimmer scaffold:gem:cw[name,namespace]
 ```
 
+
 It is important to specify a namespace to avoid having your gem clash with existing gems.
 
 The Ruby gem name will follow the convention "glimmer-cw-customwidgetname-namespace" (the 'cw' is for Custom Widget)
@@ -588,13 +625,19 @@ The `glimmer` command comes with tasks for listing Glimmer related gems to make
 The following command lists available Glimmer [Custom Shell Gems](#custom-shell-gem) (prefixed with "glimmer-cs-" by scaffolding convention) created by the the Glimmer community and published on [rubygems.org](http://www.rubygems.org):
 
 ```
-glimmer list:custom_shell_gems[query]                             # List Glimmer custom shell gems available at rubygems.org (query is optional)
+glimmer list:gems:customshell[query]
+```
+
+Or the following alternative abbreviation:
+
+```
+glimmer list:gems:cs[query]
 ```
 
 Example:
 
 ```
-glimmer list:custom_shell_gems
+glimmer list:gems:cs
 ```
 
 Output:
@@ -606,7 +649,7 @@ Output:
      Name               Gem            Version     Author                        Description                     
                                                                                                                  
   Calculator   glimmer-cs-calculator   1.0.1     Andy Maleh   Calculator - Glimmer Custom Shell                  
-  Gladiator    glimmer-cs-gladiator    0.2.0     Andy Maleh   Gladiator (Glimmer Editor) - Glimmer Custom Shell  
+  Gladiator    glimmer-cs-gladiator    0.2.3     Andy Maleh   Gladiator (Glimmer Editor) - Glimmer Custom Shell  
                                                                                                                  
 ```
 
@@ -615,7 +658,13 @@ Output:
 The following command lists available Glimmer [Custom Widget Gems](#custom-widget-gem) (prefixed with "glimmer-cw-" by scaffolding convention) created by the the Glimmer community and published on [rubygems.org](http://www.rubygems.org):
 
 ```
-glimmer list:custom_widget_gems[query]                            # List Glimmer custom widget gems available at rubygems.org (query is optional)
+glimmer list:gems:customwidget[query]
+```
+
+Or the following alternative abbreviation:
+
+```
+glimmer list:gems:cw[query]
 ```
 
 Example:
@@ -623,7 +672,7 @@ Example:
 Check if there is a custom video widget for Glimmer.
 
 ```
-glimmer list:custom_widget_gems[video]
+glimmer list:gems:cw[video]
 ```
 
 Output:
@@ -634,7 +683,7 @@ Output:
                                                                                    
   Name          Gem          Version     Author              Description           
                                                                                    
-  Video   glimmer-cw-video   0.1.1     Andy Maleh   Glimmer Custom Widget - Video  
+  Video   glimmer-cw-video   0.1.3     Andy Maleh   Glimmer Custom Widget - Video  
                                                                                    
 ```
 
@@ -643,13 +692,13 @@ Output:
 The following command lists available Glimmer [DSL Gems](#multi-dsl-support) (prefixed with "glimmer-dsl-" by convention) created by the the Glimmer community and published on [rubygems.org](http://www.rubygems.org):
 
 ```
-glimmer list:dsl_gems[query]                                      # List Glimmer DSL gems available at rubygems.org (query is optional)
+glimmer list:gems:dsl[query]
 ```
 
 Example:
 
 ```
-glimmer list:dsl_gems
+glimmer list:gems:dsl
 ```
 
 Output:
@@ -660,10 +709,10 @@ Output:
                                                                          
   Name         Gem          Version    Author          Description       
                                                                          
-  Css    glimmer-dsl-css    0.1.0     AndyMaleh   Glimmer DSL for CSS    
-  Opal   glimmer-dsl-opal   0.0.9     AndyMaleh   Glimmer DSL for Opal   
-  Swt    glimmer-dsl-swt    0.4.1     AndyMaleh   Glimmer DSL for SWT    
-  Xml    glimmer-dsl-xml    0.1.0     AndyMaleh   Glimmer DSL for XML    
+  Css    glimmer-dsl-css    0.2.0     AndyMaleh   Glimmer DSL for CSS    
+  Opal   glimmer-dsl-opal   0.1.0     AndyMaleh   Glimmer DSL for Opal   
+  Swt    glimmer-dsl-swt    0.6.1     AndyMaleh   Glimmer DSL for SWT    
+  Xml    glimmer-dsl-xml    0.2.0     AndyMaleh   Glimmer DSL for XML    
                                                                          
 ```
 
@@ -716,13 +765,24 @@ Watch out for hands-on examples in this README indicated by "you may copy/paste
 
 Keep in mind that all samples live under [https://github.com/AndyObtiva/glimmer-dsl-swt](https://github.com/AndyObtiva/glimmer-dsl-swt)
 
-## Glimmer DSL Syntax
+## Glimmer GUI DSL Syntax
 
-Glimmer DSL syntax consists of static keywords and dynamic keywords to build and bind user-interface objects.
+Glimmer is mainly a GUI DSL with a lightweight visual syntax that makes it easy to visualize the nesting of widgets in the GUI hierarchy tree.
 
-Static keywords are pre-identified keywords in the Glimmer DSL, such as `shell`, `message_box`, `async_exec`, and `bind`.
+The GUI DSL intentionally avoids overly verbose syntax, requiring as little declarative code as possible to describe what GUI to render, how to style it, and what properties to data-bind to the Models.
 
-Dynamic keywords are dynamically figured out from available SWT widgets, custom widgets, and properties. Examples are: `label`, `combo`, and `list`.
+As such, it breaks off from Ruby's convention of using `do end` for multi-line blocks, opting instead for the lightweight and visual `{ }` curly brace blocks everywhere inside the GUI DSL. More details about Glimmer's syntax conventions may be found in the [Glimmer Style Guide](#glimmer-style-guide)
+
+Glimmer DSL syntax consists mainly of:
+- keywords (e.g. `table` for a table widget)
+- style/args (e.g. :multi as in `table(:multi)` for a multi-line selection table widget)
+- content (e.g. `{ table_column { text 'Name'} }` as in `table(:multi) { table_column { text 'name'} }` for a multi-line selection table widget with a table column having header text property `'Name'` as content)
+
+Glimmer keywords may be static or dynamic.
+
+Static keywords are pre-identified keywords in the Glimmer DSL, such as `shell`, `display`, `message_box`, `async_exec`, `sync_exec`, and `bind`.
+
+Dynamic keywords are dynamically figured out from currently imported (aka required/loaded) SWT widgets, custom widgets, and widget properties. Examples are: `label`, `combo`, and `list` for widgets and `enabled`, `text`, and `selection` for properties.
 
 The only reason to distinguish between the two types of Glimmer DSL keywords is to realize that importing new Glimmer [custom widgets](#custom-widgets) and Java SWT custom widget libraries automatically expands Glimmer's DSL vocabulary via new dynamic keywords.
 
@@ -742,9 +802,9 @@ https://www.eclipse.org/swt/widgets/
 
 This screenshot taken from the link above should give a glimpse of how SWT widgets look and feel:
 
-![SWT Widgets](images/glimmer-swt-widgets.png)
+[![SWT Widgets](images/glimmer-swt-widgets.png)](https://www.eclipse.org/swt/widgets/)
 
-In Glimmer DSL, widgets are declared with lowercase underscored names mirroring their SWT names minus the package name:
+In Glimmer DSL, widgets are declared with lowercase underscored names mirroring their SWT names minus the package name. For example, here are some Glimmer widgets and their SWT counterparts:
 
 - `shell` instantiates `org.eclipse.swt.widgets.Shell`
 - `text` instantiates `org.eclipse.swt.widgets.Text`
@@ -760,8 +820,8 @@ In Glimmer DSL, widgets are declared with lowercase underscored names mirroring
 - `list` instantiates `org.eclipse.swt.widgets.List`
 
 Every **widget** is sufficiently declared by name, but may optionally be accompanied with:
-- SWT **style** ***argument*** wrapped by parenthesis according to [Glimmer Style Guide](#glimmer-style-guide) (see [next section](#widget-styles) for details).
-- Ruby block containing **properties** (widget attributes) and **content** (nested widgets)
+- SWT **style**/***arguments*** wrapped by parenthesis according to [Glimmer Style Guide](#glimmer-style-guide) (see [next section](#widget-styles) for details).
+- Ruby block containing **content**, which may be **properties** (e.g. `enabled false`) or nested **widgets** (e.g. `table_column` nested inside `table`)
 
 For example, if we were to revisit `samples/hello/hello_world.rb` above (you may copy/paste in [`girb`](#girb-glimmer-irb-command)):
 
@@ -843,6 +903,8 @@ shell {
 }.open
 ```
 
+If you are new to Glimmer, you have learned enough to start running some [samples](#samples). Go ahead and run all Glimmer [samples](#samples), and come back to read the rest in any order you like since this material is more organized like a reference.
+
 #### Display
 
 SWT Display is a singleton in Glimmer. It is used in SWT to represent your display device, allowing you to manage GUI globally 
@@ -930,6 +992,21 @@ include Glimmer
 @shell.open
 ```
 
+![Hello Message Box Dialog](images/glimmer-hello-message-box-dialog.png)
+
+It is also possible to use `message_box` even before instantiating the first `shell` ([Glimmer](https://rubygems.org/gems/glimmer) builds a throwaway `shell` parent automatically for it):
+
+Example (you may copy/paste in [`girb`](#girb-glimmer-irb-command)):
+
+```ruby
+include Glimmer
+
+message_box {
+  text 'Greeting'
+  message "Hello, World!"
+}.open
+```
+
 ##### `#swt_widget`
 
 Glimmer widget objects come with an instance method `#swt_widget` that returns the actual SWT `Widget` object wrapped by the Glimmer widget object. It is useful in cases you'd like to do some custom SWT programming outside of Glimmer.
@@ -949,6 +1026,24 @@ Shell widget proxy has extra methods specific to SWT Shell:
 - `#pack`: Packs contained widgets using SWT's `Shell#pack` method
 - `#pack_same_size`: Packs contained widgets without changing shell's size when widget sizes change
 
+##### Shell Icon
+
+To set the shell icon, simply set the `image` property under the `shell` widget. This shows up in the operating system toolbar and app-switcher (e.g. CMD+TAB) (and application window top-left corner in Windows)
+
+Example:
+
+```ruby
+shell {
+  # ...
+  image 'path/to/image.png'
+  # ...
+}
+```
+
+###### Shell Icon Tip for Packaging on Windows
+
+When setting shell icon for a [packaged](#packaging--distribution) app, which has a JAR file at its core, you can reference the `ico` file that ships with the app by going one level up (e.g. `'../AppName.ico'`)
+
 #### Dialog
 
 Dialog is a variation on Shell. It is basically a shell that is modal (blocks what's behind it) and belongs to another shell. It only has a close button.
@@ -1124,7 +1219,7 @@ text(:center, :border) { # Multiple SWT styles separated by comma
 Glimmer ships with SWT style **smart defaults** so you wouldn't have to set them yourself most of the time (albeit you can always override them):
 
 - `text(:border)`
-- `table(:border)`
+- `table(:border, :virtual, :full_selection)`
 - `tree(:border, :virtual, :v_scroll, :h_scroll)`
 - `spinner(:border)`
 - `list(:border, :v_scroll)`
@@ -1200,7 +1295,7 @@ button {
 
 In the above example, the `text` widget `enabled` property was data-bound to `#empty` method on `@tic_tac_toe_board.box(row, column)` (learn more about data-binding below)
 
-#### Colors
+#### Color
 
 Colors make up a subset of widget properties. SWT accepts color objects created with RGB (Red Green Blue) or RGBA (Red Green Blue Alpha). Glimmer supports constructing color objects using the `rgb` and `rgba` DSL keywords.
 
@@ -1249,7 +1344,7 @@ Example:
 color(:black).swt_color # returns SWT Color object
 ```
 
-#### Fonts
+#### Font
 
 Fonts are represented in Glimmer as a hash of name, height, and style keys.
 
@@ -1278,7 +1373,34 @@ label {
 # ...
 ```
 
-### Layouts
+You may simply use the standalone `font` keyword without nesting in a parent if there is a need to build a Font object to use in manual SWT programming outside of widget font property setting.
+
+Example:
+
+```ruby
+@font = font(name: 'Arial', height: 36, style: :normal)
+```
+
+### Cursor
+
+SWT widget `cursor` property represents the mouse cursor you see on the screen when you hover over that widget.
+
+The `Display` class provides a way to obtain standard system cursors matching of the SWT style constants starting with prefix `CURSOR_` (e.g. `SWT::CURSOR_HELP` shows a question mark mouse cursor)
+
+Glimmer provides an easier way to obtain and set `cursor` property on a widget by simply mentioning the SWT style constant as an abbreviated symbol excluding the "CURSOR_" suffix.
+
+Example:
+
+```ruby
+shell {
+  minimum_size 128, 128                        
+  cursor :appstarting
+}
+```
+
+This sets the shell `cursor` to that of `SWT::CURSOR_APPSTARTING`
+
+### Layout
 
 Glimmer lays widgets out visually using SWT layouts, which can only be set on composite widget and subclasses.
 
@@ -1840,7 +1962,8 @@ Let's revisit the Tic Tac Toe example shown near the beginning of the page:
 ```ruby
 shell {
   text "Tic-Tac-Toe"
-  composite {
+  minimum_size 150, 178
+  composite {  
     grid_layout 3, true
     (1..3).each { |row|
       (1..3).each { |column|
@@ -2542,11 +2665,9 @@ Glimmer configuration may be done via the `Glimmer::Config` module.
 
 ### logger
 
-Glimmer supports logging via a standard `STDOUT` Ruby `Logger` configured in the `Glimmer::Config.logger` config option.
+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.
-It may be replaced with a custom logger via `Glimmer::Config.logger = custom_logger`
-All logging is done lazily via blocks (e.g. `logger.debug {message}`) to avoid affecting app performance with logging when below the configured logging level threshold.
 
 Example:
 
@@ -2571,6 +2692,55 @@ D, [2017-07-21T19:23:12.878434 #35707] DEBUG -- : WidgetCommandHandler will hand
 D, [2017-07-21T19:23:12.878798 #35707] DEBUG -- : widget styles are: [:multi]
 ```
 
+The `logger` instance may be replaced with a custom logger via `Glimmer::Config.logger = custom_logger`
+
+To reset `logger` to the default instance, you may call `Glimmer::Config.reset_logger!`
+
+All logging is done lazily via blocks (e.g. `logger.debug {message}`) to avoid affecting app performance with logging when below the configured logging level threshold.
+
+[Glimmer DSL for SWT](https://github.com/AndyObtiva/glimmer-dsl-swt) enhances Glimmer default logging support via the Ruby [`logging`](https://github.com/TwP/logging) gem, enabling buffered asynchronous logging in a separate thread, thus completely unhindering normal desktop app performance.
+
+Other config options related to the [`logging`](https://github.com/TwP/logging) gem are mentioned below.
+
+#### logging_devices
+
+This is an array of these possible values: `:stdout` (default), `:stderr`, `:file`, `:syslog` (default), `:stringio`
+
+It defaults to `[:stdout, :syslog]`
+
+When `:file` is included, Glimmer creates a 'log' directory directly below the Glimmer app local directory. 
+It may also be customized further via the `logging_device_file_options` option.
+This is useful on Windows as an alternative to `syslog`, which is not available on Windows by default.
+
+#### logging_device_file_options
+
+This is a hash of [`logging`](https://github.com/TwP/logging) gem options for the `:file` logging device. 
+
+Default: `{size: 1_000_000, age: 'daily', roll_by: 'number'}`
+
+That ensures splitting log files at the 1MB size and daily, rolling them by unique number.
+
+#### logging_appender_options
+
+Appender options is a hash passed as options to every appender (logging device) used in the [`logging`](https://github.com/TwP/logging) gem.
+
+Default: `{async: true, auto_flushing: 500, write_size: 500, flush_period: 60, immediate_at: [:error, :fatal], layout: logging_layout}`
+
+That ensures asynchronous buffered logging that is flushed every 500 messages and 60 seconds, or immediately at error and fatal log levels
+
+#### logging_layout
+
+This is a [`logging`](https://github.com/TwP/logging) gem layout that formats the logging output.
+
+Default: 
+
+```
+Logging.layouts.pattern(
+  pattern: '[%d] %-5l %c: %m\n',
+  date_pattern: '%Y-%m-%d %H:%M:%S'
+)
+```
+
 ### import_swt_packages
 
 Glimmer automatically imports all SWT Java packages upon adding `include Glimmer`, `include Glimmer::UI::CustomWidget`, or `include Glimmer::UI::CustomShell` to a class or module. It relies on JRuby's `include_package` for lazy-importing upon first reference of a Java class.
@@ -2920,6 +3090,8 @@ This sample demonstrates a full MVC application, including GUI layout, text and
 
 Code:
 
+(Please note that on some Linux instances where the display x-axis is set to double-scale, you need to set the `shell` `minimum_size` to `300, 178` instead of `150, 178`)
+
 [samples/elaborate/tic_tac_toe.rb](https://github.com/AndyObtiva/glimmer-dsl-swt/blob/master/samples/elaborate/tic_tac_toe.rb)
 
 Run:
@@ -2995,6 +3167,8 @@ 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. 
+
 ### Math Bowling
 
 [<img alt="Math Bowling Logo" src="https://raw.githubusercontent.com/AndyObtiva/MathBowling/master/images/math-bowling-logo.png" width="40" />Math Bowling](https://github.com/AndyObtiva/MathBowling): an educational math game for elementary level kids
@@ -3003,20 +3177,30 @@ The following production apps have been built with Glimmer.
 
 [<img alt="Are We There Yet Logo" src="https://raw.githubusercontent.com/AndyObtiva/are-we-there-yet/master/are-we-there-yet-logo.svg" width="40" />Are We There Yet?](https://github.com/AndyObtiva/are-we-there-yet): A tool that helps you learn when your small projects will finish
 
-If you have a Glimmer app you would like referenced here, please mention in a Pull Request. 
+### Garderie Rainbow Daily Agenda
+
+[<img alt="Garderie Rainbow Daily Agenda Logo" src="https://github.com/AndyObtiva/garderie_rainbow_daily_agenda/raw/master/images/garderie_rainbow_daily_agenda_logo.png" width="40" />Garderie Rainbow Daily Agenda](https://github.com/AndyObtiva/garderie_rainbow_daily_agenda): A child nursery daily agenda reporting desktop app
 
 ## Packaging & Distribution
 
 Glimmer apps may be packaged and distributed on the Mac, Windows, and Linux via these tools:
 - Warbler (https://github.com/jruby/warbler): Enables bundling a Glimmer app into a JAR file
-- javapackager (https://docs.oracle.com/javase/8/docs/technotes/tools/unix/javapackager.html): Enables packaging a JAR file as a DMG file on Mac, EXE on Windows, and multiple Linux supported formats on Linux.
+- javapackager (https://docs.oracle.com/javase/8/docs/technotes/tools/unix/javapackager.html): Enables packaging a JAR file as a DMG/PKG/APP file on Mac, MSI/EXE on Windows, and DEB/RPM on Linux.
 
-Glimmer simplifies the process of Mac packaging via the `glimmer package` command. It works out of the box for any application generated by [Glimmer Scaffolding](#scaffolding):
+Glimmer simplifies the process of Mac and Windows packaging via the `glimmer package` command:
 
 ```
 glimmer package
 ```
 
+It works out of the box for any application generated by [Glimmer Scaffolding](#scaffolding).
+
+Otherwise, if you are using Glimmer manually, to make the `glimmer package` command available, you must add the following line to your application `Rakefile`:
+
+```ruby
+require 'glimmer/rake_task'
+```
+
 This will automatically generate a JAR file under `./dist` directory using Warbler, which is then used to automatically generate a DMG file (and pkg/app) under `./packages/bundles` using `javapackager`. 
 JAR file name will match your application local directory name (e.g. `MathBowling.jar` for `~/code/MathBowling`)
 DMG file name will match the humanized local directory name + dash + application version (e.g. `Math Bowling-1.0.dmg` for `~/code/MathBowling` with version 1.0 or unspecified)
@@ -3024,6 +3208,14 @@ DMG file name will match the humanized local directory name + dash + application
 The `glimmer package` command will automatically set "mac.CFBundleIdentifier" to ="org.#{project_name}.application.#{project_name}". 
 You may override by configuring as an extra argument for javapackger (e.g. Glimmer::Package.javapackager_extra_args = " -Bmac.CFBundleIdentifier=org.andymaleh.application.MathBowling")
 
+You may choose to generate a specific type of packaging by passing the `[type]` option:
+
+```
+glimmer package[msi]
+```
+
+That generates an MSI file on Windows (could specify exe or image as alternatives on Windows).
+
 ### Packaging Defaults
 
 Glimmer employs smart defaults in packaging.
@@ -3084,6 +3276,14 @@ JAVAPACKAGER_EXTRA_ARGS='-Bmac.CFBundleName="Math Bowling Game"' glimmer package
 
 That overrides the default application display name.
 
+### Windows Application Packaging
+
+Windows offers two options for setup packaging: 
+- `msi` (recommended): simpler packaging option. Requires [WiX Toolset](https://wixtoolset.org/) and [.NET Framework](https://dotnet.microsoft.com/download/dotnet-framework). Simply run `glimmer package[msi]` (or `glimmer package:native[msi]` if it's not your first time) and it will tell you what you need to install including which version of .NET Framework it needs.
+- `exe`: more advanced packaging option. Requires [Inno Setup](https://jrsoftware.org/isinfo.php). Simply run `glimmer package[exe]` (or `glimmer package:native[exe]` if it's not your first time) and it will tell you what you need to install.
+
+If you just want to test out packaging into a native Windows app that is not packaged for Windows setup, just pass `image` to generate a native Windows app only.
+
 ### Mac Application Distribution
 
 Recent macOS versions (starting with Catalina) have very stringent security requirements requiring all applications to be signed before running (unless the user goes to System Preferences -> Privacy -> General tab and clicks "Open Anyway" after failing to open application the first time they run it). So, to release a desktop application on the Mac, it is recommended to enroll in the [Apple Developer Program](https://developer.apple.com/programs/) to distribute on the [Mac App Store](https://developer.apple.com/distribute/) or otherwise request [app notarization from Apple](https://developer.apple.com/documentation/xcode/notarizing_macos_software_before_distribution) to distribute independently.
@@ -3149,6 +3349,10 @@ By the way, keep in mind that during normal operation, it does also indicate a f
 Exec failed with code 2 command [[/usr/bin/SetFile, -c, icnC, /var/folders/4_/g1sw__tx6mjdgyh3mky7vydc0000gp/T/fxbundler4076750801763032201/images/MathBowling/.VolumeIcon.icns] in unspecified directory
 ```
 
+## App Updates
+
+Glimmer already supports automatic (and manual) app updates via the Mac App Store for Mac apps. Simply run the `glimmer package` command with the Mac App Store keys configured as per [Mac Application Distribution](mac-application-distribution) instructions and you get automatic (and manual) app update support courtesy of the Mac App Store.
+
 ## Resources
 
 * [Code Master Blog](http://andymaleh.blogspot.com/search/label/Glimmer)

data/VERSION

@@ -1 +1 @@
-0.10.1
+0.10.2

data/lib/glimmer.rb

@@ -4,6 +4,7 @@
 # UI with domain models.
 require 'logger'
 require 'set'
+require 'array_include_methods'
 
 $LOAD_PATH.unshift(File.expand_path('..', __FILE__))
 

data/lib/glimmer/config.rb

@@ -15,9 +15,7 @@ module Glimmer
       end
       
       def reset_excluded_keyword_checkers!
-        @excluded_keyword_checkers = [
-          lambda { |method_symbol, *args| method_symbol.to_s.match(REGEX_METHODS_EXCLUDED) }
-        ]
+        @excluded_keyword_checkers = [ lambda { |method_symbol, *args| method_symbol.to_s.match(REGEX_METHODS_EXCLUDED) } ]
       end
       
       def loop_max_count
@@ -25,7 +23,7 @@ module Glimmer
       end
       
       # Returns Glimmer logger (standard Ruby logger)
-      def logger
+      def logger      
         reset_logger! unless defined? @@logger
         @@logger
       end
@@ -36,13 +34,9 @@ module Glimmer
   
       def reset_logger!
         self.logger = Logger.new(STDOUT).tap do |logger| 
-          logger.level = Logger::ERROR
+          logger.level = ENV['GLIMMER_LOGGER_LEVEL'] ? ENV['GLIMMER_LOGGER_LEVEL'].downcase : Logger::ERROR
         end
       end
     end
   end
 end
-
-if ENV['GLIMMER_LOGGER_LEVEL']
-  Glimmer::Config.logger.level = ENV['GLIMMER_LOGGER_LEVEL'].downcase
-end

data/lib/glimmer/data_binding/observable_array.rb

@@ -1,77 +1,280 @@
 require 'set'
+require 'array_include_methods'
 
 require 'glimmer/data_binding/observable'
 
+using ArrayIncludeMethods
+
 module Glimmer
   module DataBinding
     # TODO prefix utility methods with double-underscore
     module ObservableArray
       include Observable
 
-      def add_observer(observer, element_properties=nil)
-        return observer if has_observer?(observer) && element_properties.nil?
+      def add_observer(observer, *element_properties)
+        element_properties = element_properties.flatten.compact.uniq
+        return observer if has_observer?(observer) && has_observer_element_properties?(observer, element_properties)
         property_observer_list << observer
-        [element_properties].flatten.compact.each do |property|
-          each do |element|
-            observer.observe(element, property)
-          end
-        end
+        observer_element_properties[observer] = element_properties_for(observer) + Set.new(element_properties)
+        each { |element| add_element_observer(element, observer) }
         observer
       end
+      
+      def add_element_observers(element)
+        property_observer_list.each do |observer|
+          add_element_observer(element, observer)
+        end
+      end
 
-      def remove_observer(observer, element_properties=nil)
-        property_observer_list.delete(observer)
-        [element_properties].flatten.compact.each do |property|
+      def add_element_observer(element, observer)
+        element_properties_for(observer).each do |property|
+          observer.observe(element, property)
+        end      
+      end
+
+      def remove_observer(observer, *element_properties)
+        element_properties = element_properties.flatten.compact.uniq
+        if !element_properties.empty?
+          old_element_properties = element_properties_for(observer)
+          observer_element_properties[observer] = element_properties_for(observer) - Set.new(element_properties)
           each do |element|
-            observer.unobserve(element, property)
+            element_properties.each do |property|
+              observer.unobserve(element, property)
+            end
           end
         end
+        if element_properties_for(observer).empty?
+          property_observer_list.delete(observer)
+          observer_element_properties.delete(observer)
+          each { |element| remove_element_observer(element, observer) }
+        end        
         observer
       end
 
+      def remove_element_observers(element)
+        property_observer_list.each do |observer|
+          remove_element_observer(element, observer)
+        end      
+      end
+
+      def remove_element_observer(element, observer)
+        element_properties_for(observer).each do |property|
+          observer.unobserve(element, property)
+        end      
+      end
+
       def has_observer?(observer)
         property_observer_list.include?(observer)
       end
+      
+      def has_observer_element_properties?(observer, element_properties)
+        element_properties_for(observer).to_a.include_all?(element_properties)
+      end
 
       def property_observer_list
         @property_observer_list ||= Set.new
       end
 
+      def observer_element_properties
+        @observer_element_properties ||= {}
+      end
+
+      def element_properties_for(observer)
+        observer_element_properties[observer] ||= Set.new
+      end
+
       def notify_observers
         property_observer_list.to_a.each(&:call)
       end
       
       def <<(element)
-        super(element)
-        notify_observers
+        super(element).tap do
+          add_element_observers(element)        
+          notify_observers
+        end
       end
+      alias push <<
       
       def []=(index, value)
         old_value = self[index]
         unregister_dependent_observers(old_value)
-        super(index, value)
-        notify_observers
+        remove_element_observers(old_value)
+        add_element_observers(value)    
+        super(index, value).tap do
+          notify_observers
+        end
+      end
+      
+      def pop
+        popped_element = last
+        unregister_dependent_observers(popped_element)
+        remove_element_observers(popped_element)
+        super.tap do
+          notify_observers
+        end
       end
       
       def delete(element)
         unregister_dependent_observers(element)
-        super(element)
-        notify_observers
+        remove_element_observers(element)
+        super(element).tap do
+          notify_observers
+        end
       end
       
       def delete_at(index)
         old_value = self[index]
         unregister_dependent_observers(old_value)
-        super(index)
-        notify_observers
+        remove_element_observers(old_value)
+        super(index).tap do
+          notify_observers
+        end
+      end
+      
+      def delete_if(&block)
+        if block_given?
+          old_array = Array.new(self)
+          super(&block).tap do |new_array|
+            (old_array - new_array).each do |element| 
+              unregister_dependent_observers(element)
+              remove_element_observers(element)
+            end
+            notify_observers
+          end
+        else
+          super
+        end
       end
       
       def clear
         each do |old_value|
           unregister_dependent_observers(old_value)
+          remove_element_observers(old_value)
+        end
+        super.tap do
+          notify_observers
+        end
+      end
+      
+      def reverse!
+        super.tap do
+          notify_observers
+        end
+      end
+
+      def collect!(&block)
+        if block_given?
+          each do |old_value|
+            unregister_dependent_observers(old_value)
+            remove_element_observers(old_value)
+          end
+          super(&block).tap do
+            each do |element|
+              add_element_observers(element)
+            end
+            notify_observers
+          end
+        else
+          super
+        end
+      end
+      alias map! collect!
+
+      def compact!
+        super.tap do
+          notify_observers
+        end
+      end
+
+      def flatten!(level=nil)
+        each do |old_value|
+          unregister_dependent_observers(old_value)
+          remove_element_observers(old_value)
+        end
+        (level.nil? ? super() : super(level)).tap do
+          each do |element|
+            add_element_observers(element)
+          end
+          notify_observers
+        end
+      end
+
+      def rotate!(count=1)
+        super(count).tap do
+          notify_observers
+        end
+      end
+
+      def select!(&block)
+        if block_given?
+          old_array = Array.new(self)
+          super(&block).tap do
+            (old_array - self).each do |old_value|
+              unregister_dependent_observers(old_value)
+              remove_element_observers(old_value)
+            end
+            notify_observers
+          end
+        else
+          super
+        end
+      end
+
+      def shuffle!(hash = nil)
+        (hash.nil? ? super() : super(random: hash[:random])).tap do
+          notify_observers
+        end
+      end
+
+      def slice!(arg1, arg2=nil)
+        old_array = Array.new(self)
+        (arg2.nil? ? super(arg1) : super(arg1, arg2)).tap do
+          (old_array - self).each do |old_value|
+            unregister_dependent_observers(old_value)
+            remove_element_observers(old_value)
+          end
+          notify_observers
+        end
+      end
+
+      def sort!(&block)
+        (block.nil? ? super() : super(&block)).tap do
+          notify_observers
+        end
+      end
+
+      def sort_by!(&block)
+        (block.nil? ? super() : super(&block)).tap do
+          notify_observers
+        end
+      end
+
+      def uniq!(&block)
+        each do |old_value|
+          unregister_dependent_observers(old_value)
+          remove_element_observers(old_value)
+        end
+        (block.nil? ? super() : super(&block)).tap do
+          each do |element|
+            add_element_observers(element)
+          end
+          notify_observers
+        end
+      end
+
+      def reject!(&block)
+        if block_given?
+          old_array = Array.new(self)
+          super(&block).tap do
+            (old_array - self).each do |old_value|
+              unregister_dependent_observers(old_value)
+              remove_element_observers(old_value)
+            end
+            notify_observers
+          end
+        else
+          super
         end
-        super()
-        notify_observers
       end
       
       def unregister_dependent_observers(old_value)

data/lib/glimmer/data_binding/observable_model.rb

@@ -34,7 +34,7 @@ module Glimmer
       end
 
       def has_observer_for_any_property?(observer)
-        property_observer_hash.values.map(&:to_a).sum.include?(observer)
+        property_observer_hash.values.map(&:to_a).reduce(:+).include?(observer)
       end
 
       def property_observer_hash

data/lib/glimmer/data_binding/observer.rb

@@ -59,6 +59,7 @@ module Glimmer
       # registers observer in an observable on a property (optional)
       # observer maintains registration list to unregister later
       def register(observable, property = nil)
+        return if observable.nil?
         unless observable.is_a?(Observable)
           # TODO refactor code to be more smart/polymorphic/automated and honor open/closed principle
           if observable.is_a?(Array)

metadata

@@ -1,15 +1,35 @@
 --- !ruby/object:Gem::Specification
 name: glimmer
 version: !ruby/object:Gem::Version
-  version: 0.10.1
+  version: 0.10.2
 platform: ruby
 authors:
 - AndyMaleh
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2020-07-27 00:00:00.000000000 Z
+date: 2020-08-20 00:00:00.000000000 Z
 dependencies:
+- !ruby/object:Gem::Dependency
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 1.0.2
+    - - "<"
+      - !ruby/object:Gem::Version
+        version: 2.0.0
+  name: array_include_methods
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 1.0.2
+    - - "<"
+      - !ruby/object:Gem::Version
+        version: 2.0.0
 - !ruby/object:Gem::Dependency
   requirement: !ruby/object:Gem::Requirement
     requirements: