similar to: The great MSVC wxruby-swig bug hunt!

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

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

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

wxRuby 0.6.0 has been released and is now available for download from RubyForge at http://wxruby.rubyforge.org/ This release includes binary builds for Max OS X and MS Windows. Changes in this release include: * Additional widget support in XRC (thanks to Marshall Elfstrand) * Addition of wxScrollbar (thanks to Hans Harmon of Pinnacle Technologies Inc) * Addition of wxGrid event handlers (thanks

Hello, All. I`m trying to compile wxruby with wxwidgets 2.6 under windows with latest mingw, but have lot of troubles. wxwidgets and ruby 1.8.2 compiles just fine, examples work pretty well. To make wxruby compile (non-swig, from cvs) i was made some minor changes like explicit cast ("IN2NUM(...)" to "INT2NUM((long) ...)"), removed some constant definitions from const.cpp

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

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

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

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

A while back there was a discussion about what version of WxWidgets to target with WxRuby-SWIG. I don''t remember seeing any resolution, but I gather that thus far WxRuby-SWIG has continued to target 2.4.2, with the thinking that WxRuby-SWIG would quickly mature to the point that it could replace WxRuby, and once that was done the focus would shift to working with 2.5.x.

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

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

Hey Guys, This just came over the rubytalk list. Does anybody have any Debian experience? BTW, one thing this project *really* could use is people to package wxruby for <your distro here>. You don''t need SWIG/C++ experience for it, and a little work could help a lot of people. Nick -------- Original Message -------- Subject: Re: Help a newbie pick a gui tool kit Date: Sun, 13

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

Hi, Has this problem been resolved? I encountered the same problem on my FC3 system with wxGTK-2.4.2 and wxruby-0.6. Thanks. Stephen [Wxruby-users] Re: Problem building wxRuby: htmlproc.h not found *Nick* devel at nicreations.com

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

We''ve had some discussion in the past about the wxruby vs wxruby-swig name, and how they are a bit confusing. My big problem with ''wxruby-swig'' is that unless you know what ''swig'' is, it''s not a terribly useful (or sexy) postfix. It''s like naming a car after it''s manufacturing process - "the all new Acura

I''m trying to build wxruby-swig on windows with the idea of building a windows installer for it. I think that this would go a long way toward encouraging windows developers to try out wxruby-swig. What do you think? Are we far enough along to contemplate a release? Building wxruby-swig on windows is actually going pretty smoothly, but I want to build it with vc++ 7.1 to match the

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