Just a quick update on where we stand.
I was updating the README, and looking at the wiki, and see that there
are only 20 classes that were supported in wxruby 0.6 that are missing
from wxruby2. And most of those are rarely used, and most should be easy
to support. That''s not counting the classes that were intentionally
removed. There are also at least a dozen classes that are supported in
wxruby2 that were never in wxruby 0.6.
There are two "big" problems with the current wxruby2 code:
1. Inheritance. Currently, virtual methods can only be overridden in
ruby if they were defined in the wx class that ruby is extending. If
they were defined in the parent of that class, they behave as if they
were non-virtual.
There is a fairly easy fix for this, but it involves tweaking almost
every swig class file in the system. Hopefully we can complete this
within a week or so.
2. Memory management. Currently, most wxruby2 apps crash on exit, and
some crash even earlier. We believe that any ruby garbage collection
triggers it. The cause is not yet known, but is likely to end up being a
straightforward fix, perhaps in our swig typemaps. It is even possible
that the inheritance problem is causing this memory problem.
Aside from those big issues, wxruby2 is looking very good. With more
samples, better documentation, and binary packaging, we could be ready
for a real release relatively soon (weeks? a couple months?).
Thanks,
Kevin
