similar to: Big question: Move to SWIG?

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

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

I was investigating why the find dialog causes an error when you close it. It seems that wxRuby2 is returning a new ruby object when you call Event.get_dialog. This causes some big problems when you''re expecting you''re going to get back the same ruby pointer that you put in. In a brief check over the source I don''t see anything that preserves the original ruby

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

Hello again, I''m noticing that many of the headers in swig/classes/include have the comment: // This file was automatically generated // by extractxml.rb, part of the wxRuby project // Do not make changes directly to this file! Is this still the case, or was this just a one-time conversion? 228 out of 441 files in that directory don''t have the comment. I ask this because

Hi Attached, patches to implement ListItem. This class, in wxruby 0.6.0, allows styling of individual items in a ListCtrl, via a particularly clunky API. In disambiguating the overloaded ListCtrl#set_item method it introduces one non backwards-compatible change. I''ve followed the WxPython convention as described in the Wx class ref, renaming set_item(index, col, string, imageid) to

About a year ago (ouch!), Robert Carlin submitted a ported version of the wxPython demo/sample. I hoped to include it in wxruby2, but it relies on SplitterWindow, which isn''t in wxruby2 yet. I tried to implement SplitterWindow myself, but got such strange results that I''m thinking I did something wrong. Even though the generated C++ code specified a variable number of

I''ve spent a couple hours tracking through the code and reading Swig documentation to try to find out about tracking C objects back to Ruby objects. It''s not so easy to do. I took at look at wxPython and their source is a mess! I wasn''t able to glean anything from them on how they do it. My current hypothesis is to trap SWIG_NewPointerObj calls and build a map.

Hello, wxruby-users. I`m noticed huge GDI resources leakage when working with my programs (on windows). Fortunately, i simple fix this by calling ''delete'' on wxBitmap object (patch bellow). But i`m wondering -- why there are no calls to destructors of wrapped wxwidgets objects in wxruby? Is there some problems? This is a patch:

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.

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

Wow. Look what SWIG does to GetTextExtent in Grid.cpp: void SwigDirector_wxGrid::GetTextExtent(wxString const &string, int *x, int *y, int *descent, int *externalLeading, wxFont const *font) const { ... if (swig_get_up()) { wxWindow::GetTextExtent(string,x,y,descent,externalLeading,font); return; } obj0 = rb_str_new2((const char *)(&string)->mb_str());

Hey Guys, This just came over the rubytalk list. Does anybody have any Debian experience? BTW, one thing this project *really* could use is people to package wxruby for <your distro here>. You don''t need SWIG/C++ experience for it, and a little work could help a lot of people. Nick -------- Original Message -------- Subject: Re: Help a newbie pick a gui tool kit Date: Sun, 13

I just grabbed the latest wxruby-swig from cvs and tried to compile it (without enabling the SWIG step) on my gentoo Linux box. I get: g++ -c -I/usr/lib/wx/include/gtk2-2.4 -DGTK_NO_CHECK_CASTS -D__WXGTK__ -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -O2 -march=athlon-xp -fPIC -I /usr/lib/ruby/gems/1.8/gems/rake-0.4.8/bin -I /usr/lib/ruby/gems/1.8/gems/rake-0.4.8/lib -I

-- +-[ Kontra, Gergely<kgergely@mcl.hu> PhD student Room IB113 ]---------+ | http://www.mcl.hu/~kgergely "Olyan langesz vagyok, hogy | | Mobil:(+36 20) 356 9656 ICQ: 175564914 poroltoval kellene jarnom" | +-- Magyar php mirror es magyar php dokumentacio: http://hu.php.net --+ -------------- next part -------------- A non-text attachment was scrubbed... Name:

Hi We''re all keen to get a release out, for lots of reasons: getting more people testing, showing people the progress we''ve made, etc. So I suggest that we now look to release an alpha version very soon, based pretty much on the current state of CVS plus pending check-ins. Sure, it has some bugs, some missing features and segfaults occasionally - but my experience on OS X

I am working on the Printer, PrintDialog, PrintDialogData, PrinterDC, etc... classes and I''m having a problem with Printout. In the wxWindows source, the file "prntbase.h" defines the class "wxPrintout". When wrapping this for wxRuby I am trying the call: cppResult = new wxPrintout( cppParm0 ); //where cppParm0 is a wxString If I do this it complains that I need

Hi, my first post here so a little background first... I started out using wxRuby-0.6.0 about 4 months ago while trying to get a grip on Ruby as a means of writing a little budgetting app I''ve been meaning to write for a couple of years. As I didn''t like the way that the wxruby examples are coded (having to punch the individual C++ api methods that way isn''t nice) I

Hey everybody, I''ve made some progress on wxruby-swig, and have some good news and some bad news. The good news is that the MSVC version finally can run all of the samples provided in CVS. I''m using the same solve-by-ignore solution to the GC problem that wxruby uses, so there is far less crashing goin'' on. Depending on the next few weeks, we might be able to