search for: wxclasses

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 ShowModal are virtual in WxWidgets, but non-virtual in wxruby-swig I realize that wxruby-swig is in a very highly experimental stage,...

I couldn''t find the original tex document that the author of the xml file converted from. Anyone knows where it is? I am toying with the idea of _not using_ the xml file. Either getting the wx header files thru SWIG (I assume you guys have thought about this before already, any specific problems?), or continue with the template generator in the current wxruby-4.0. The RUBY port of

Hello, wxruby-users. This is an addition which implement wrapper for overloading wxHtmlWindow::OnLinkClicked method. Unfortunately, it was impossible to make it correctly without ugly hack to wxpp.rb, but i`m hope it does not broke it. Please look at attachment for a patch for htmlwindow.t and wxpp.rb and additional file htmllinkinfo.t (need to be added to $objs array in extconf.rb). Sample

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

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

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.