similar to: wxruby-swig 0.0.14 is available

In case you missed the earlier thread, I am exploring using SWIG as part of the wxRuby build process. So far, wxruby-swig is purely experimental, and supports almost no wx classes or methods. I just pushed wxruby-swig 0.0.2 up to my public darcs repo: http://qualitycode.com/repos/wxruby-swig/ As always, you can use wget if you don''t have darcs. If you really need a tarball

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

More progress on wxruby-swig. Nothing too exciting. It now support 36 classes, compared to the (apparently) 139 supported by wxRuby 0.3. A working version of the calendar sample is included. I made several changes to the sample. I have tentatively decided *not* to wrap the wxDateTime class, and instead to automatically convert to/from Ruby''s own DateTime class. My logic is that in

REMINDER: This news is about the swig-based prototype. The main wxRuby release is still current at 0.3.0. I just pushed the latest wxruby-swig code to: http://qualitycode.com/repos/wxruby-swig Thanks to Nick for reminding me about the Window#paint method that wxRuby 0.3 supports. I had forgotten all about it. There may be other features that we manually added to wxRuby that I will need to

This fixes the rakefile to not require NQXML and SWIG, unless you have a WXRUBY_SWIG environment variable set. It also fixes some of the calendar sample errors, but one remains: stock objects (like the color RED) are still not supported. I tried a couple approaches, but none of them will work. I will have to think of something more creative. Kevin

Bugs item #6809, was opened at 2006-11-21 22:05 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=218&aid=6809&group_id=35 Category: Incorrect behavior Group: None Status: Open Resolution: None Priority: 4 Submitted By: Alex Fenton (brokentoy) Assigned to: Kevin Smith (qualitycode) Summary: Weird SWIG error when constructing statusbar Initial Comment: A

At each step, I think I am past most of the big hurdles. At each step, I find another one. I''m sharing these development stories on the list for a few reasons: 1. Perhaps some of you will find the stories interesting 2. To preserve my lessons in the list archives so I, or someone else, can (re)learn from them later 3. As a record of tangible progress 4. To vent some frustration

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

> Great news!! So is the swig-version going to be first released with 2.5 > support? The documentation I''m working on parses the 2.4 xml file. Will > the original parser create a xml file in the same format for 2.5 ? Thankfully, the XML hasn''t changed - I''m using the same file and removing the stripped methods. > I think a while back there was some talk

Patches item #9297, was opened at 2007-03-15 00:46 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=220&aid=9297&group_id=35 Category: None Group: None Status: Open Resolution: None Priority: 3 Submitted By: Nobody (None) Assigned to: Nobody (None) Summary: Patch to compile wxruby 0.0.39 on windows (vc2003,swig 1.3.31,wxwidgets 2.8.0) Initial Comment:

I just checked in some good fixes. You can see the (full) Changelog here: http://qualitycode.com/repos/wxruby/ChangeLog Notable items: - Added shanko''s grid sample (thanks!) - Added support for ComboBox#get_value - Fixed *all* the known crashing bugs. The way I "fixed" the problems with get_client_data was to remove the set_client_data and get_client_data implementations. I

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)

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

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

Feature Requests item #17477, was opened at 2008-01-25 01:57 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=221&aid=17477&group_id=35 Category: None Group: None Status: Open Priority: 3 Submitted By: Nobody (None) Assigned to: Nobody (None) Summary: wxruby fails with SWIG 1.3.33 Initial Comment: Using SourceMage GNU/Linux. Stable recently upgraded to

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

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

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

Bugs item #15225, was opened at 2007-10-31 01:38 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=218&aid=15225&group_id=35 Category: Incorrect behavior Group: current Status: Open Resolution: None Priority: 3 Submitted By: Nobody (None) Assigned to: Nobody (None) Summary: Wx::Region.contains returns an opaque SWIG pointer type Initial Comment: On Windows