[ANN] FXRuby-1.0.14 Now Available

I am pleased to announce the latest release of FXRuby, the Ruby language
bindings for the FOX GUI toolkit. FOX is a C+±based toolkit for developing
graphical user interfaces easily and effectively. It offers a wide, and
growing, collection of widgets, and provides state-of-the-art facilities
such as drag-and-drop, selection, as well as OpenGL widgets for 3-D
graphical manipulation. FOX also implements icons, images, and
user-convenience features such as status line help and tooltips.

Please see the comments on the home page concerning any problems with this
release, or the change log:

http://www.fxruby.org/doc/changes.html

to see what has changed since the previous release.

The FXRuby home page is here:

http://www.fxruby.org

and the source tarball can be downloaded here:

http://prdownloads.sourceforge.net/fxruby/FXRuby-1.0.14.tar.gz

A binary installer for Windows, compatible with the mswin32-based versions
of Ruby 1.6.7 for Windows, is available for download here:

http://prdownloads.sourceforge.net/fxruby/FXRuby-1.0.14-ruby167.exe

and a Linux RPM (for Ruby 1.6) will soon be available for download here:

http://prdownloads.sourceforge.net/fxruby/FXRuby-1.0.14-1.i386.rpm

Note that this release of FXRuby depends on FOX version 1.0.x, which can be
downloaded from the FOX downloads page here:

http://www.fox-toolkit.org/download.html

Please feel free to send me any questions or comments, and watch this space
for future announcements!

Lyle

Please see the comments on the home page concerning any problems with this
release, or the change log:

http://www.fxruby.org/doc/changes.html

to see what has changed since the previous release.

Awesome, Lyle. Great job as always. (I’ve only looked over
the list of changes, but I’ll download it when I get a
chance.)

I think one thing I’d like to see tackled is the
*_require stuff (or whatever it is) that prevents
FXRuby apps from working with exerb.

FWIW, I’ve tried exerb a few times, and it works
great. The .exe is pretty big, but that’s to be
expected since it embeds the entire Ruby interpreter
and whatever else is needed.

I did try it on a Fox app and it seemed to work
at first (giving me a 7 meg executable, I think)
but of course it failed immeditately at runtime.

Hal

···

----- Original Message -----
From: lyle@knology.net
To: “ruby-talk ML” ruby-talk@ruby-lang.org;
foxgui-announce@lists.sourceforge.net;
foxgui-users@lists.sourceforge.net;
fxruby-announce@lists.sourceforge.net; announce@rubynet.org
Sent: Tuesday, October 15, 2002 3:32 PM
Subject: [ANN] FXRuby-1.0.14 Now Available

The last few versions no longer build for me. I get this:

FXRuby.cpp:258: cannot convert VALUE' to void *’ for argument 1' to rb_gc_mark (void *)’
make: *** [FXRuby.o] Error 1
setup failed
‘system make’ failed
try ‘ruby install.rb --help’ for usage

Any idea what’s going on here?

This is on Ruby 1.6.7, but with the header file mods needed for
compilation.

Ian

···

On Wed 16 Oct 2002 at 05:32:11 +0900, lyle@knology.net wrote:

I am pleased to announce the latest release of FXRuby, the Ruby language
bindings for the FOX GUI toolkit.


Ian Macdonald | Bipolar, adj.: Refers to someone who has
ian@caliban.org | homes in Nome, Alaska, and Buffalo, New
> York.
>
>

The last few versions no longer build for me. I get this:

FXRuby.cpp:258: cannot convert VALUE' to void *’ for
argument 1' to rb_gc_mark (void *)’
make: *** [FXRuby.o] Error 1
setup failed
‘system make’ failed
try ‘ruby install.rb --help’ for usage

Any idea what’s going on here?

This is on Ruby 1.6.7, but with the header file mods needed
for compilation.

The corrected prototype for rb_gc_mark() [from the latest CVS sources
for Ruby 1.6] is:

void rb_gc_mark(VALUE);

and so you should “fix the fix” accordingly. You are absolutely correct
that in FXRuby releases 1.0.12 and earlier, the instructions were to
change the prototype to expect a void* argument, which was consistent
with the implementation of rb_gc_mark() at that time. When this
prototype was “officially” corrected in the Ruby 1.6 sources, I changed
the build instructions accordingly – but I failed to make a big deal
about it in the change history for the 1.0.13 release (my oversight).

I think one thing I’d like to see tackled is the
*_require stuff (or whatever it is) that prevents
FXRuby apps from working with exerb.

I believe this bug was fixed in the latest exerb release (version 2.2.0),
but I can do a quick sanity check tomorrow morning. As I recall, it works
just peachy now. In fact, the author added a new script that automatically
generates the dependencies for your Ruby script so you don’t even have to
write the recipe file (i.e. the *.rbc file) anymore.

FWIW, I’ve tried exerb a few times, and it works
great. The .exe is pretty big, but that’s to be
expected since it embeds the entire Ruby interpreter
and whatever else is needed.

exerb is very, very nice. It “just works” :wink:

I did try it on a Fox app and it seemed to work
at first (giving me a 7 meg executable, I think)
but of course it failed immeditately at runtime.

On the file size, yes, there’s no magic there. The FXRuby extension (the
shared library part) takes up 3 or 4 megs, and the Ruby core adds another
few. It adds up quickly. Of course, the FXRuby that I put in my installer
statically links in all of the optional bells and whistles (e.g.
FXScintilla, JPEG, PNG and TIFF support) and so you’re paying a price for
those goodies. If one were to build a “lighter” FXRuby, it might shrink the
size a bit (but maybe not enough to make it worthwhile).

I think one thing I’d like to see tackled is the
*_require stuff (or whatever it is) that prevents
FXRuby apps from working with exerb.

I believe this bug was fixed in the latest exerb release (version 2.2.0),
but I can do a quick sanity check tomorrow morning. As I recall, it works
just peachy now. In fact, the author added a new script that automatically
generates the dependencies for your Ruby script so you don’t even have to
write the recipe file (i.e. the *.rbc file) anymore.

Oh, pardon me. I thought this was a limitation
in the way FXRuby was written.

I’ve tried the dependency generation. Yes, that’s
cool. Especially when tabs are required. I had
some difficulty with .rbc files initially. :slight_smile:

I’ll try this in a day or so.

Thanks,
Hal

···

----- Original Message -----
From: “Lyle Johnson” lyle@knology.net
Newsgroups: comp.lang.ruby
To: “ruby-talk ML” ruby-talk@ruby-lang.org
Sent: Tuesday, October 15, 2002 10:22 PM
Subject: Re: [ANN] FXRuby-1.0.14 Now Available

Thanks. That did the trick.

Ian

···

On Wed 16 Oct 2002 at 11:50:14 +0900, Lyle Johnson wrote:

The corrected prototype for rb_gc_mark() [from the latest CVS sources
for Ruby 1.6] is:

void rb_gc_mark(VALUE);

and so you should “fix the fix” accordingly.


Ian Macdonald | If in doubt, mumble.
ian@caliban.org |
>
>
>