glimmer-dsl-web 0.5.0 → 0.6.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 702f2aed3db1d4fcb6fbda9e794a756a3cdb44dfa47db714bbd350a5dd5e1d81
-  data.tar.gz: 5c6b8c276bc246c023cb9419744bceea8021450943cf7e2da2dfb0f86cbb4b3c
+  metadata.gz: b2c800cf33832acb3ab52d13d6ffa1db466d8c1c017bde29ce120c92c8e597e9
+  data.tar.gz: 81e200ca9d1c20c62ed5a5b3e900b9723c08c54933d93e35c7d7ac114cda480f
 SHA512:
-  metadata.gz: 5e3dbff73a4ebb082523dbcf76facc65d27a93e69e2873c08f02bd5939b34a1e9292eadd7698963d5eb53cfa164fbf7b2b14a100213c5d0f3d8d5566d6dc08cd
-  data.tar.gz: dfcc0d083636b8d0943b1ff78215c73651bfe768b970ac9cf81852a9e29ab54bf18f94d49483dc4753154c5497cbeb0f99acfbf91d684eebb97d533be19ccb30
+  metadata.gz: d86f6012cf574205d499aad0a684e33793ce547740917c186580cc7295da0c7b8e625ae20473e6cd49edb87fc8a7abe4d109ab2f98cbc52e2a7208608a76c3bd
+  data.tar.gz: 9269348151f2ad4007a1dccae80ff9ae2565af008c70285a6e0ffbe6d22faa4878b414d287556621d8ced0b23e3424980af25ec3027f3f8b39633c288ceb4e55

data/CHANGELOG.md

@@ -1,8 +1,14 @@
 # Change Log
 
+## 0.6.0
+
+- Support Component Custom Event Listeners (declare inside Component with `event :eventname` or `events :event1, :event2, ...` and then listen inside consumer code by adding `on_customeventname do; ...; end` listener inside content block of a consumed Glimmer Web Component)
+- Using latest opal-sprockets 1.0.4 will fix an issue with Opal compilation breaking whenever upgrading Opal gems in a Rails project and trying to restart server and render a webpage locally.
+
 ## 0.5.0
 
-- Support Glimmer Web Component Slots (by adding `slot: :slot_name` to any parent element, like a `div`, inside a `Glimmer::Web::Component` `markup {...}` element)
+- Support Glimmer Web Component Slots (by adding `slot: :slot_name` to any parent element, like a `div`, inside a `Glimmer::Web::Component` `markup {...}` element, and later having a consumer open a `slot_name {...}` block inside the content block of a consumed component)
+- Hello, Component Slots! Sample: `require 'glimmer-dsl-web/samples/hello/hello_component_slots'`
 
 ## 0.4.4
 

data/README.md

@@ -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 Web 0.5.0 (Beta)
+# [<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 Web 0.6.0 (Beta)
 ## Ruby-in-the-Browser Web Frontend Framework
 ### Finally, Ruby Developer Productivity, Happiness, and Fun in the Frontend!!!
 [![Gem Version](https://badge.fury.io/rb/glimmer-dsl-web.svg)](http://badge.fury.io/rb/glimmer-dsl-web)
@@ -12,7 +12,7 @@
 
 You can finally have Ruby developer happiness and productivity in the Frontend! No more wasting time splitting your resources across multiple languages, using badly engineered, over-engineered, or premature-optimization-obsessed JavaScript libraries, fighting JavaScript build issues (e.g. webpack), or rewriting Ruby Backend code in Frontend JavaScript. With [Ruby in the Browser](https://www.youtube.com/watch?v=4AdcfbI6A4c), you can have an exponential jump in development productivity (2x or higher), time-to-release (1/2 or less time), cost (1/2 or cheaper), and maintainability (~50% the code that is simpler and more readable) over JavaScript libraries like React, Angular, Ember, Vue, and Svelte, while being able to reuse Backend Ruby code as is in the Frontend for faster interactions when needed. Also, with Frontend Ruby, companies can cut their hiring budget in half by having Backend Ruby Software Engineers do Frontend Development in Ruby! [Ruby in the Browser](https://www.youtube.com/watch?v=4AdcfbI6A4c) finally fulfills every smart highly-productive Rubyist's dream by bringing Ruby productivity fun to Frontend Development, the same productivity fun you had for years and decades in Backend Development.
 
-[Glimmer](https://github.com/AndyObtiva/glimmer) DSL for Web enables building Web Frontends using [Ruby in the Browser](https://www.youtube.com/watch?v=4AdcfbI6A4c), as per [Matz's recommendation in his RubyConf 2022 keynote speech to replace JavaScript with Ruby](https://youtu.be/knutsgHTrfQ?t=789). It supports Rails' principle of the One Person Framework by not requiring any extra developers with JavaScript expertise, yet enabling Ruby (Backend) Software Engineers to develop the Frontend with Ruby code that is better than any JavaScript code produced by JS developers. It aims at providing the simplest, most intuitive, most straight-forward, and most productive frontend framework in existence. The framework follows the Ruby way (with [DSLs](https://martinfowler.com/books/dsl.html) and [TIMTOWTDI](https://en.wiktionary.org/wiki/TMTOWTDI#English)) and the Rails way ([Convention over Configuration](https://rubyonrails.org/doctrine)) in building Isomorphic Ruby on Rails Applications. It provides a Ruby [HTML DSL](#usage) (including full support for [SVG](#hello-svg)), which uniquely enables writing both structure code and logic code in one language. It supports both Unidirectional (One-Way) [Data-Binding](#hello-data-binding) (using `<=`) and Bidirectional (Two-Way) [Data-Binding](#hello-data-binding) (using `<=>`). Dynamic rendering (and re-rendering) of HTML content is also supported via [Content Data-Binding](#hello-content-data-binding). Modular design is supported with [Glimmer Web Components](#hello-component) and [Slots](#hello-component-slots). And, a Ruby CSS DSL is supported with the included [Glimmer DSL for CSS](https://github.com/AndyObtiva/glimmer-dsl-css). To automatically convert legacy HTML & CSS code to Glimmer DSL Ruby code, Software Engineers could use the included [`html_to_glimmer`](https://github.com/AndyObtiva/glimmer-dsl-xml#html-to-glimmer-converter) and [`css_to_glimmer`](https://github.com/AndyObtiva/glimmer-dsl-css#css-to-glimmer-converter) commands. Many [samples](#samples) are demonstrated in the [Rails sample app](https://github.com/AndyObtiva/sample-glimmer-dsl-web-rails7-app) (there is a very minimal [Standalone [No Rails] static site sample app](https://github.com/Largo/glimmer-dsl-web-standalone-demo) too). You can finally live in pure Rubyland on the Web in both the frontend and backend with [Glimmer DSL for Web](https://rubygems.org/gems/glimmer-dsl-web)!
+[Glimmer](https://github.com/AndyObtiva/glimmer) DSL for Web enables building Web Frontends using [Ruby in the Browser](https://www.youtube.com/watch?v=4AdcfbI6A4c), as per [Matz's recommendation in his RubyConf 2022 keynote speech to replace JavaScript with Ruby](https://youtu.be/knutsgHTrfQ?t=789). It supports Rails' principle of the One Person Framework by not requiring any extra developers with JavaScript expertise, yet enabling Ruby (Backend) Software Engineers to develop the Frontend with Ruby code that is better than any JavaScript code produced by JS developers. It aims at providing the simplest, most intuitive, most straight-forward, and most productive frontend framework in existence. The framework follows the Ruby way (with [DSLs](https://martinfowler.com/books/dsl.html) and [TIMTOWTDI](https://en.wiktionary.org/wiki/TMTOWTDI#English)) and the Rails way ([Convention over Configuration](https://rubyonrails.org/doctrine)) in building Isomorphic Ruby on Rails Applications. It provides a Ruby [HTML DSL](#usage) (including full support for [SVG](#hello-svg)), which uniquely enables writing both structure code and logic code in one language. It supports both Unidirectional (One-Way) [Data-Binding](#hello-data-binding) (using `<=`) and Bidirectional (Two-Way) [Data-Binding](#hello-data-binding) (using `<=>`). Dynamic rendering (and re-rendering) of HTML content is also supported via [Content Data-Binding](#hello-content-data-binding). Modular design is supported with [Glimmer Web Components](#hello-component), [Component Slots](#hello-component-slots), and Component Custom Event Listeners. And, a Ruby CSS DSL is supported with the included [Glimmer DSL for CSS](https://github.com/AndyObtiva/glimmer-dsl-css). To automatically convert legacy HTML & CSS code to Glimmer DSL Ruby code, Software Engineers could use the included [`html_to_glimmer`](https://github.com/AndyObtiva/glimmer-dsl-xml#html-to-glimmer-converter) and [`css_to_glimmer`](https://github.com/AndyObtiva/glimmer-dsl-css#css-to-glimmer-converter) commands. Many [samples](#samples) are demonstrated in the [Rails sample app](https://github.com/AndyObtiva/sample-glimmer-dsl-web-rails7-app) (there is a very minimal [Standalone [No Rails] static site sample app](https://github.com/Largo/glimmer-dsl-web-standalone-demo) too). You can finally live in pure Rubyland on the Web in both the frontend and backend with [Glimmer DSL for Web](https://rubygems.org/gems/glimmer-dsl-web)!
 
 [Glimmer DSL for Web](https://rubygems.org/gems/glimmer-dsl-web) aims to be a very simple Ruby-based drop-in replacement for your existing JavaScript Frontend library (e.g. React, Angular, Vue, Ember, Svelte) or your JavaScript Frontend layer in general. It does not change how your Frontend interacts with the Backend, meaning you can continue to write Rails Backend API endpoints as needed and make HTTP/Ajax requests or read data embedded in elements, but from [Ruby in the Browser](https://www.youtube.com/watch?v=4AdcfbI6A4c). Whatever is possible in JavaScript is possible when using Glimmer DSL for Web as it integrates with any existing JavaScript library. The [Rails sample app](https://github.com/AndyObtiva/sample-glimmer-dsl-web-rails7-app) demonstrates how to [make HTTP calls](https://github.com/AndyObtiva/sample-glimmer-dsl-web-rails7-app/blob/master/app/assets/opal/sample_selector/models/sample_api.rb) and how to [integrate with a JavaScript library](https://github.com/AndyObtiva/sample-glimmer-dsl-web-rails7-app/blob/master/app/views/layouts/application.html.erb) (highlightjs) that performs [code syntax highlighting](https://github.com/AndyObtiva/sample-glimmer-dsl-web-rails7-app/blob/master/app/assets/opal/sample_selector.rb).
 
@@ -1400,7 +1400,7 @@ rails new glimmer_app_server
 Add the following to `Gemfile`:
 
 ```
-gem 'glimmer-dsl-web', '~> 0.5.0'
+gem 'glimmer-dsl-web', '~> 0.6.0'
 ```
 
 Run:
@@ -1629,7 +1629,7 @@ Disable the `webpacker` gem line in `Gemfile`:
 Add the following to `Gemfile`:
 
 ```ruby
-gem 'glimmer-dsl-web', '~> 0.5.0'
+gem 'glimmer-dsl-web', '~> 0.6.0'
 ```
 
 Run:
@@ -3059,7 +3059,7 @@ class HelloComponentSlots
           h1('Shipping Address')
           legend('This is the address that is used for shipping your purchase.', style: {margin_bottom: 10})
         }
-        address_footer { # contribute elements to the address_header component slot
+        address_footer { # contribute elements to the address_footer component slot
           p(sub("#{strong('Note:')} #{em('Purchase will be returned if the Shipping Address does not accept it in one week.')}"))
         }
       }
@@ -3069,7 +3069,7 @@ class HelloComponentSlots
           h1('Billing Address')
           legend('This is the address that is used for your billing method (e.g. credit card).', style: {margin_bottom: 10})
         }
-        address_footer { # contribute elements to the address_header component slot
+        address_footer { # contribute elements to the address_footer component slot
           p(sub("#{strong('Note:')} #{em('Payment will fail if payment method does not match the Billing Address.')}"))
         }
       }
@@ -3389,7 +3389,9 @@ Screenshot:
 
 Every Glimmer Web Component can have a `style {}` block that contains CSS styles common to all instances of that element. That block is evaluated against the component class as such.
 
-Also, within every element, you can add `style(:property) <= [model, attribute]` element inline style data-binding statements to dynamically alter a CSS style property based on some changes to a model attribute.
+Also, within every element, you can add `style(:some_property) <= [model, attribute]` element inline-style data-binding statements to dynamically alter a CSS style property based on some changes to a model attribute.
+
+And, within every element, you can add `class_name(:some_css_class) <= [model, attribute]` element class-inclusion data-binding statements to dynamically alter the inclusion of a CSS class based on some changes to a model attribute.
 
 [lib/glimmer-dsl-web/samples/hello/hello_style.rb](/lib/glimmer-dsl-web/samples/hello/hello_style.rb)
 

data/VERSION

@@ -1 +1 @@
-0.5.0
+0.6.0

data/glimmer-dsl-web.gemspec

@@ -2,17 +2,17 @@
 # DO NOT EDIT THIS FILE DIRECTLY
 # Instead, edit Jeweler::Tasks in Rakefile, and run 'rake gemspec'
 # -*- encoding: utf-8 -*-
-# stub: glimmer-dsl-web 0.5.0 ruby lib
+# stub: glimmer-dsl-web 0.6.0 ruby lib
 
 Gem::Specification.new do |s|
   s.name = "glimmer-dsl-web".freeze
-  s.version = "0.5.0"
+  s.version = "0.6.0"
 
   s.required_rubygems_version = Gem::Requirement.new(">= 0".freeze) if s.respond_to? :required_rubygems_version=
   s.require_paths = ["lib".freeze]
   s.authors = ["Andy Maleh".freeze]
-  s.date = "2024-08-03"
-  s.description = "Glimmer DSL for Web (Ruby in the Browser Web Frontend Framework) enables building Web Frontends using Ruby in the Browser, as per Matz's recommendation in his RubyConf 2022 keynote speech to replace JavaScript with Ruby. It aims at providing the simplest, most intuitive, most straight-forward, and most productive frontend framework in existence. The framework follows the Ruby way (with DSLs and TIMTOWTDI) and the Rails way (Convention over Configuration) in building Isomorphic Ruby on Rails Applications. It provides a Ruby HTML DSL, which uniquely enables writing both structure code and logic code in one language. It supports both Unidirectional (One-Way) Data-Binding (using <=) and Bidirectional (Two-Way) Data-Binding (using <=>). Dynamic rendering (and re-rendering) of HTML content is also supported via Content Data-Binding. Modular design is supported with Glimmer Web Components and Slots. And, a Ruby CSS DSL is supported with the included Glimmer DSL for CSS. Many samples are demonstrated in the Rails sample app (there is a very minimal Standalone [No Rails] sample app too). You can finally live in pure Rubyland on the Web in both the frontend and backend with Glimmer DSL for Web! This gem relies on Opal Ruby.".freeze
+  s.date = "2024-08-24"
+  s.description = "Glimmer DSL for Web (Ruby in the Browser Web Frontend Framework) enables building Web Frontends using Ruby in the Browser, as per Matz's recommendation in his RubyConf 2022 keynote speech to replace JavaScript with Ruby. It aims at providing the simplest, most intuitive, most straight-forward, and most productive frontend framework in existence. The framework follows the Ruby way (with DSLs and TIMTOWTDI) and the Rails way (Convention over Configuration) in building Isomorphic Ruby on Rails Applications. It provides a Ruby HTML DSL, which uniquely enables writing both structure code and logic code in one language. It supports both Unidirectional (One-Way) Data-Binding (using <=) and Bidirectional (Two-Way) Data-Binding (using <=>). Dynamic rendering (and re-rendering) of HTML content is also supported via Content Data-Binding. Modular design is supported with Glimmer Web Components, Component Slots, and Component Custom Event Listeners. And, a Ruby CSS DSL is supported with the included Glimmer DSL for CSS. Many samples are demonstrated in the Rails sample app (there is a very minimal Standalone [No Rails] sample app too). You can finally live in pure Rubyland on the Web in both the frontend and backend with Glimmer DSL for Web! This gem relies on Opal Ruby.".freeze
   s.email = "andy.am@gmail.com".freeze
   s.extra_rdoc_files = [
     "CHANGELOG.md",

data/lib/glimmer/web/component.rb

@@ -89,6 +89,20 @@ module Glimmer
           @after_render = block
         end
         
+        def event(event)
+          @events ||= []
+          event = event.to_sym
+          @events << event unless @events.include?(event)
+        end
+        
+        def events(*events)
+          if events.empty?
+            @events
+          else
+            events.each { |event| event(event) }
+          end
+        end
+        
         def keyword
           self.name.underscore.gsub('::', '__')
         end
@@ -255,7 +269,7 @@ module Glimmer
       end
       # <- end of class methods
       
-      attr_reader :markup_root, :parent, :args, :options, :style_block, :component_style, :slot_elements
+      attr_reader :markup_root, :parent, :args, :options, :style_block, :component_style, :slot_elements, :events
       alias parent_proxy parent
 
       def initialize(parent, args, options, &content)
@@ -272,6 +286,7 @@ module Glimmer
         @args = args
         options ||= {}
         @options = self.class.options.merge(options)
+        @events = self.class.instance_variable_get("@events")
         @content = Util::ProcTracker.new(content) if content
 #         @style_blocks = {} # TODO enable when doing bulk head rendering in the future
         execute_hooks('before_render')
@@ -317,32 +332,84 @@ module Glimmer
       def can_handle_observation_request?(observation_request)
         observation_request = observation_request.to_s
         result = false
-        if observation_request.start_with?('on_updated_')
-          property = observation_request.sub(/^on_updated_/, '')
+        if observation_request.start_with?('on_update_') # TODO change to on_someprop_update & document this feature
+          property = observation_request.sub(/^on_update_/, '')
           result = can_add_observer?(property)
+        elsif observation_request.start_with?('on_')
+          event = observation_request.sub(/^on_/, '')
+          result = can_add_observer?(event)
         end
-        result || markup_root&.can_handle_observation_request?(observation_request)
+        result || @markup_root&.can_handle_observation_request?(observation_request)
       end
 
       def handle_observation_request(observation_request, block)
         observation_request = observation_request.to_s
-        if observation_request.start_with?('on_updated_')
-          property = observation_request.sub(/^on_updated_/, '') # TODO look into eliminating duplication from above
+        if observation_request.start_with?('on_update_')
+          property = observation_request.sub(/^on_update_/, '') # TODO look into eliminating duplication from above
           add_observer(DataBinding::Observer.proc(&block), property) if can_add_observer?(property)
+        elsif observation_request.start_with?('on_')
+          event = observation_request.sub(/^on_/, '') # TODO look into eliminating duplication from above
+          add_observer(DataBinding::Observer.proc(&block), event) if can_add_observer?(event)
         else
-          markup_root.handle_observation_request(observation_request, block)
+          @markup_root.handle_observation_request(observation_request, block)
         end
       end
 
-      def can_add_observer?(attribute_name)
-        has_instance_method?(attribute_name) || has_instance_method?("#{attribute_name}?") || @markup_root.can_add_observer?(attribute_name)
+      def can_add_observer?(attribute_or_event)
+        can_add_attribute_observer?(attribute_or_event) ||
+          can_add_custom_event_listener?(attribute_or_event)
       end
 
-      def add_observer(observer, attribute_name)
-        if has_instance_method?(attribute_name)
-          super(observer, attribute_name)
+      def can_add_attribute_observer?(attribute_name)
+        has_instance_method?(attribute_name) || has_instance_method?("#{attribute_name}?")
+      end
+
+      def can_add_custom_event_listener?(event)
+        events.include?(event.to_sym)
+      end
+
+      def add_observer(observer, attribute_or_event)
+        if can_add_attribute_observer?(attribute_or_event)
+          super(observer, attribute_or_event)
+        elsif can_add_custom_event_listener?(attribute_or_event)
+          add_custom_event_listener(observer, attribute_or_event)
+        end
+      end
+      
+      def custom_event_listeners_for(event)
+        event = event.to_sym
+        @custom_event_listeners ||= {}
+        @custom_event_listeners[event] ||= []
+      end
+      
+      def add_custom_event_listener(observer, event)
+        custom_event_listeners_for(event) << observer
+      end
+      
+      def remove_observer(observer, attribute_or_event, options = {})
+        if can_add_attribute_observer?(attribute_or_event)
+          super(observer, attribute_or_event)
+        elsif can_add_custom_event_listener?(attribute_or_event)
+          remove_custom_event_listener(observer, attribute_or_event)
+        end
+      end
+      
+      def remove_custom_event_listener(observer, event)
+        event = event.to_sym
+        custom_event_listeners_for(event).delete(observer) if custom_event_listeners_for(event).include?(observer)
+      end
+      
+      def notify_listeners(event, *args)
+        if can_add_custom_event_listener?(event)
+          notify_custom_event_listeners(event, *args)
         else
-          @markup_root.add_observer(observer, attribute_name)
+          @markup_root&.notify_listeners(event)
+        end
+      end
+      
+      def notify_custom_event_listeners(event, *args)
+        custom_event_listeners_for(event).each do |listener|
+          listener.call(*args)
         end
       end
 

data/lib/glimmer-dsl-web/samples/hello/hello_component.rb

@@ -126,7 +126,7 @@ class AddressForm
           value <=> [address, :full_name]
         }
         
-        @somelabel = label('Street: ', for: 'street-field')
+        label('Street: ', for: 'street-field')
         input(id: 'street-field') {
           value <=> [address, :street]
         }

data/lib/glimmer-dsl-web/samples/hello/hello_component_slots.rb

@@ -97,9 +97,9 @@ end
 #
 # Including Glimmer::Web::Component makes this class a View component and automatically
 # generates a new Glimmer HTML DSL keyword that matches the lowercase underscored version
-# of the name of the class. AddressForm generates address_form keyword, which can be used
+# of the name of the class. AddressForm generates address_form_with_slots keyword, which can be used
 # elsewhere in Glimmer HTML DSL code as done inside HelloComponentSlots below.
-class AddressForm
+class AddressFormWithSlots
   include Glimmer::Web::Component
   
   option :address
@@ -149,7 +149,7 @@ class AddressForm
         }
       }
       
-      div(style: 'margin: 5px') {
+      div(style: {margin: 5}) {
         inner_text <= [address, :summary,
                         computed_by: address.members + ['state_code'],
                       ]
@@ -199,22 +199,22 @@ class HelloComponentSlots
   
   markup {
     div {
-      address_form(address: @shipping_address) {
+      address_form_with_slots(address: @shipping_address) {
         address_header { # contribute elements to the address_header component slot
           h1('Shipping Address')
           legend('This is the address that is used for shipping your purchase.', style: {margin_bottom: 10})
         }
-        address_footer { # contribute elements to the address_header component slot
+        address_footer { # contribute elements to the address_footer component slot
           p(sub("#{strong('Note:')} #{em('Purchase will be returned if the Shipping Address does not accept it in one week.')}"))
         }
       }
       
-      address_form(address: @billing_address) {
+      address_form_with_slots(address: @billing_address) {
         address_header { # contribute elements to the address_header component slot
           h1('Billing Address')
           legend('This is the address that is used for your billing method (e.g. credit card).', style: {margin_bottom: 10})
         }
-        address_footer { # contribute elements to the address_header component slot
+        address_footer { # contribute elements to the address_footer component slot
           p(sub("#{strong('Note:')} #{em('Payment will fail if payment method does not match the Billing Address.')}"))
         }
       }

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: glimmer-dsl-web
 version: !ruby/object:Gem::Version
-  version: 0.5.0
+  version: 0.6.0
 platform: ruby
 authors:
 - Andy Maleh
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2024-08-03 00:00:00.000000000 Z
+date: 2024-08-24 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: glimmer
@@ -240,12 +240,12 @@ description: Glimmer DSL for Web (Ruby in the Browser Web Frontend Framework) en
   both structure code and logic code in one language. It supports both Unidirectional
   (One-Way) Data-Binding (using <=) and Bidirectional (Two-Way) Data-Binding (using
   <=>). Dynamic rendering (and re-rendering) of HTML content is also supported via
-  Content Data-Binding. Modular design is supported with Glimmer Web Components and
-  Slots. And, a Ruby CSS DSL is supported with the included Glimmer DSL for CSS. Many
-  samples are demonstrated in the Rails sample app (there is a very minimal Standalone
-  [No Rails] sample app too). You can finally live in pure Rubyland on the Web in
-  both the frontend and backend with Glimmer DSL for Web! This gem relies on Opal
-  Ruby.
+  Content Data-Binding. Modular design is supported with Glimmer Web Components, Component
+  Slots, and Component Custom Event Listeners. And, a Ruby CSS DSL is supported with
+  the included Glimmer DSL for CSS. Many samples are demonstrated in the Rails sample
+  app (there is a very minimal Standalone [No Rails] sample app too). You can finally
+  live in pure Rubyland on the Web in both the frontend and backend with Glimmer DSL
+  for Web! This gem relies on Opal Ruby.
 email: andy.am@gmail.com
 executables: []
 extensions: []