As a "downstream" user, though, fiddle is not easy to use. Often I just get segfaults and
then I end up not understanding why. I can figure out indirectly to some extent and with
helpful comments (e. g. GC kicking in), but by and large I'd love if ruby-fiddle would have
more debug-friendly support - similar to did-you-mean gem or the recent debug-related
changes by mame in MRI ruby.
Having worked with ruby-gtk a lot I am kind of used to modify core widgets such as
Gtk::Windows or Gtk::Box (horizontal and vertical). I like simple APIs such as .add()
or << just to add widgets together, a bit like LEGO building blocks.
With fiddle, though, this is a bit complicated. So the core question for this issue is
whether fiddle could allow for "designated" pseudoclasses? I'd love to build up
classes that can simulate the Gtk widgets to some extent (at the least what libui
allows for; see also libui-ng that has been recently started).
Something where I can build "pseudoclasses" and then at the least the error
messages can be more helpful. Rather than a segfault as such, something
that allows us to investigate which line is faulty or why it crashed (e. g. GC
kicking in). kojix2 showed various work arounds (see the examples he provides
for ruby-libui) but this requires some more expert knowledge than many ruby
developers have. For instance I do not really know C. And while I should really
have learned C properly, ruby is simply more fun to work with! :D
I do not know how easy it would be to have something like pseudoclasses
work, and better error/debug support for fiddle. It's ok if the downstream
dev has to write more code to enable this - I am not really suggesting an
"autofixer" that solves all problems as-is. But something with better debug-support
and to use fiddle in a more ruby-way, including a traditional OOP-like hierarchy.
Getting random SEGFAULTS and not really knowing why can be frustrating.
Other than that fiddle is pretty cool. (ruby-gtk via gobject-introspection also
has this problem partially by the way - the error messages I get are often
not super-useful.)
Hello fiddle-folks,
fiddle is quite epic. kojix2 wrote the bindings (if you can call them) for libui - see here for most of the try_extern calls:
https://github.com/kojix2/LibUI/blob/main/lib/libui/ffi.rb
As a "downstream" user, though, fiddle is not easy to use. Often I just get segfaults and then I end up not understanding why. I can figure out indirectly to some extent and with helpful comments (e. g. GC kicking in), but by and large I'd love if ruby-fiddle would have more debug-friendly support - similar to did-you-mean gem or the recent debug-related changes by mame in MRI ruby.
Having worked with ruby-gtk a lot I am kind of used to modify core widgets such as Gtk::Windows or Gtk::Box (horizontal and vertical). I like simple APIs such as .add() or << just to add widgets together, a bit like LEGO building blocks.
With fiddle, though, this is a bit complicated. So the core question for this issue is whether fiddle could allow for "designated" pseudoclasses? I'd love to build up classes that can simulate the Gtk widgets to some extent (at the least what libui allows for; see also libui-ng that has been recently started).
Something where I can build "pseudoclasses" and then at the least the error messages can be more helpful. Rather than a segfault as such, something that allows us to investigate which line is faulty or why it crashed (e. g. GC kicking in). kojix2 showed various work arounds (see the examples he provides for ruby-libui) but this requires some more expert knowledge than many ruby developers have. For instance I do not really know C. And while I should really have learned C properly, ruby is simply more fun to work with! :D
I do not know how easy it would be to have something like pseudoclasses work, and better error/debug support for fiddle. It's ok if the downstream dev has to write more code to enable this - I am not really suggesting an "autofixer" that solves all problems as-is. But something with better debug-support and to use fiddle in a more ruby-way, including a traditional OOP-like hierarchy. Getting random SEGFAULTS and not really knowing why can be frustrating.
Other than that fiddle is pretty cool. (ruby-gtk via gobject-introspection also has this problem partially by the way - the error messages I get are often not super-useful.)