Richard Dale wrote:
Nicholas Marriott wrote:
I didn't get your original post so I'm replying here from someone quoting
it.
lighter and more free than Qt (not to mention the
fact that google fails to turn up a website for ruby-qt and it doesn't
appear in FreeBSD ports, making it useless for me)
Possibly that might be because the ruby bindings for Qt 3.x are called
'QtRuby'. There was an older unrelated project for Qt 1.x, called
'Ruby/Qt'. Try searching for 'kde + ruby' or 'qt + ruby' instead.
Aha! Found it. Thanks.
As QtRuby/Korundum are part of the KDE project I would assume FreeBSD
ports
exist.
Not that I can find. However, Google seems to imply it exists so perhaps it
just hasn't appeared yet.
I'm fairly suspicious of the link between KDE and QtRuby, I doubt it is
likely but I really really don't want to turn round one day and find I'm
having to tell people to install parts of KDE in order to get my stuff to
work.
I don't know what you mean be 'lighter' - there is a version of Qt for
embedded devices which works fine on PDAs and Smartphones.
I'm not really concerned with PDAs and Smartphones.
Qt is considerably larger than Wx and QtRuby appears to be larger than
wxRuby. On a more anecdotal level, I've consistently found Qt apps to have
problems with memory consumption and speed - this may be, however, because
on the whole the Qt apps I've used are KDE apps.
The next version of Qt, Qt 4.x will be GPL'd on the Windows platform, and
there will be a corresponding GPL'd windows version of QtRuby. It is
already licensed under the GPL on all other platforms, including Mac OS X.
If there is demand, Alex Kellett and myself will be happy to release a
commercial paid for version of QtRuby for Qt 4.x.
Windows support at a later date is not an awful lot of use for me. Windows
was part of the reason we changed toolkit in the first place (a large
proportion - probably 80-90% - of potential users are on Windows). wxRuby is
not perfect on Windows either, of course :-).
Anyway, I'm sticking with wxRuby at the moment despite it's problems. Now
that I know where it is, when QtRuby becomes more visible and portable - or
I get seriously pissed off with wxRuby's flaws - I will consider it again.
-- Nicholas.