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.
>
> Cees
>
> --
> Posted via http://www.ruby-forum.com/.
>