similar to: SWIG Bug

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.

Hi, Are there any effort in making wxDocument, wxView, etc types of classes avaiable under wxRuby? For supporting SDI/MDI architecture. Cheers, Phuah Yee Keat

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 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

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

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

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 have recently started to use wxRuby, because I have used the wxWidgets library from C++ for a few years and found it an excellent toolkit. I am using Ubuntu 8.04 and version 1.9.6 of wxRuby. A problem though is a number of instabilities. This may be due to my own ignorance, but I have usually found C++/wxWidgets, once the program compiles it will at least stay working, if at times

A history question - why was wxSocket wrapped into wxruby? Since Ruby already has a pretty robust networking API, I can''t see the purpose. I''m debating on if it belongs in wxruby-swig, and right now the only vote in its favor is "it was in the old version." Nick

Hi Think I tracked down why Windows suddenly went horrible crashy - the newest SWIG release generates slightly different code for object tracking, so our fixmodule.rb wasn''t picking up the broken line, so we got a nasty regression. Anyway, the patch (SVN:862) gives me a major improvement in stability Windows. Please could you let me know how SVN HEAD is working for you; if no major

I couldn''t find the original tex document that the author of the xml file converted from. Anyone knows where it is? I am toying with the idea of _not using_ the xml file. Either getting the wx header files thru SWIG (I assume you guys have thought about this before already, any specific problems?), or continue with the template generator in the current wxruby-4.0. The RUBY port of

I decided to try my hand at hacking SWIG and successfully produced a patch that fixes the error I demonstrated. I''m not -positive- it''s correct for all cases but I''ll re-run my version of SWIG over the library and see how things turn out. Roy

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

I just re-integrated fixdeleting.rb, the last of the post-processors. Running minimal.rb no longer segfaults on exit. Running dialogs.rb and immediately exiting doesn''t segfault, but bringing up a dialog and then exiting does. So there are still memory problems, but fewer than yesterday :-/ I''m not sure how it compares to last week. I probably won''t have much time

When operating with a wxGrid is there a way to get a reference to the TextCtrl field that is created when you start typing in a cell. Also is there a way to get mouse events to work with a wxGrid, so far I can''t get any of them to work. I had tried various combo''s of: @grid.evt_left_down(){ |event| puts "Left mouse is down"; } using evt_left_down, evt_left_up,

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

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

I have a minimal working version of a SWIG-based wxRuby that can bring up an empty Frame with a title. On my system, it crashes on exit. I suspect this is the same problem that I mentioned months ago when I first upgraded to wxWindows 2.4.2. The problem mysteriously vanished at some point, but now it is back. I fiddled with this new code for several frustrating hours, and couldn''t

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