similar to: Re: FW: problems installing wxruby

Hi wxRuby gurus, I remember a while back, Zach Dennis was working on a mini Spreadsheet app using wxGrid when the issue of lack of wxGrid event handling was discussed. I think Kevin (or Assaph?) had suggested some workarounds until the Swig based version is out. Could not figure out from the archives exactly what the final resolution was, but I am stuck at the same spot and am desperately in need

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.

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

Kevin, were you planning to do a linux tarball or RPM for 0.3 before focusing on the SWIG version? I think its important for many obvious reasons, but I''ll just mention the one that prompted me to write this email. In the long term, I''d like to see wxRuby become the standard GUI toolkit for ruby, and I am simultaneously working several fronts to help make that happen. My

wxRuby 0.4.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 Panther and MS Windows. Please report any bugs or feature requests here: http://rubyforge.org/tracker/?group_id=35 Changes in this release include: * Many bugs were fixed. * Added grid sample program. * Windows binary now includes

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

Last week I was struggling to get xrc built into wxRuby and finally got it to compile. The problem I am now having is that the normal samples are not working at all (have not even tried any xrc stuff yet). So to test if it is a problem with xrc or my build process I tried compiling wxRuby without XRC, this caused the same error to be printed out as the failed XRC build. The output (in both

I''m just trying to plan out my week, and I wanted to see how everyone felt about a 0.5.0 release of wxRuby (not wxruby-swig). Are we ready for this? If not, what remains to be done? Curt

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

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,

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

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

wxRuby 0.3.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 Panther and MS Windows. Hopefully, within a couple weeks I will release RubyGems for the source, and RubyGem binaries for Mac, Windows, and Linux. Please report any bugs or feature requests here:

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

I think so (especially if you build from source), but I''m not 100% sure. I''ll forward this to the wxRuby user''s ML -- Kevin Smith probably knows. Curt > -----Original Message----- > From: Wayne Magor [mailto:wemagor@hotmail.com] > Sent: Thursday, April 15, 2004 12:19 AM > To: ruby-talk ML > Subject: wxRuby and Unicode > > > Is it possible to

A few days ago, someone asked me why I am using wxpp instead of SWIG. The question prompted me to revisit and re-evaluate SWIG, and I now believe it would be best to convert wxRuby to SWIG. SWIG has greatly improved its C++ support since the last time I looked at it, and I think its Ruby support has improved quite a bit as well. Also, now that I have written wxpp, I understand the nature of

I''m fairly new to the Ruby world, particularly WxRuby, so please forgive me if this is ground that''s been covered in the past. I''m trying to load a frame from an XRC file (created using DialogBlocks), and I''m having trouble getting an instance of the Gauge object using the Wx::Window.find_window_by_xxx methods. I''m trying this on Windows XP,

Any chance of incrementing the ol'' version number a bit more aggressively? Doing so could really help wxRuby adoption if done right: http://fishbowl.pastiche.org/2003/07/28/version_numbers_and_you -- Ryan "John" Platte Custom services, NIKA Consulting http://nikaconsulting.com/

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

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.