Quoting Will Parsons (email@example.com):
Simple how-to's are fine, but try to build *any* kind sophisticated
GUI application using Ruby/Gtk, and one is sure to come accross one
*serious* obstacle - Ruby/Gtk documentation is so poor as to be
completely useless! Good luck in making anything more than a trivial
I have done that. As I already mentioned, it's been hard. But
obstacles can be solved. At least they have been, in the case of my
few applications (one quite large, the others smaller but requiring
live, non-sluggish interactive bitmap manipulations).
The documentation may be poor, but it is certainly not useless. Then,
I must say that I did my work before the 'introspection' stuff came
to be, so my best documentation was the source. Now, I may have more
problems. But still, everything has to be learned.
Anyway, Gtk was the only working option. I never liked the looks of Tk
(although people were able to do wonders with it - I think of
PureData). Same goes with Qt, that reeks of c++ from miles away. I
don't know if you ever had the joy of compiling Qt.
If I were the Ruby god, I'd start from scratch, doing a nice, tight
rendering engine in C that does not pretend to be directly usable from
applications, and an elegant, clean Ruby interface that exploits the
power of object orientation. And, of course, without the dependance
from hundreds of gems. But, having seen the complexity of Gtk, having
negotiated the use of every aspect I needed with much sweat, I know
that it would be years of effort before you'd obtain the complete
palette of necessary widgets.
If I did not have a job, and if someone offered to pay me for my
needs, that's one think I'd like to dedicate my time to for a few
Subject: Re: [ANN] 2018 Call for Grant Proposals
Date: dom 05 ago 18 10:52:54 -0400
* Se la Strada e la sua Virtu' non fossero state messe da parte,
* K * Carlo E. Prelz - firstname.lastname@example.org che bisogno ci sarebbe
* di parlare tanto di amore e di rettitudine? (Chuang-Tzu)