Asp Forum - [ANN] QtRuby 1.4.7

richard.j.dale@gmail.com

10/30/2006 8:38:00 PM

URIS

http://rubyforge.org/projects...
http://developer.kde.org/language-bindings/ruby/...

NAME

QtRuby 1.4.7

SYNOPSIS

Ruby bindings for the Qt4 GUI apis. Many fixes and
improvements. QtDBus now works.

DESCRIPTION

Highlights from the QtRuby ChangeLog since release 1.4.7:

* Support for Qt 4.2 final

* The Qt4 version of QtRuby can be installed at the same time as
the Qt3 version.
* Use:
- require 'Qt3'
- require 'Qt4'
- require 'Qt'
The last option will default to Qt4 QtRuby.
* The command line api introspection tool can be used to query
both Qt3 and Qt4 apis:
- rbqt3api
- rbqt4api
- rbqtapi
Again the last option will default to the Qt4 api for QtRuby
* The 'rbuic' tool has been renamed 'rbuic4' to avoid a clash with
the Qt3 one.
* The Qt3 and Qt4 versions of the Smoke library have different
versions and can be installed in the same directory

* Added the rbrcc Ruby resource compiler tool

* Optional support for the QtDbus classes, and Qt QDBus examples
ported to ruby

* Optional support for the Qwt plotting library

* Blocks can be used as targets for connect calls as well as ordinary
slots:

* Added a new variant of connect, which takes a SIGNAL as an
argument, along with a block. For example:

quit.connect(SIGNAL(:clicked)) { puts 'quit pressed' }

The block is called in the context of where the connect call was
made, and 'self' needn't be a Qt::Object. It is similar to
the
signal_connect() method in ruby-gnome. This was suggested by
rickdangerous on the #qtruby irc channel.

* Here is an example of the class method connect() call with a block
as a target:

app = Qt::Application.new(ARGV)
quit = Qt::PushButton.new('Quit')
Qt::Object.connect(quit, SIGNAL('clicked()'), app) do
puts 'quit clicked'
end

The block is executed in the context of the target instance,
'app' in this case.

* And the instance method form:

class MyButton < Qt::Button
def initialize(text)
super(text)
connect(self, SIGNAL(:clicked)) do
puts 'button clicked'
end
end
...

The block is executed in the context of self - the instance making
the connect() call.

CONFIG

See the qtruby/INSTALL file for details of configuration, building
and installation.

BUILDING ON WINDOWS

* The smoke library can be built on windows by manually editing
qtguess.pl.in and generate.pl.in (automake doesn't work with
qtruby on Windows). Run 'perl qtguess.pl' to for the configure
tests. Then run 'perl generate.pl' to generate the Smoke sources,
and build with qmake. Use extconf.rb and qmake to build the
qtruby extension and rbuic tool.

ENVIRONMENTS

Linux, BSD*, Unix etc
Mac OS X, Windows

AUTHORS

Richard Dale with Caleb Tennis, Alexander Kellett and others.
Special thanks to kelko and rickdangerous for suggesting how
to implment 'blocks as slots' for this release.

15 Answers

M. Edward (Ed) Borasky

10/30/2006 9:19:00 PM

richard.j.dale@gmail.com wrote:
> URIS
>
> http://rubyforge.org/projects...
> http://developer.kde.org/language-bindings/ruby/...
>
> NAME
>
> QtRuby 1.4.7
>
> SYNOPSIS
>
> Ruby bindings for the Qt4 GUI apis. Many fixes and
> improvements. QtDBus now works.
>
> DESCRIPTION
>
> Highlights from the QtRuby ChangeLog since release 1.4.7:
>
> * Support for Qt 4.2 final
>
> * The Qt4 version of QtRuby can be installed at the same time as
> the Qt3 version.
> * Use:
> - require 'Qt3'
> - require 'Qt4'
> - require 'Qt'
> The last option will default to Qt4 QtRuby.
> * The command line api introspection tool can be used to query
> both Qt3 and Qt4 apis:
> - rbqt3api
> - rbqt4api
> - rbqtapi
> Again the last option will default to the Qt4 api for QtRuby
> * The 'rbuic' tool has been renamed 'rbuic4' to avoid a clash with
> the Qt3 one.
> * The Qt3 and Qt4 versions of the Smoke library have different
> versions and can be installed in the same directory
>
> * Added the rbrcc Ruby resource compiler tool
>
> * Optional support for the QtDbus classes, and Qt QDBus examples
> ported to ruby
>
> * Optional support for the Qwt plotting library
>
> * Blocks can be used as targets for connect calls as well as ordinary
> slots:
>
> * Added a new variant of connect, which takes a SIGNAL as an
> argument, along with a block. For example:
>
> quit.connect(SIGNAL(:clicked)) { puts 'quit pressed' }
>
> The block is called in the context of where the connect call was
> made, and 'self' needn't be a Qt::Object. It is similar to
> the
> signal_connect() method in ruby-gnome. This was suggested by
> rickdangerous on the #qtruby irc channel.
>
> * Here is an example of the class method connect() call with a block
> as a target:
>
> app = Qt::Application.new(ARGV)
> quit = Qt::PushButton.new('Quit')
> Qt::Object.connect(quit, SIGNAL('clicked()'), app) do
> puts 'quit clicked'
> end
>
> The block is executed in the context of the target instance,
> 'app' in this case.
>
> * And the instance method form:
>
> class MyButton < Qt::Button
> def initialize(text)
> super(text)
> connect(self, SIGNAL(:clicked)) do
> puts 'button clicked'
> end
> end
> ...
>
> The block is executed in the context of self - the instance making
> the connect() call.
>
> CONFIG
>
> See the qtruby/INSTALL file for details of configuration, building
> and installation.
>
> BUILDING ON WINDOWS
>
> * The smoke library can be built on windows by manually editing
> qtguess.pl.in and generate.pl.in (automake doesn't work with
> qtruby on Windows). Run 'perl qtguess.pl' to for the configure
> tests. Then run 'perl generate.pl' to generate the Smoke sources,
> and build with qmake. Use extconf.rb and qmake to build the
> qtruby extension and rbuic tool.
>
> ENVIRONMENTS
>
> Linux, BSD*, Unix etc
> Mac OS X, Windows
>
> AUTHORS
>
> Richard Dale with Caleb Tennis, Alexander Kellett and others.
> Special thanks to kelko and rickdangerous for suggesting how
> to implment 'blocks as slots' for this release.
>
>
>
Awesome!! Questions:

1. Does all this magic work on Windows?
2. Is it packaged as a gem?
3. Is Caleb going to update his excellent tutorial on QT Ruby?

Pau Garcia i Quiles

10/30/2006 10:15:00 PM

Quoting "richard.j.dale@gmail.com" <richard.j.dale@gmail.com>:

Awesome!

> URIS
>
> http://rubyforge.org/projects...
> http://developer.kde.org/language-bindings/ruby/...
>
> NAME
>
> QtRuby 1.4.7
>
> SYNOPSIS
>
> Ruby bindings for the Qt4 GUI apis. Many fixes and
> improvements. QtDBus now works.
>
> DESCRIPTION
>
> Highlights from the QtRuby ChangeLog since release 1.4.7:
>
> * Support for Qt 4.2 final
>
> * The Qt4 version of QtRuby can be installed at the same time as
> the Qt3 version.
> * Use:
> - require 'Qt3'
> - require 'Qt4'
> - require 'Qt'
> The last option will default to Qt4 QtRuby.
> * The command line api introspection tool can be used to query
> both Qt3 and Qt4 apis:
> - rbqt3api
> - rbqt4api
> - rbqtapi
> Again the last option will default to the Qt4 api for QtRuby
> * The 'rbuic' tool has been renamed 'rbuic4' to avoid a clash with
> the Qt3 one.
> * The Qt3 and Qt4 versions of the Smoke library have different
> versions and can be installed in the same directory
>
> * Added the rbrcc Ruby resource compiler tool
>
> * Optional support for the QtDbus classes, and Qt QDBus examples
> ported to ruby
>
> * Optional support for the Qwt plotting library
>
> * Blocks can be used as targets for connect calls as well as ordinary
> slots:
>
> * Added a new variant of connect, which takes a SIGNAL as an
> argument, along with a block. For example:
>
> quit.connect(SIGNAL(:clicked)) { puts 'quit pressed' }
>
> The block is called in the context of where the connect call was
> made, and 'self' needn't be a Qt::Object. It is similar to
> the
> signal_connect() method in ruby-gnome. This was suggested by
> rickdangerous on the #qtruby irc channel.
>
> * Here is an example of the class method connect() call with a block
> as a target:
>
> app = Qt::Application.new(ARGV)
> quit = Qt::PushButton.new('Quit')
> Qt::Object.connect(quit, SIGNAL('clicked()'), app) do
> puts 'quit clicked'
> end
>
> The block is executed in the context of the target instance,
> 'app' in this case.
>
> * And the instance method form:
>
> class MyButton < Qt::Button
> def initialize(text)
> super(text)
> connect(self, SIGNAL(:clicked)) do
> puts 'button clicked'
> end
> end
> ...
>
> The block is executed in the context of self - the instance making
> the connect() call.
>
> CONFIG
>
> See the qtruby/INSTALL file for details of configuration, building
> and installation.
>
> BUILDING ON WINDOWS
>
> * The smoke library can be built on windows by manually editing
> qtguess.pl.in and generate.pl.in (automake doesn't work with
> qtruby on Windows). Run 'perl qtguess.pl' to for the configure
> tests. Then run 'perl generate.pl' to generate the Smoke sources,
> and build with qmake. Use extconf.rb and qmake to build the
> qtruby extension and rbuic tool.
>
> ENVIRONMENTS
>
> Linux, BSD*, Unix etc
> Mac OS X, Windows
>
> AUTHORS
>
> Richard Dale with Caleb Tennis, Alexander Kellett and others.
> Special thanks to kelko and rickdangerous for suggesting how
> to implment 'blocks as slots' for this release.
>
>
>

Vincent Fourmond

10/30/2006 10:23:00 PM

richard.j.dale@gmail.com wrote:
> URIS
>
> http://rubyforge.org/projects...
> http://developer.kde.org/language-bindings/ruby/...
>
> NAME
>
> QtRuby 1.4.7
> * Blocks can be used as targets for connect calls as well as ordinary
> slots:

Great, that's exactly what was missing from 1.4.6 !! I'll make a new
upload as soon as the previous one is in the Debian archive (shoudln't
take too long, hopefully...)

Cheers !

Vince

David Vallner

10/30/2006 11:23:00 PM

M. Edward (Ed) Borasky wrote:
> Awesome!! Questions:
>
> 1. Does all this magic work on Windows?
> 2. Is it packaged as a gem?
>

Seconded, mswin32 gem or bust. I'm not particularly in the mood for
polluting my machine with things related to compiling C, I sure as hell
don't have the presence of mind to keep results thereof between the
inevitable full reinstalls, and that it's overall a Good Thing for use
outside personal code I don't need to remember.

Please, give me a reason to quit Python for GUI work, clashing naming
conventions of DOOM keep making me want to scream at someone on that
side of the ballpark.

*idly daydreams of mswin64 Ruby and native gems*

David Vallner

richard.j.dale@gmail.com

10/31/2006 3:20:00 AM

Vincent Fourmond wrote:
> richard.j.dale@gmail.com wrote:
> > URIS
> >
> > http://rubyforge.org/projects...
> > http://developer.kde.org/language-bindings/ruby/...
> >
> > NAME
> >
> > QtRuby 1.4.7
> > * Blocks can be used as targets for connect calls as well as ordinary
> > slots:
>
> Great, that's exactly what was missing from 1.4.6 !! I'll make a new
> upload as soon as the previous one is in the Debian archive (shoudln't
> take too long, hopefully...)
>
> Cheers !
>
> Vince
I forgot to include your Debian patch in the release. I hope to rectify
that and do another release in 2-3 weeks along with a rbqdbusxml2rb
tool and more fixes for QtDBus, and more work on fixing the examples.

-- Richard

Caleb Tennis

10/31/2006 12:13:00 PM

> 3. Is Caleb going to update his excellent tutorial on QT Ruby?
>

I am, but I'm in the final stages of another book project at the
moment so I've put it off until that one is complete. Luckily, if
you're familiar with the Qt3 version, jumping into the Qt4 version
isn't too big of a stretch.

Thanks,
Caleb

richard.j.dale@gmail.com

10/31/2006 12:31:00 PM

M. Edward (Ed) Borasky wrote:
> 1. Does all this magic work on Windows?
Yes, once you get it built - I'm not sure whether QtDBus works on
Windows yet but everything else should. Look at the help forum posts on
the Korundum site for info about building on Windows.

> 2. Is it packaged as a gem?
No, it really needs to be. I haven't personally good easy access to a
Windows machine for development, and I'm not particularly familiar with
the development environment either. Sooner or later I hope there will
be a binary gem for Windows..

Shea Martin

11/8/2006 2:14:00 PM

David Vallner wrote:
> M. Edward (Ed) Borasky wrote:
>> Awesome!! Questions:
>>
>> 1. Does all this magic work on Windows?
>> 2. Is it packaged as a gem?
>>
>
> Seconded, mswin32 gem or bust. I'm not particularly in the mood for
> polluting my machine with things related to compiling C, I sure as hell
> don't have the presence of mind to keep results thereof between the
> inevitable full reinstalls, and that it's overall a Good Thing for use
> outside personal code I don't need to remember.

I will second that. I would love to use ruby and qt together. But my
apps are multi-platform, and I can't assume that people who use windows
will already have Qt installed. If there was a simple way to get the
minimum amount of Qt binaries installed for them, then I would do it for
them.

~S

Shea Martin

11/8/2006 2:45:00 PM

Shea Martin wrote:
> David Vallner wrote:
>> M. Edward (Ed) Borasky wrote:
>>> Awesome!! Questions:
>>>
>>> 1. Does all this magic work on Windows?
>>> 2. Is it packaged as a gem?
>>>
>>
>> Seconded, mswin32 gem or bust. I'm not particularly in the mood for
>> polluting my machine with things related to compiling C, I sure as hell
>> don't have the presence of mind to keep results thereof between the
>> inevitable full reinstalls, and that it's overall a Good Thing for use
>> outside personal code I don't need to remember.
>
> I will second that. I would love to use ruby and qt together. But my
> apps are multi-platform, and I can't assume that people who use windows
> will already have Qt installed. If there was a simple way to get the
> minimum amount of Qt binaries installed for them, then I would do it for
> them.
>
> ~S

What are the legal issues of creating a rubygem for Qt (which included
necessary .so/.dll's)? I am starting a GUI project in about a month,
and am trying to decide whether to go with wx or qt. The fact that
there is a wx gem, makes it sooo much easier for people to install my app.

I guess I am just trying to gauge the chances of a qt ruby gem being built?

Thanks,

~S

Vincent Fourmond

11/8/2006 3:07:00 PM

Shea Martin wrote:
> What are the legal issues of creating a rubygem for Qt (which included
> necessary .so/.dll's)? I am starting a GUI project in about a month,
> and am trying to decide whether to go with wx or qt. The fact that
> there is a wx gem, makes it sooo much easier for people to install my app.

Qt4 and QtRuby are GPL, which means that if you distribute you project
to anyone, you'll need to do so under GPL -- so you'll have to make
OpenSource software. If that doesn't bother you, that's all the legal
problems you'll have. It also applies to any Qt rubygem.

> I guess I am just trying to gauge the chances of a qt ruby gem being built?

If I understood right, you're looking for a gem that would also
include Qt4 libraries, is it right ? There would be no legal problem in
distributing it, but I think it will be rather tricky to make. I hope
I'm wrong.

Vince

--
Vincent Fourmond, PhD student
http://vincent.fourmon...

comp.lang.ruby

[ANN] QtRuby 1.4.7

richard.j.dale@gmail.com

M. Edward (Ed) Borasky

Pau Garcia i Quiles

Vincent Fourmond

David Vallner

richard.j.dale@gmail.com

Caleb Tennis

richard.j.dale@gmail.com

Shea Martin

Shea Martin

Vincent Fourmond

x Login to ForumsZone