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) memory usage.
Until recently, I have been doing all the wxruby-swig development
myself, using darcs for version control. All of that is changing now. We
have created a new top-level CVS module at rubyforge, named wxruby-swig.
Eventually we will rename the current wxruby module to be wxruby-legacy,
and will rename wxruby-swig to be wxruby.
Nick now has CVS access, and has been working on getting wxruby-swig to
compile under MS-Windows. It already works under Linux and Mac. I don''t
have an MS-Windows box myself, but I understand there are still some
run-time problems under MS-Windows, which Nick can address.
Hopefully between Nick''s efforts, and the fact that I am just now
starting to recover from moving, we will be able to start making more
progress on wxruby-swig. As soon as it supports everything that wxruby
0.4.0 supports, it will become the official wxruby.
We could use help supporting more classes. In many cases, doing so does
not require any C++ skills at all. In many other cases, some methods can
be added without C++ knowlege, and the other methods can be commented
out. If you are interested in helping, the first step is to download and
build wxruby-swig. Then, please contact me (on or off list) so we can
coordinate work and avoid duplicating effort. Assuming a few people are
interested, I can write up a HOWTO that explains the process.
Thanks,
Kevin
