similar to: New tutorial added!

Ok. I seem to be having some real problems today :) There is a link from the main page straight to the Wx::Frame tutorial, under the NEWS section. http://wxruby.rubyforge.org/wiki/wiki.pl Sorry for wasting everyone''s time :( Robert _________________________________________________________________ Getting married? Find tips, tools and the latest trends at MSN Life Events.

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/

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

0.0.5 sure gets the Mac build a lot further. There''s a bug in the wxMac-2.4.2 distribution that I''m running into: wx-config wants to invoke a program in the source directory at link time. That''s ugly in itself, but it tries to use a variable ${top_srcdir} to accomplish this, and it''s apparently empty. It tries to invoke

Grabbed 0.0.16 and tried a build for kicks. ...all good, except for a warning in MenuBar.cpp, then... g++ -c -I/usr/local/lib/wx/include/mac-2.4 -D__WXMAC__ -DWXMAKINGDLL -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -fno-common -fno-common -pipe -fno-common -x objective-c++ -I /usr/local/lib/ruby/gems/1.8/rake-0.3.2/lib -I /usr/local/lib/ruby/site_ruby/1.8 -I

Looks like the Wiki got spammed. Dan

It is becoming clear to me that the swig version of wxRuby will not be ready within the next several weeks[1]. Therefore, I think we should do a 0.4.0 release based on the existing source code. Hopefully this will be the final non-swig-based version. My goal is to have it ready within the next week or so. It will fix a few bugs discovered after the 0.3.0 release, and will include several

The only changes are Nick''s Mac fixes to the rakefile and App.i. This might be "the one" for Macs. Kevin

This fixes the wxRED Mac link error. Thanks to Nick for pointing out that I hadn''t removed some wxRED code related to an earlier experiment. Hopefully this one will build on Mac, end-to-end. I also found and fixed a problem that was causing the crash on exit: wxWindows automatically deletes the C++ app object as soon as the last frame is closed. Later, when ruby garbage collected the

I have a minimal working version of a SWIG-based wxRuby that can bring up an empty Frame with a title. On my system, it crashes on exit. I suspect this is the same problem that I mentioned months ago when I first upgraded to wxWindows 2.4.2. The problem mysteriously vanished at some point, but now it is back. I fiddled with this new code for several frustrating hours, and couldn''t

Has anybody tried the new wxruby-swig from the msvc++ command line compiler using ''rake''? The rakefile seems to depend on the wx_config method, which doesn''t exist for msw because it doesn''t have BASH to execute the shell script. Has anyone hacked the rakefile to fix this? Nick

I''ve only had the briefest play with wxSugar and already I like it a lot. One small question - have you considered some more ''convention over configuration'' like they do in rails, in particular for event connectors? So instead of listen(:button, my_button, my_button_pressed) you can leave it out entirely and rely on the convention that a button has a _pressed

=begin I am trying to understand how FlexGridSizer works and I have written a small test application using the latest wxRuby 0.4.0 on Win XP (Home). I cannot get static text ''Week'', ''Day'' and ''Date'' line up above the OK button. I have tried all combinations of ALIGN flags, but I either got the text sticking far too close to the left edge of

Really stupid question, but have you wrapped this all in an App class? If you don''t have a wxApp subclass driving your applications then all sorts of badness would happen. > I''m writing a custom little application for my boss''s high school > football team to track there stats play by play. > > My problem is that when I start the application, it

Hey Kevin, Am I correct in assuming that if I want a particular widget to respond to an event which doesn''t take an ID as an argument (like evt_size or evt_left_down), that I have to inherit a new widget and define the event handler within the inherited class? Here''s a little contrived code example to illustrate what I mean: class MyCtrl < Wx::TextCtrl def

Hi Do a search on ''wxruby'' and you''ll see that people''s main gripes are 1) stability 2) development progress 3) documentation and 4) syntax. We''re making great progress on 1-3 so thought it seemed like a good time to start looking at 4). So here''s announcing a first release of WxSugar. It can be downloaded via gems (gem install wx_sugar)

Hi all, Ruby 1.8.1 Solaris 9 wxwindows 2.4.2 (package from blastwave.org) wxruby 0.3.0 I''m having trouble getting this sucker to build on my Solaris box. Here''s how I''m building: ruby extconf.rb --with-xrc-dir=/opt/csw --with-xrc-include=/opt/csw/lib/wx The include directive I added because the setup.h file is there (for whatever reason). And yes, /opt/csw/bin and

Hi I''m trying to follow the tutorial on xrcise at http://wxruby.rubyforge.org/wiki/wiki.pl?UsingXRCise But I keep getting the following error when I try to run the example; tutorial.rb:21:in `initialize'': undefined method ''upper_bt'' for #<CaseChangeFrame:0x2d610f8> (NoMethodError) from tutorial.rb:28:in `new'' from

Dear all, I have a problem with the function read.xls from the gdata package, error message see below. Two examples: First, I try to read my data, which does not work; Secondly, I tried the example code/data with the Iris data, which worked Any idea? Thanks, Lars > path<-"I:/subProjects/bh/HPGD/" > > setwd(path) > > xls <- "Platten_Liste_090421.xls"

Hi Given the warm response to the syntax additions in 1.9.1 I''m considering moving one or two more syntax extensions into core, and would like your thoughts. Last ones, I promise. Realise we don''t want much more API change now, but also we''ll probably also have to live with whatever we settle on for 2.0 for a little while, so... 1) Setting up event handlers In