similar to: Hello, new developer here. (for Bryan Green)

Jeremy Stell-Smith wrote: > Thanks a lot for the help, guys. I''m up and running with 2.4.2, but I > did have a few questions. Excellent. > So first, a friend and I basically have this month to dedicate to trying > to get a ruby ide pilot built on top of wxRuby. So, no, I really can''t > wait a few weeks to start. Any chance you could commit changes into cvs

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

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/

I thought that the list of top RubyForge downloads was interesting: (6,992) Ruby Release Mirror (2,539) Win32 Utils (1,994) FreeRIDE (1,569) RMagick (1,470) AEditor (1,418) wxRuby In looking at this, I discard the top two entries -- the first because that''s Ruby itself, and the second because Win32 Utils is broken up into *lots* of packages that are downloaded separately and this skews

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

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

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

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.

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

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

Jeremy Stell-Smith wrote: > > actually... > > the mac distro only includes the mac readme, and doesn''t say > anything about > wxwindows/widgets at all, except for where to get it > > the source distro in the main readme says that it works with wxWidgets OR > wxWindows 2.4.x Probably a wording error that snuck in when trying to accomodate the name change to

Curt Hibbs wrote: > Kevin Smith wrote: >>On the other hand, I do not want wxRuby to get a bad reputation. Perhaps >>it is worth fixing them, and releasing a 0.4 (or 0.3.1). > > I guess this really hinges on when "reasonably soon" is likely to be. Are we > talking a month? two months? four months? Good question. I should have a better idea by the end of this

I guess this is mostly for Curt, but I wanted to toss it out there. I could really use a wiki to capture the information that gets posted to this list. Eventually we''ll want FAQ''s and HOWTO''s, as well as a "real" manual, and the wiki is great for collecting raw material. Also, we should have links to related projects, like wxrbbr, and projects written in

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

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

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

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:

Roy Sutton wrote (on the FreeRIDE list): > Really? That''s interesting. I haven''t checked out WxRuby but I would > be much happier using something that interfaces to the underlying > operating system''s widgets. As a member (and former leader) of the wxruby team, I thought I would share the state of the wxruby world. The current release is 0.6, and it has

Greetings all, Sadly, I must announce my "retirement" as the wxruby project leader. I still believe in the project, and really want it to succeed. Unfortunately, there are other projects that are higher priority for me right now. I cannot be an effective wxruby lead at this time. Perhaps at some point in the future, wxruby will again become a top priority for me. If that happens,