similar to: Making it easier to contribute wxRuby-SWIG code

Hi Everyone, Over the past couple of weeks wxruby-swig has made a lot of progress. Over 100 classes have been added with attempts to mimic the existing wxruby interfaces. While still not as stable as wxruby, stability has increased dramatically. Finally, it has been built on Linux, Mac, and MSVC. This email is an invitation to try out wxruby-swig for yourself. The source code is in CVS and

The result of the compilation after installing swig results in lots of errors of the sort: WindowDisabler.obj : error LNK2001: unresolved external symbol _SWIG_Ruby_ConvertPtr I can see this is defined in rubydef.swg but I''m not sure why this isn''t just included in the files that need it. Can any swig experts tell me what I need to do to progress? I''m using

If wxRuby-SWIG is as usable as wxRuby 0.6.0, maybe it should be given a version number and packaged up for download. Given the nature of SWIG, having a lot more people use it would probably result in more code contributions to this project. Seems most of the changes are 2+ months old, so I''m guessing wxRuby-SWIG is fairly stable right now in terms of frequency of changes...

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

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

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

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

Hi, my first post here so a little background first... I started out using wxRuby-0.6.0 about 4 months ago while trying to get a grip on Ruby as a means of writing a little budgetting app I''ve been meaning to write for a couple of years. As I didn''t like the way that the wxruby examples are coded (having to punch the individual C++ api methods that way isn''t nice) I

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

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

Good news and bad news. First he good news. wxruby-swig now compiles on Linux, Mac, and Windows using wxWidgets 2.5. I just patched a bug with the paint method today, but it''s getting very close to the first release of wxruby. With a little more cleanup, I think we''re getting ready to do a first release of it, which will hopefully replaced wxruby. Of course, the debug spew

Sorry for the lameness, but I need things explained to me very slowly... -----Original Message----- Subject: RE: [Wxruby-users] wxGrid Question > > Yes, grab the latest tarball from the above location. Then, you should > install rubygems if you haven''t already: > http://rubyforge.org/projects/rubygems/ > > That should allow you to easily install rake: >

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

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

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

I''ve checked a number of new .i files into the wxruby-swig tree. Not all of them are fully tested, but I thought it would be better for them to be there than to have somebody start duplicating the work. I''ve also added the ''caret'' and ''image'' samples, as well as the generic etc/test.rb. These need the unreleased SWIG-1.3.22. The current

It has been a frustrating couple days. I have been tracking down the bug where any wxruby-swig app will crash/segfault upon exit. Yesterday, I fixed the problem where the App object was being freed twice. Today, after several hours of debugging, I discovered that the Frame object is also being deleted twice (for a different reason). I have asked Lyle Johnson for some guidance, because it is

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

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,

Nick wrote: > > I''m assuming you''ve installed ruby 1.8 over the Mac default? Yep, I installed 1.8 over the Debian default. I''m running Debian Linux atm, my Mac box is the next in line for me to get going. Zach > > Nick > > Zach Dennis wrote: > >> Nick wrote: >> >>> >>> What version of Swig do you have? Make sure it