search for: how_to_add_a_new_class_to_wxruby

...pplications. We''ve been testing with the existing samples, but I know those of you out there have a lot more abusive tests! For people interested in assisting with wxruby-swig development, there is a Wiki page that describes the process at: http://wxruby.rubyforge.org/wiki/wiki.pl?How_To_Add_A_New_Class_To_Wxruby-Swig This goes through setting up the build environment and a number of pitfalls. I''d like to hear about what works and what does not. I appreciate any time you can put into this. Any contribution only makes wxruby that much better. Nick

After seeing contributions from Dmitry and Alex, I''m wondering how we can better organize and encourage user contributions. ORGANIZING Maybe identifying what is still missing in wxRuby-SWIG and publishing a prioritized todo list could useful to contributors. GETTING NOTICED It might be useful to post a link to the unassigned todo list each month to comp.lang.ruby and ask for

The CVS module has been renamed from wxruby-swig to wxruby2, and I have checked in the related changes to reflect the name change. Anyone with a CVS tree will need to re-checkout from CVS because of the module name change. There is now a wx.rb in the lib/ directory, which loads the wxruby2 shared library that gets built. I have tagged this as 0.0.22. Next steps: - Apply Choice.i patch from