similar to: ruby-lang.org

What do you think about adding a shebang line to the samples so they can be launched on linux/mac like you can on windows? Roy

http://visualwx.altervista.org/ A visual builder for wxWindows that purports to support Ruby. I''ll play with this some and see if I can design projects that work with wxRuby2. Roy

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

SWIG 1.3.29 isn''t going to cut it for us. We''ll have to wait until 1.3.30, unless I can hack together a nasty workaround for a problem with the object tracking. It seem that each SWIG module gets its own hash for tracking objects. This means that, for example, you create a find dialog (in FindReplaceDialog.cpp) events you get from it (from FindDialogEvent.cpp)

Small patch to correct spelling of lemonade. Should ask Sean if he really wanted it to be lemonaid. If not, here''s the patch. On another note... This sample works! Kudos. It is odd that the textbox doesn''t scroll. I suppose I may patch that, too. Roy _______________________________________________ wxruby-users mailing list wxruby-users@rubyforge.org

The latest cvs version of SWIG breaks a few things. I have patched common.i to fix most of it. There will be some other things later that should be compatible with all versions. Can someone test to see if this compiles with the old version? Roy -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: common.i.patch Url:

The ColourDialog (Darn Brits messing up the spellings of perfectly good words!) has a weird behavior. When you first open it you can''t select a color from the ''rainbow'' on the right side until you select a basic color on the left. I don''t think this was the case before we did the big inheritance change. Does anyone else remember if it worked properly

Two patches here: First one removes virtual from a function that shouldn''t have been virtual. Second one applies a typemap to catch GetRectFromChildWindow. For reasons that are completely beyond me the standard ruby OUTPUT typemaps don''t define directorargouts. I will take a stab at patching SWIG''s default typemaps someday so we get this fixed for free on all our

This patch makes Unicode the default build for windows. You can override the default by setting a WXRUBY_NO_UNICODE environment variable. Roy _______________________________________________ wxruby-users mailing list wxruby-users@rubyforge.org http://rubyforge.org/mailman/listinfo/wxruby-users

I was trying to fix the problem with wxImage and the char */unsigned char * thing today and I was going to hand-write the functions to translate between the two. While doing so I decided I''d clean up the SWIG error message to make it more clear. Here''s an example SWIG-generated argument error: in method SetData'', argument 2 of type ''wxImage *''

I might be a bit scarce this weekend -- I managed to score a late ticket to RubyConf! I''ll be in Denver hobnobbing with Matz. :) Roy

We include wx/wx.h in a lot of places. It seems from a (very) cursory examination that the current method is to include wx/wxprec.h. Seems to work fine including wx/wx.h so this may be entirely a non-issue. Does anyone have any feelings on this? Roy

I was fiddling around with wxScintilla tonight and I added it to wxRuby. I haven''t gotten it really nicely integrated since I wanted to make it an optional component. Nicely, wxScintilla was built with SWIG in mind so [most] everything swigged beautifully after a little touch-up. I may fiddle with this some more if you guys think it would be worth adding to wxRuby2. Any thoughts?

Hey guys, I''m really sorry to be so out of touch these days. We just hired two new programmers at work so I''m busy bringing them up to speed...in time for them to help us get a major release out at the end of the year. So my personal goals for wxruby participation at the moment are: 1. Respond to any support requests as quickly as possible 2. Respond to any questions from you

Hi, I am making a game with Ruby/SDL and have run into trouble finding a GUI to cooperate. I have seen numerous examples of wxWindows in combination with SDL (wxPython and PyGame), but have yet to be able to do it in ruby (PyGame example: http://wiki.wxpython.org/index.cgi/IntegratingPyGame). I am not very good with wxRuby as this is my first time using it and thought some more knowledgable users

Hi all, How soon can we do our alpha (binary gem) release? 1. I would like to get the samples working a bit better, but am ok simply documenting most of the current problems. Do the samples crash every few minutes for other people? Or is it just me? I would like to have a copyright/license comment at the top of every sample file before the alpha release. 2. I would like to receive and merge a

Hi Now we''ve got the download problems nailed, shall we do an announcement on comp.lang.ruby? I can do it if you''re really busy, but Kevin I think you have first refusal as you''re owed the biggest chunk of kudos for getting us this far. re patch backlog: no worries - just clearing the decks before having another go at integrating wxScintilla - but I can''t

I think we can mark this bug closed and check in the patch. Anyone have any concerns/questions before I do? Roy -------- Original Message -------- Subject: [ wxruby-Bugs-6144 ] error: cast from ?void*? to ?int? loses precision Date: Sun, 15 Oct 2006 08:37:31 -0400 (EDT) From: <noreply at rubyforge.org> To: noreply at rubyforge.org Bugs item #6144, was opened at 2006-10-15 00:04

This patch fixes background color problems (at least on Windows). It uses the dreaded ''FIXME'' My plan for next weekend is to try building wxPython from the source to see how they manage to achieve several things with SWIG that we''re not (yet) able to. If I''m successful it might lead to wrapping a significant portion of wxWidgets more correctly than

This patch enables the char event and changes the set and kill focus events to be attached to the correct items