similar to: wxruby-swig 0.0.10 released

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

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

I just checked in several changes from Sean Long that should make wxruby-swig work with wx 2.6 as well as 2.5. I also committed his changes to extconf.rb. But could someone please explain to me why anyone would prefer to use extconf.rb instead of rake? It just seems like one more piece of code to maintain, and I don''t like extra code. Sean: The other diffs in the patch you sent were

Was trying to understand more about the internals of wxruby-swig, where does the big chunk of XML comes from? I saw something similiar in Python, is that massaged out of there? The codes produced by extractxml.rb and wxclasses-2.4.2.xml is quite different from the original header files. Just for example the WxDialog class. OnXXX are non-virtual in WxWidgets, but virtual in wxruby-swig

Tonight, I generated a full set of almost 400 swiggable .h files, one for each wxWidgets class. I used the big xml file that I mentioned earlier, which itself was (apparently) scraped from the wxWidgets html help files. Several interesting notes: 1. REXML took forever to parse the 2.5 meg xml file. I didn''t want to do stream processing, and hoped to stay with a pure-ruby solution,

I just pushed a new wxruby-swig, which includes the known MSWin rakefile changes. It also has some significant internal improvements that will make it easier to add classes, and it includes support for one new class (wxEvent). wxruby-swig is now licensed under the "MIT license". wxRuby will remain under the wxWindows license as long as we are releasing the old code base. When we

Hey everybody, I''ve made some progress on wxruby-swig, and have some good news and some bad news. The good news is that the MSVC version finally can run all of the samples provided in CVS. I''m using the same solve-by-ignore solution to the GC problem that wxruby uses, so there is far less crashing goin'' on. Depending on the next few weeks, we might be able to

Since I''m setting up my development environment on a new system, I figure now is the time to get rid of one of the extra dependencies: NQXML. It appears that REXML can now parse the whole classes xml file in about 20 seconds on this machine, which is a huge improvement over the many, many minutes it used to take. So I am now updating extract.rb to use REXML instead of NQXML.

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

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

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

This fixes the crash-on-exit for nothing.rb and minimal.rb. We still have a problem with calendar.rb. I had to modify the swig source code to get this part of my memory management to work. Hopefully the swig folks will incorporate my change in the main code line so I won''t be stuck maintaining a swig fork forever. The change I made was to force swig to create a "director"

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

Bugs item #6809, was opened at 2006-11-21 22:05 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=218&aid=6809&group_id=35 Category: Incorrect behavior Group: None Status: Open Resolution: None Priority: 4 Submitted By: Alex Fenton (brokentoy) Assigned to: Kevin Smith (qualitycode) Summary: Weird SWIG error when constructing statusbar Initial Comment: A

More progress on wxruby-swig. Nothing too exciting. It now support 36 classes, compared to the (apparently) 139 supported by wxRuby 0.3. A working version of the calendar sample is included. I made several changes to the sample. I have tentatively decided *not* to wrap the wxDateTime class, and instead to automatically convert to/from Ruby''s own DateTime class. My logic is that in

I just grabbed the latest wxruby-swig from cvs and tried to compile it (without enabling the SWIG step) on my gentoo Linux box. I get: g++ -c -I/usr/lib/wx/include/gtk2-2.4 -DGTK_NO_CHECK_CASTS -D__WXGTK__ -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -O2 -march=athlon-xp -fPIC -I /usr/lib/ruby/gems/1.8/gems/rake-0.4.8/bin -I /usr/lib/ruby/gems/1.8/gems/rake-0.4.8/lib -I

In trying to add wxTextCtrl to wxruby-swig, I''ve been running into a problem with the argument conversion that appears to be a SWIG director bug. It is tied to multiple inheritance, and is related to SWIG specifically making director''s ''initialize'' take a first argument, but because ''initialize'' is static there isn''t a self value

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

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)

At each step, I think I am past most of the big hurdles. At each step, I find another one. I''m sharing these development stories on the list for a few reasons: 1. Perhaps some of you will find the stories interesting 2. To preserve my lessons in the list archives so I, or someone else, can (re)learn from them later 3. As a record of tangible progress 4. To vent some frustration