- ruby-talk - ml.ruby-lang.org

[ruby-talk:444257] Glimmer DSL for WX 0.0.6 Released
by Andy Maleh 26 Jun '23

26 Jun '23

Glimmer DSL for WX 0.0.6 has been released! It now supports all layout sizers (like VBoxSizer, which is `v_box_sizer` in Glimmer DSL syntax), and includes a new sample (`samples/hello/hello_sizer.rb`). Sizer child controls can specify their own `sizer_args` declaratively within their bodies. GitHub: https://github.com/AndyObtiva/glimmer-dsl-wx Ruby Gem: https://rubygems.org/gems/glimmer-dsl-wx Change Log: 0.0.6: - Sizer (layout) support - samples/hello/hello_sizer.rb - Refactor/move glimmer_new samples to hello directory - Fix ControlProxy#frame_proxy method, which grabs the parent frame (going all the way to the top of the hierarchy)

1 0

[ruby-talk:444255] [ANN] elevenlabs-rb 0.1.0 released
by Stephen Schor 25 Jun '23

25 Jun '23

Hello I've just released elevenlabs-rb 0.1.0, A VERY light wrapper on top of elevenlabs's API for AI text-to-speech. I've only implemented the endpoints I need for my personal project but PRs are welcome! *Github:* https://github.com/nodanaonlyzuul/elevenlabs-rb *Rubygems:*https://rubygems.org/gems/elevenlabs-rb *Elevenlabs API Docs:* https://api.elevenlabs.io/docs Stephen

1 0

[ruby-talk:444254] I want to scrape all the recommended videos from a current YT page
by Philip Rhoades 25 Jun '23

25 Jun '23

People, Is there a way of doing this for a currently displayed page? - maybe this would have to be done from a Chrome extension? Thanks, Phil. -- Philip Rhoades PO Box 896 Cowra NSW 2794 Australia E-mail: phil(a)pricom.com.au

1 0

[ruby-talk:444252] [ANN] Glimmer DSL for WX (wxWidgets GUI Toolkit) [using wxruby3] 0.0.5 Released
by Andy Maleh 25 Jun '23

25 Jun '23

Just as promised, I built a Glimmer DSL for WX that supports the wxWidgets GUI toolkit using the new wxruby3 binding. It is high appreciated that the wxruby3 binding did the hard work and heavy lifting of binding low-level wxWidgets C/C++ code to Ruby code. Glimmer DSL for WX aims to add Declarative Minimalistic GUI Syntax, Convention over Configuration, Smart Defaults, and many other improved productivity/maintainability features like the upcoming Bidirectional/Unidirectional Data-Binding support. Glimmer DSL for WX Early Alpha 0.0.5 has just been released. https://raw.githubusercontent.com/AndyObtiva/glimmer-dsl-wx/master/screensh… Blog post: https://andymaleh.blogspot.com/2023/06/glimmer-dsl-for-wx-for-wxwidgets-gui… GitHub: https://github.com/AndyObtiva/glimmer-dsl-wx Rubygem: https://rubygems.org/gems/glimmer-dsl-wx Change Log: ## 0.0.1 - First alpha release of Glimmer DSL for WX for wxWidgets GUI Toolkit, using wxruby3 binding, and supporting "nothing" sample ## 0.0.2 - Remove forgotten occurrences of pd (puts_debuggerer) from code ## 0.0.3 - Support control arguments and properties - girb (Glimmer IRB) - Use frame title argument in samples/minimal/nothing.rb - Support `app_name` argument/property on `frame` - Automatically set `app_name` to `frame` `title` if `frame` `app_name` is not specified - samples/glimmer_new/hello_world.rb - samples/glimmer_new/hello_world2.rb ## 0.0.4 - Fix issue with complaining about not finding `frame` `app_name` when not specified despite it being optional ## 0.0.5 - Nested child control support - Listener support - `about_box` keyword for displaying an about dialog box - samples/glimmer_new/hello_button.rb - samples/glimmer_new/hello_button2.rb - Fix again the issue with complaining about not finding `frame` `app_name` when not specified despite it being optional Andy Maleh

2 1

[ruby-talk:444251] [ANN] wxRuby3/Shapes 0.9.0.beta-3 released
by martin＠corino.nl 24 Jun '23

24 Jun '23

For those that find wxRuby3's revival (mildly) interesting this may be of interest as well. A first public beta of the wxRuby3/Shapes framework has been released. This framework aims to provide a pure Ruby 2D shapes and diagramming library based on wxRuby3. If you are interested check this out: Release info: https://github.com/mcorino/wxRuby3-shapes/releases/tag/v0.9.0-beta.3 Github: https://github.com/mcorino/wxRuby3-shapes Github-pages: https://mcorino.github.io/wxRuby3-shapes/ Rubygems: https://rubygems.org/gems/wxruby3-shapes

1 0

[ruby-talk:444250] If You Liked Shoes, You'll Love Glimmer!
by Andy Maleh 22 Jun '23

22 Jun '23

A new Glimmer FAQ (Frequently Asked Questions) section (linked at the bottom) has been added to the Glimmer project README on GitHub (linked at the bottom) in order to answer questions like "How do Glimmer GUI DSLs compare to Shoes?" and "What is the difference between Glimmer and Glimmer DSL for SWT?", among others. https://github.com/AndyObtiva/glimmer-dsl-swt/raw/master/images/glimmer-dsl… I am including the Glimmer FAQ below for your convenience. If you have other questions that are not answered in the Glimmer FAQ, please reply with your questions. ## How do Glimmer GUI DSLs compare to Shoes? If you liked Shoes, you'll love Glimmer! That is because Glimmer does everything that Shoes did, but with a lighter and better GUI DSL (Graphical User Interface Domain Specific Language) that addresses all the issues that Shoes suffered from, such as: - Shoes does not allow code in Shoes blocks to use variables defined outside of Shoes blocks in a straightforward manner as it changes self inside Shoes blocks, breaking Ruby expectations and producing confusing behavior. On the other hand, Glimmer DSL blocks are 100% standard Ruby blocks that represent real closures, so they enable usage of variables defined outside the blocks in a 100% standard Ruby way. - Shoes lacks support for high-quality business widget controls (View components) like table and tree. Glimmer GUI DSLs that are feature complete like Glimmer DSL for SWT do support table and tree widgets. Some non-final Glimmer GUI DSLs like Glimmer DSL for LibUI support the table control too. - Shoes does not encourage proper separation of concerns with a correct MVC architecture (Model-View-Controller), resulting in a lot of non-presentation logic mixed with View code. Glimmer GUI DSLs do support proper separation of concerns 100% following the MVC or MVP (Model-View-Presenter) architecture by default. - Shoes does not provide a simple way for connecting View components to Model data. Glimmer GUI DSLs provide full bidirectional/unidirectional data-binding support out of the box that provides the terest code syntax for connecting Views to Models and keeping them in sync. - Shoes does not support a native mechanism for building custom View components. Glimmer does support the ability to build custom widgets (aka controls or View components), custom windows (aka shells), and custom shapes (canvas graphics). That results in much higher productivity by enabling the reuse of higher visual concepts as their own self-encapsulated components. - Shoes does not expose native features of its wrapped GUI toolkit. Glimmer GUI DSLs do expose all native features of their wrapped GUI toolkits, thus enabling developers to use a GUI toolkit like SWT directly when needed on top of using Glimmer DSL for SWT. That facilitates the 80/20 rule of having Glimmer GUI DSLs automate 80% of the work while still enabling software engineers to reach down to the low-level GUI toolkit API in 20% of the cases when needed (though in practice, it's probably more like 1% of the cases). It is great that Shoes paved the way for creating desktop GUI DSLs in Ruby. Glimmer took that approach to its maximum and produced the ultimate evolution of Shoes. ## What is the difference between Glimmer and Glimmer DSL for SWT? Glimmer DSL for SWT was the first GUI DSL created as part of the Glimmer project to enable building desktop applications, and it was originally just called Glimmer. It relied on the Eclipse SWT library to render GUI (Graphical User Interface) widget controls (View components) on every platform (Mac, Windows, and Linux). Eventually, the idea of a Glimmer DSL proved itself so successful and viable for building desktop apps with a fraction of the effort needed in other programming languages/technologies that it was expanded to support other GUI toolkits. So, Glimmer got renamed to Glimmer DSL for SWT, and the core Glimmer DSL engine got extracted to Glimmer (becoming a DSL framework), which then got reused to build other Glimmer GUI DSLs such as Glimmer DSL for LibUI and Glimmer DSL for GTK, among many others. ## What is the difference between Glimmer DSL for SWT and Glimmer DSL for LibUI? Both Glimmer DSL for SWT and Glimmer DSL for LibUI support rendering platform native widgets/controls, which enable building native desktop apps that look 100% native on every platform (Mac, Windows, and Linux). However, Glimmer DSL for SWT runs in JRuby (Ruby running in the JVM [Java Virtual Machine]) whereas Glimmer DSL for LibUI runs in standard Ruby (aka MRI Ruby or CRuby). Glimmer DSL for SWT is 100% feature-complete and has a final release. Glimmer DSL for LibUI is 100% complete as far as covering the LibUI features, but LibUI itself is still a mid-alpha library, so it is missing a few features that will get added eventually. ## What is the difference between Glimmer DSL for LibUI, Glimmer DSL for GTK, Glimmer DSL for Tk, and Glimmer DSL for FX? All of Glimmer DSL for LibUI, Glimmer DSL for GTK, Glimmer DSL for Tk, and Glimmer DSL for FX run in standard Ruby (aka MRI Ruby or CRuby). However, only Glimmer DSL for LibUI renders native controls on every platform (Mac, Windows, and Linux). The other libraries do not render native controls on every platform, albeit Glimmer DSL for GTK renders native controls on Linux distributions utilizing Gnome. Also, Glimmer DSL for LibUI does not require any prerequisites beyond installing the Ruby gem, so you can install it and get instant GUI with very little effort, whereas Glimmer DSL for GTK, Glimmer DSL for Tk, and Glimmer DSL for FX do require extra dependencies in general, albeit Glimmer DSL for GTK has everything it needs in Linux Gnome flavors. You may learn more about the differences between various Glimmer DSLs by checking out the Glimmer DSL Comparison Table (linked at the bottom). ## What is the difference between Glimmer DSL for SWT, Glimmer DSL for Swing, and Glimmer DSL for JFX? Glimmer DSL for SWT relies on the Eclipse SWT library, which renders native widgets on every platform (Mac, Windows, and Linux) to build desktop apps that look 100% native on every platform (Mac, Windows, and Linux). Glimmer DSL for Swing relies on Swing, which does not render native widgets on every platform. Glimmer DSL for JFX relies on JavaFX, which also does not render native widgets on every platform. You may learn more about the differences between various Glimmer DSLs by checking out the Glimmer DSL Comparison Table (linked at the bottom). ## Links: Glimmer GitHub Page: https://github.com/AndyObtiva/glimmer Glimmer FAQ: https://github.com/AndyObtiva/glimmer#faq Glimmer DSL Comparison Table: https://github.com/AndyObtiva/glimmer#glimmer-dsl-comparison-table Blog Post Announcement: https://andymaleh.blogspot.com/2023/06/if-you-liked-shoes-youll-love-glimme…

1 0

[ruby-talk:444249] [ANN] wxRuby3 0.9.0.beta-14 released
by martin＠corino.nl 22 Jun '23

22 Jun '23

Once again bitten in the behind by reality. Ran into a minor but very annoying platform issue when testing something new so here's a bug-fix release. If you are interested check this out: Release info: https://github.com/mcorino/wxRuby3/releases/tag/v0.9.0-beta.13 Github: https://github.com/mcorino/wxruby3 Rubygems: https://rubygems.org/gems/wxruby3

1 0

[ruby-talk:444248] [ANN] wxRuby3 0.9.0.beta-13 released
by martin＠corino.nl 21 Jun '23

21 Jun '23

A new public beta of the newly revived wxRuby3 has been released. If all goes well this should be the last beta release before the release candidate. If you are interested check this out: Release info: https://github.com/mcorino/wxRuby3/releases/tag/v0.9.0-beta.13 Github: https://github.com/mcorino/wxruby3 Rubygems: https://rubygems.org/gems/wxruby3

1 0

[ruby-talk:444247] [ANN] minitest 5.18.1 Released
by Ryan Davis 16 Jun '23

16 Jun '23

minitest version 5.18.1 has been released! * home: <https://github.com/minitest/minitest> * bugs: <https://github.com/minitest/minitest/issues> * rdoc: <https://docs.seattlerb.org/minitest> * vim: <https://github.com/sunaku/vim-ruby-minitest> * emacs: <https://github.com/arthurnn/minitest-emacs> minitest provides a complete suite of testing facilities supporting TDD, BDD, mocking, and benchmarking. "I had a class with Jim Weirich on testing last week and we were allowed to choose our testing frameworks. Kirk Haines and I were paired up and we cracked open the code for a few test frameworks... I MUST say that minitest is *very* readable / understandable compared to the 'other two' options we looked at. Nicely done and thank you for helping us keep our mental sanity." -- Wayne E. Seguin minitest/test is a small and incredibly fast unit testing framework. It provides a rich set of assertions to make your tests clean and readable. minitest/spec is a functionally complete spec engine. It hooks onto minitest/test and seamlessly bridges test assertions over to spec expectations. minitest/benchmark is an awesome way to assert the performance of your algorithms in a repeatable manner. Now you can assert that your newb co-worker doesn't replace your linear algorithm with an exponential one! minitest/mock by Steven Baker, is a beautifully tiny mock (and stub) object framework. minitest/pride shows pride in testing and adds coloring to your test output. I guess it is an example of how to write IO pipes too. :P minitest/test is meant to have a clean implementation for language implementors that need a minimal set of methods to bootstrap a working test suite. For example, there is no magic involved for test-case discovery. "Again, I can't praise enough the idea of a testing/specing framework that I can actually read in full in one sitting!" -- Piotr Szotkowski Comparing to rspec: rspec is a testing DSL. minitest is ruby. -- Adam Hawkins, "Bow Before MiniTest" minitest doesn't reinvent anything that ruby already provides, like: classes, modules, inheritance, methods. This means you only have to learn ruby to use minitest and all of your regular OO practices like extract-method refactorings still apply. Changes: ### 5.18.1 / 2023-06-16 * 3 bug fixes: * Avoid extra string allocations when filtering tests. (tenderlove) * Only mention deprecated ENV['N'] if it is an integer string. * Push up test_order to Minitest::Runnable to fix minitest/hell. (koic)

1 0

[ruby-talk:444246] [ANN] httpx 0.24.0 released
by Tiago Cardoso 15 Jun '23

15 Jun '23

httpx 0.24.0 has been released. ``` HTTPX.get("https://gitlab.com/honeyryderchuck/httpx <https://gitlab.com/honeyryderchuck/httpx>") ``` HTTPX is an HTTP client library for the Ruby programming language. Among its features, it supports: * HTTP/2 and HTTP/1.x protocol versions * Concurrent requests by default * Simple and chainable API * Proxy Support (HTTP(S), CONNECT tunnel, Socks4/4a/5) * Simple Timeout System * Lightweight by default (require what you need) And also: * Compression (gzip, deflate, brotli) * Streaming Requests * Authentication (Basic Auth, Digest Auth, AWS Sigv4) * Expect 100-continue * Multipart Requests * Cookies * HTTP/2 Server Push * H2C Upgrade * Automatic follow redirects * International Domain Names * GRPC * Circuit breaker * WebDAV * Datadog integration * Faraday integration * Webmock integration * Sentry integration Here are the updates since the last release: # 0.24.0 ## Features ### `:oauth` plugin The `:oauth` plugin manages the handling of a given OAuth session, in that it ships with convenience methods to generate a new access token, which it then injects in all requests. More info under https://honeyryderchuck.gitlab.io/httpx/wiki/OAuth ### session callbacks HTTP request/response lifecycle events have now the ability of being intercepted via public API callback methods: ```ruby HTTPX.on_request_completed do |request| puts "request to #{request.uri} sent" end.get(...) ``` More info under https://honeyryderchuck.gitlab.io/httpx/wiki/Events to know which events and callback methods are supported. ### `:circuit_breaker` plugin `on_circuit_open` callback A callback has been introduced for the `:circuit_breaker` plugin, which is triggered when a circuit is opened. ```ruby http = HTTPX.plugin(:circuit_breaker).on_circuit_open do |req| puts "circuit opened for #{req.uri}" end http.get(...) ``` ## Improvements Several `:response_cache` features have been improved: * `:response_cache` plugin: response cache store has been made thread-safe. * cached response sharing across threads is made safer, as stringio/tempfile instances are copied instead of shared (without copying the underling string/file). * stale cached responses are eliminate on cache store lookup/store operations. * already closed responses are evicted from the cache store. * fallback for lack of compatible response "date" header has been fixed to return a `Time` object. ## Bugfixes * Ability to recover from errors happening during response chunk processing (required for overriding behaviour and response chunk callbacks); error bubbling up will result in the connection being closed. * Happy eyeballs support for multi-homed early-resolved domain names (such as `localhost` under `/etc/hosts`) was broken, as it would try the first given IP; so, if given `::1` and connection would fail, it wouldn't try `127.0.0.1`, which would have succeeded. * `:digest_authentication` plugin was removing the "algorithm" header on `-sess` declared algorithms, which is required for HTTP digest auth negotiation. # 0.23.4 ## Bugfixes * fix `Response::Body#read` which rewinds on every call. # 0.23.3 ## Bugfixes * native resolver: fix missing exception variable in the DNS error code path. * native resolver: fixed short DNS packet handling when using TCP. # 0.23.2 ## Bugfixes * fix missing variable on code path in the native resolver. # 0.23.1 ## Bugfixes * fixed regression causing dns candidate names not being tried after first one fails.

1 0