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

[ruby-talk:444315] Tutorial: Ruby GUI with Glimmer (by Mattias Velamsson)
by Andy Maleh 28 Aug '23

28 Aug '23

Mattias Velamsson recently shared a beginner's tutorial for making a GUI (Graphical User Interface) in Ruby titled "Ruby GUI with Glimmer". It provides a step-by-step code walkthrough that produces a full-fledged web-API-driven table-based business application. It uses various gems and APIs like glimmer-dsl-libui, dotenv, Net::HTTP, URI, JSON, and the Exchange Rates Data API. https://dev.to/smackdh/ruby-gui-with-glimmer-2fkh

1 0

[ruby-talk:444309] Rails Already Supports View Components!
by Andy Maleh 23 Aug '23

23 Aug '23

Rails Already Supports View Components! The video for the Montreal.rb Ruby Meetup April 3, 2023 talk "Rails Already Supports View Components!" has been posted! This talk will explain the various ways Rails already supports view components out of the box. https://andymaleh.blogspot.com/2023/08/montrealrb-apr-2023-rails-already.ht… https://youtu.be/9aT_ATtends

3 4

[ruby-talk:444308] [ANN] Learning by Reversing: Native Gems, Part 5
by Mohit Sindhwani 16 Aug '23

16 Aug '23

Hi Everyone, I started on a series to learn by reversing a simple native C Ruby gem. Part 5 is now published! This does a deep dive on understanding how to use the Ruby C API from a C file.It shows how the Ruby C API works & how it accesses Ruby data, raises exceptions, checks function arguments and so on. Link to Part 5: https://notepad.onghu.com/2023/learning-by-reversing-s1-e5-native-gems/ The first 4 parts are also online on my blog: * Part 1 - This covers the background to the gem we explore Link: https://notepad.onghu.com/2023/learning-by-reversing-s1-e1-native-gems/ * Part 2 - This goes into the details of how ruby loads the native gem and extension (and includes a nice sequence diagram of how all the bits happen together) Link: https://notepad.onghu.com/2023/learning-by-reversing-s1-e2-native-gems/ * Part 3 - How do we ensure that we have everything and that it actually gets built at installation? Link: https://notepad.onghu.com/2023/learning-by-reversing-s1-e3-native-gems/ * Part 4 - Understanding the development Makefil Link: https://notepad.onghu.com/2023/learning-by-reversing-s1-e4-native-gems/ Future posts are planned to go into details like: * Documenting the code * Running the specs and the performance benchmark * Enhancements: - Providing an executable - A gem that also works on JRuby - Making the gem ractor friendly - Patching an existing gem rather than a new module Comments on the posts or the plans welcome. I'm @onghu on Twitter or @onghu@ruby.social on Mastodon if you're on either. Best regards, Mohit.

1 0

[ruby-talk:444307] Every True Rubyist Builds Their Own Code Editor in Ruby!
by Andy Maleh 15 Aug '23

15 Aug '23

"Every self respecting Senior Software Engineer out there should build their own code editor, even if just as a toy app to later be discarded in favor of another code editor (though they might grow to prefer their own). And, if they are Rubyists, they should build their code editor in Ruby (whether using MRI Ruby, JRuby or Opal Ruby). If you think of yourself as a Ruby Senior Software Engineer, but cannot build your own code editor in Ruby, there are serious holes in your skillset!! Explore Glimmer libraries for many Ruby options to help you start the code editor building challenge and journey." Full Blog Post: https://andymaleh.blogspot.com/2023/08/every-true-rubyist-builds-their-own.… https://github.com/AndyObtiva/glimmer-cs-gladiator/raw/master/images/glimme…

1 0

[ruby-talk:444294] Alternative logging solutions
by Peter Hickman 04 Aug '23

04 Aug '23

Presently our applications use the standard Logger package that comes with Ruby and it works just fine. We use it in conjunction with the standard unix logrotate. Up to now everything has been working as expected Until the logrotate hit in the middle of some significant processing and a client had a query. What we found was a 2 second gap in the logs. The end of the old log was the start of a transaction and the start of the new log was the end of a completely different transaction. So we have lost partial information from two transactions and it is possible that there was at least one transaction between these two that was lost completely. Each transaction takes around 1 second to process, sometimes less This time it was not too big an issue and there were other ways to investigate the problem Is there some other way of logging that is even less likely to lose data?

4 10

[ruby-talk:444293] [ANN] oedipus_lex 2.6.2 Released
by Ryan Davis 03 Aug '23

03 Aug '23

oedipus_lex version 2.6.2 has been released! * home: <http://github.com/seattlerb/oedipus_lex> * rdoc: <http://docs.seattlerb.org/oedipus_lex> Oedipus Lex is a lexer generator in the same family as Rexical and Rex. Oedipus Lex is my independent lexer fork of Rexical. Rexical was in turn a fork of Rex. We've been unable to contact the author of rex in order to take it over, fix it up, extend it, and relicense it to MIT. So, Oedipus was written clean-room in order to bypass licensing constraints (and because bootstrapping is fun). Oedipus brings a lot of extras to the table and at this point is only historically related to rexical. The syntax has changed enough that any rexical lexer will have to be tweaked to work inside of oedipus. At the very least, you need to add slashes to all your regexps. Oedipus, like rexical, is based primarily on generating code much like you would a hand-written lexer. It is _not_ a table or hash driven lexer. It uses StrScanner within a multi-level case statement. As such, Oedipus matches on the _first_ match, not the longest (like lex and its ilk). This documentation is not meant to bypass any prerequisite knowledge on lexing or parsing. If you'd like to study the subject in further detail, please try [TIN321] or the [LLVM Tutorial] or some other good resource for CS learning. Books... books are good. I like books. Changes: ### 2.6.2 / 2023-08-03 * 1 bug fix: * Removed extra newline when do_parse option is used.

1 0

[ruby-talk:444292] [ANN] wxRuby3 0.9.0.rc-3
by martin＠corino.nl 27 Jul '23

27 Jul '23

Here is a third release candidate of the wxRuby3 gem that should be the last before the first stable 0.9.0 release. wxRuby3 is a cross-platform GUI library for Ruby, based on the mature wxWidgets GUI toolkit for C++. It uses native widgets wherever possible, providing the correct look, feel and behavior to GUI applications on Windows, OS X and Linux/GTK. wxRuby aims to provide a comprehensive solution to developing professional-standard desktop applications in Ruby. What's new: - improved documentation - more regression tests - update INSTALL.md with clearer MacOS instructions and update README with note about ARM64 M2 Chip being tested by @AndyObtiva - improved Wx logging support - various other improvements and fixes If you are interested check this out: Documentation: https://mcorino.github.io/wxRuby3/index.html Github: https://github.com/mcorino/wxruby3 Rubygems: https://rubygems.org/gems/wxruby3

1 0

[ruby-talk:444291] [ANN] imap_processor 1.8.1 Released
by Ryan Davis 27 Jul '23

27 Jul '23

imap_processor version 1.8.1 has been released! * home: <https://github.com/seattlerb/imap_processor> * rdoc: <http://docs.seattlerb.org/imap_processor> IMAPProcessor is a client for processing messages on an IMAP server. It provides some basic mechanisms for connecting to an IMAP server, determining capabilities and handling messages. IMAPProcessor ships with several executables which can query and manipulate IMAP mailboxes in several different ways: imap_archive :: Archives old messages to a new dated mailbox. imap_cleanse :: Delete messages older than a certain age in specified mailboxes. imap_flag :: Flag messages to/from certain people. imap_idle :: Shows new messages in a mailbox. imap_keywords :: Queries an IMAP server for keywords set on messages imap_learn :: Flags messages based on what you've flagged before. imap_mkdir :: Ensures that certain mailboxes exist. Changes: ### 1.8.1 / 2023-07-27 * 1 bug fix: * Cleanse: Use Regexp.escape when searching mailboxen.

1 0

[ruby-talk:444290] [ANN] graphics 1.1.0 Released
by Ryan Davis 26 Jul '23

26 Jul '23

graphics version 1.1.0 has been released! * home: <https://github.com/zenspider/graphics> * rdoc: <http://docs.seattlerb.org/graphics> Graphics provides a simple framework to implement games and/or simulations and is designed to follow mathematical conventions, NOT game programming conventions. Particularly it: * Uses degrees. * Draws in quadrant 1 (0-90 degrees). * Right hand rule: 0 degrees is east, 90 is north, etc. These allow simple things like Trigonometry functions to work as expected. It means that all that stuff you were taught in grade school still work as intended. This makes one less thing you have to adjust when implementing your simulation. Changes: ### 1.1.0 / 2023-07-26 * 3 minor enhancements: * Added anti-aliasing to polygon. Want to add filling at some point. * Requiring ruby 2.7+. Too many changes to ruby internals to try to maintain. * polygon now takes an array of points. * 4 bug fixes: * Fixed a bunch of compiler warnings for ruby struct changes. * Fixed font lookup on linux. (presidentbeef) * Fixed graphics_setup.sh for obsolete build flag on sdl2_image. (NickSchimek) * ruby 3.2: Fixed warning from ruby headers by explicitly removing alloc funcs.

1 0

[ruby-talk:444289] [ANN] minitest 5.19.0 Released
by Ryan Davis 26 Jul '23

26 Jul '23

minitest version 5.19.0 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.19.0 / 2023-07-26 * 2 minor enhancements: * Add metadata lazy accessor to Runnable / Result. (matteeyah) * Only load minitest/unit (aka ancient MiniTest compatibility layer) if ENV["MT_COMPAT"] * 1 bug fix: * Minitest::TestTask enthusiastically added itself to default. (ParadoxV5)

1 0