similar to: Plans for wxRuby 0.4.0

Grabbed 0.0.16 and tried a build for kicks. ...all good, except for a warning in MenuBar.cpp, then... g++ -c -I/usr/local/lib/wx/include/mac-2.4 -D__WXMAC__ -DWXMAKINGDLL -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -fno-common -fno-common -pipe -fno-common -x objective-c++ -I /usr/local/lib/ruby/gems/1.8/rake-0.3.2/lib -I /usr/local/lib/ruby/site_ruby/1.8 -I

This one includes the latest App.cpp which includes the Mac fix from Nick. I thought it was in 0.0.11, but it wasn''t. It also adds support for "stock objects", like colours, pens, and fonts. This turned out to be quite challenging, but I''m happy with the solution. It only took a few days :-/ Kevin

0.0.5 sure gets the Mac build a lot further. There''s a bug in the wxMac-2.4.2 distribution that I''m running into: wx-config wants to invoke a program in the source directory at link time. That''s ugly in itself, but it tries to use a variable ${top_srcdir} to accomplish this, and it''s apparently empty. It tries to invoke

Any chance of incrementing the ol'' version number a bit more aggressively? Doing so could really help wxRuby adoption if done right: http://fishbowl.pastiche.org/2003/07/28/version_numbers_and_you -- Ryan "John" Platte Custom services, NIKA Consulting http://nikaconsulting.com/

I have a minimal working version of a SWIG-based wxRuby that can bring up an empty Frame with a title. On my system, it crashes on exit. I suspect this is the same problem that I mentioned months ago when I first upgraded to wxWindows 2.4.2. The problem mysteriously vanished at some point, but now it is back. I fiddled with this new code for several frustrating hours, and couldn''t

The only changes are Nick''s Mac fixes to the rakefile and App.i. This might be "the one" for Macs. Kevin

Ok. I seem to be having some real problems today :) There is a link from the main page straight to the Wx::Frame tutorial, under the NEWS section. http://wxruby.rubyforge.org/wiki/wiki.pl Sorry for wasting everyone''s time :( Robert _________________________________________________________________ Getting married? Find tips, tools and the latest trends at MSN Life Events.

This fixes the wxRED Mac link error. Thanks to Nick for pointing out that I hadn''t removed some wxRED code related to an earlier experiment. Hopefully this one will build on Mac, end-to-end. I also found and fixed a problem that was causing the crash on exit: wxWindows automatically deletes the C++ app object as soon as the last frame is closed. Later, when ruby garbage collected the

Hey guys, It''s been awhile, but I''ve put up a new tutorial page on Wx::Frame. It''s the first half of the tutorial on Frame, the rest will come a little later. Let me know what you guys think. Any comments or criticisms are welcome. Let me know what was good and what could have been better, so that future tutorials will be able to incorporate those improvements.

Has anybody tried the new wxruby-swig from the msvc++ command line compiler using ''rake''? The rakefile seems to depend on the wx_config method, which doesn''t exist for msw because it doesn''t have BASH to execute the shell script. Has anyone hacked the rakefile to fix this? Nick

Looks like the Wiki got spammed. Dan

Hi all, Ruby 1.8.1 Solaris 9 wxwindows 2.4.2 (package from blastwave.org) wxruby 0.3.0 I''m having trouble getting this sucker to build on my Solaris box. Here''s how I''m building: ruby extconf.rb --with-xrc-dir=/opt/csw --with-xrc-include=/opt/csw/lib/wx The include directive I added because the setup.h file is there (for whatever reason). And yes, /opt/csw/bin and

I just checked in some good fixes. You can see the (full) Changelog here: http://qualitycode.com/repos/wxruby/ChangeLog Notable items: - Added shanko''s grid sample (thanks!) - Added support for ComboBox#get_value - Fixed *all* the known crashing bugs. The way I "fixed" the problems with get_client_data was to remove the set_client_data and get_client_data implementations. I

REMINDER: This news is about the swig-based prototype. The main wxRuby release is still current at 0.3.0. I just pushed the latest wxruby-swig code to: http://qualitycode.com/repos/wxruby-swig Thanks to Nick for reminding me about the Window#paint method that wxRuby 0.3 supports. I had forgotten all about it. There may be other features that we manually added to wxRuby that I will need to

Hi everyone, As Kevin has just announced, wxruby-swig has been moved into CVS as a toplevel project. It still is not in a "releasable" form yet, but it now builds on more systems than it doesn''t, and is moving towards stability. Because of the complexity of the build environment, we''re using rake (http://rake.rubyforge.org) as a build system instead of the standard

Greetings all, Over the last few months, while I have been busy on other projects, Nick and other folks have built wxruby-swig up to where it now supports about 120 classes, compared to the 139 in wxruby 0.6. When you include the fact that wxruby 0.6 had a few classes that really weren''t needed (because non-wx ruby versions work fine), it looks like wxruby-swig is actually very

REMINDER: wxruby-swig is an experimental rewrite of wxRuby, using SWIG. It is not yet useful. The official wxRuby is still at 0.2.1. The 0.0.3 release of wxruby-swig is able to run the "minimal.rb" sample, which includes menu event handling. As always, it is available at: http://qualitycode.com/repos/wxruby-swig/ I also created a tarball this time, so you can just download that and

Greetings, I wanted to give you all a progress report on wxruby-swig, the next generation of wxruby. As most of you know, we are in the process of rewriting wxruby from scratch, using SWIG instead of the custom wxpp template tool in the current version. Using SWIG will make it easier for more people to add support for new classes and methods, and will make it easier to optimize (and fix)

In case you missed the earlier thread, I am exploring using SWIG as part of the wxRuby build process. So far, wxruby-swig is purely experimental, and supports almost no wx classes or methods. I just pushed wxruby-swig 0.0.2 up to my public darcs repo: http://qualitycode.com/repos/wxruby-swig/ As always, you can use wget if you don''t have darcs. If you really need a tarball

since http://nqxml.sourceforge.net/ also recommends that we switch to use rexml which is shipped with ruby? If there are plans for it but no developers, I might take it up as an exercise to learn the internals of wxruby-swig. Cheers, Phuah Yee Keat