I did a small Python/Qt project at work that has gotten me pretty
excited about Qt. However from googling around, the only languages
people seem to be actively using to write Qt apps are C++ and Python.
So, a few questions:
1. What is the current state of Qt and Ruby, in terms of people
keeping bindings up to date, and people using it for projects?
2. Am I right that the qtbindings and qt_connect gems are the current
best way to go?
3. Are there working scintilla and webkit bindings?
4. Is anyone using Qt 4.8 + Ruby 1.9.3 for an active open source
project I can take a look at?
Apparently is active: https://www.ruby-toolbox.com/projects/qtbindings
Apparently few people use GUI for build desktop applications with Ruby,
I'm one of the few but I'm developing with FXRuby.
For the last three questions I have no answer. See you around.
4. Is anyone using Qt 4.8 + Ruby 1.9.3 for an active open source
project I can take a look at?
martin
I used qtbindings and ruby 1.9.3 for a building a reporting tool over a
MySql database. See https://github.com/badal/J2R (the Readme file is not
uptodate).
Before, I used FXRuby and Gtk2 for other projects. The main advantage I
found to Qt is that it has exactly the same look on Windows and OSX (I
developed under Windows and the project runs in production on
OSX-Server). This is not true for FXRuby nor Gtk2.
You may write me (michel@demazure.com) for more. I can send you some
technical doc (in French).
I used Qt via the `qtbindings' gem for a small personal project,
and the gem seems to be actively supported and is easy to install
on both Linux and Windows. You can of course take a look at my code
(https://github.com/stomar/nametrainer\), but I'm rather new to Ruby
and Qt myself and would not consider it exemplary in any way...
(Feedback or corrections are highly welcome.)
···
Am 12.12.2012 11:18, schrieb Martin DeMello:
I did a small Python/Qt project at work that has gotten me pretty
excited about Qt. However from googling around, the only languages
people seem to be actively using to write Qt apps are C++ and Python.
So, a few questions:
1. What is the current state of Qt and Ruby, in terms of people
keeping bindings up to date, and people using it for projects?
2. Am I right that the qtbindings and qt_connect gems are the current
best way to go?
3. Are there working scintilla and webkit bindings?
4. Is anyone using Qt 4.8 + Ruby 1.9.3 for an active open source
project I can take a look at?
Thanks, everyone. I got qtbindings up and running; qt_connect looks
interesting but still seems a little flaky on my system. (I'll play
with it some more and file bugs). I'll check out the examples people
pointed me to, together with the qt docs I should be in good shape.
martin
···
On Wed, Dec 12, 2012 at 2:18 AM, Martin DeMello <martindemello@gmail.com> wrote:
I did a small Python/Qt project at work that has gotten me pretty
excited about Qt. However from googling around, the only languages
people seem to be actively using to write Qt apps are C++ and Python.
So, a few questions:
1. What is the current state of Qt and Ruby, in terms of people
keeping bindings up to date, and people using it for projects?
2. Am I right that the qtbindings and qt_connect gems are the current
best way to go?
3. Are there working scintilla and webkit bindings?
4. Is anyone using Qt 4.8 + Ruby 1.9.3 for an active open source
project I can take a look at?
I have been using qtruby for several years now and find the qtbindings
gem the easiest way to stay up to date.
The gem is well maintained and very popular with more than 16000
downloads on rubygems.org.
I developed the qt_connect gem initially to make it possible to run my
qtruby applications using JRuby.
The main reason for doing this was that a qtruby application can then be
compiled and packaged into a single jar file, which is great for
distributing and protecting software sources.
The qt_connect gem for JRuby provides bindings to the Qt Jambi Java
classes and an interface to the Qt Jambi Signals and Slot mechanism.
After using this for a while I found the Qt Jambi Signal interface made
a lot more sense (for a Ruby programmer) than the one based on the
C++ API and I extended the Ruby bindings to support the same interface.
So the qt_connect gem can be used either with the qtbindings gem to
provide a Ruby interface OR with the QtJambi jars to provide a JRuby
interface to essentially the same qtruby programs.
Since I published the gem on rubygems and github earlier this year,
there have been about 600 downloads, but very little feedback.
I certainly plan to maintain the qt_connect gem, but would apppreciate
some more feedback.
I use qt_connect on both MRI and JRuby. I do most of my development on
MRI but regularly check that the application works on both platforms.
All my testing is done under Windows, but if more people are interested
to use the gem, further testing on OS X and Linux would be great.
This applies more to the JRuby version (where the gem supplies full
bindings to the platform dependant QtJambi jars) than the MRI version
(where the gem is a small extension of the qtbindings gem). Ultimately
it would be best to use the same interface on both MRI and JRuby
(maybe based on ffi) but given the size of the Qt framework that may
take a while to happen. Richard Dale is planning to do some new
qtruby development and in particular look at the slots and signal
syntax.
Incidentally, for anyone else interested in qt language bindings, I
just discovered EQL, which looks excellent: http://password-taxi.at/EQL
martin
···
On Sun, Dec 16, 2012 at 4:40 PM, Martin DeMello <martindemello@gmail.com> wrote:
Thanks, everyone. I got qtbindings up and running; qt_connect looks
interesting but still seems a little flaky on my system. (I'll play
with it some more and file bugs). I'll check out the examples people
pointed me to, together with the qt docs I should be in good shape.
martin
On Wed, Dec 12, 2012 at 2:18 AM, Martin DeMello <martindemello@gmail.com> wrote:
I did a small Python/Qt project at work that has gotten me pretty
excited about Qt. However from googling around, the only languages
people seem to be actively using to write Qt apps are C++ and Python.
So, a few questions:
1. What is the current state of Qt and Ruby, in terms of people
keeping bindings up to date, and people using it for projects?
2. Am I right that the qtbindings and qt_connect gems are the current
best way to go?
3. Are there working scintilla and webkit bindings?
4. Is anyone using Qt 4.8 + Ruby 1.9.3 for an active open source
project I can take a look at?
I really like the idea of trying to provide a more rubyish API. Do you
use qt_connect on MRI yourself, or do you primarily use it on JRuby?
I'd be happy to help test on linux + ruby 1.9.3 (which I notice is
missing from your "tested on" list).
martin
···
On Tue, Dec 18, 2012 at 12:25 PM, Cees Zeelenberg <lists@ruby-forum.com> wrote:
I have been using qtruby for several years now and find the qtbindings
gem the easiest way to stay up to date.
The gem is well maintained and very popular with more than 16000
downloads on rubygems.org.
I developed the qt_connect gem initially to make it possible to run my
qtruby applications using JRuby.
The main reason for doing this was that a qtruby application can then be
compiled and packaged into a single jar file, which is great for
distributing and protecting software sources.
The qt_connect gem for JRuby provides bindings to the Qt Jambi Java
classes and an interface to the Qt Jambi Signals and Slot mechanism.
After using this for a while I found the Qt Jambi Signal interface made
a lot more sense (for a Ruby programmer) than the one based on the
C++ API and I extended the Ruby bindings to support the same interface.
So the qt_connect gem can be used either with the qtbindings gem to
provide a Ruby interface OR with the QtJambi jars to provide a JRuby
interface to essentially the same qtruby programs.
Since I published the gem on rubygems and github earlier this year,
there have been about 600 downloads, but very little feedback.
I certainly plan to maintain the qt_connect gem, but would apppreciate
some more feedback.