Notes:
There is something messed up with RubyForge, in
that it always gives you the wrong release of qt4
qruby by renaming the tar balls. If it untars into 'qt4-qtruby-1.4.0' then it's happened yet
again..
A first release of the Qt4 version of QtRuby, now free of any unsermake dependencies. Needs Qt 4.x and automake/autoconf.
Changes:
First release, copied from the KDE svn without KDE4 dependencies. Recent ChangeLog entries:
2006-01-19 Richard Dale <Richard_Dale@tipitina.demon.co.uk>
* Improved the debug logging of virtual method callbacks so that the
arg types are shown too
2005-12-20 Richard Dale <Richard_Dale@tipitina.demon.co.uk>
* Restored Caleb Tennis's refactored marshall_types.cpp code after
accidently deleting it in August.
2005-12-16 Richard Dale <Richard_Dale@tipitina.demon.co.uk>
* The logger_backend() function has been removed and replaced with
qWarning() calls. This was because of problems with getting the
logger_backend() code to work on Windows.
2005-12-08 Richard Dale <Richard_Dale@tipitina.demon.co.uk>
* The ruby display() method was clashing with a display() method in some
QtRuby classes, and so it was aliased to _display(). However, this caused
problems with the ruby RMagick extension. The display methods are now
special cased in Qt::LCDNumber. Fixes problem reported by David Corbin.
* The slots and signals methods are now module methods of Qt::Base,
rather than defined as ordinary methods in class Module, reducing name
space pollution. Thanks to Esteban Manchado for pointing this out.
2005-12-06 Richard Dale <Richard_Dale@tipitina.demon.co.uk>
* QtRuby didn't work with versions of ruby > 1.8.3, as it didn't call
initialize methods correctly. It used the rb_respond_to() method
to check it a newly created qt instance responded to :initialize.
However, in newer versions of ruby rb_responds_to() ignores
private methods such as initialize(). The solution was to just remove
the test, as it was redundant anyway.
* Fixes problem reported by Hans Fugel and Caleb Tennis.
|
