similar to: Progress on wxruby-swig segfaults

Hello, is it possible to code a wxWidgets GUI in C++ and pass the whole wxApp or just single windows to embedded Ruby code? This would be very nice to provide a scriptable plugin system. Greetings, Niklas _______________________________________________ wxruby-users mailing list wxruby-users@rubyforge.org http://rubyforge.org/mailman/listinfo/wxruby-users

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

wxRuby 0.6.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 and MS Windows. Changes in this release include: * Additional widget support in XRC (thanks to Marshall Elfstrand) * Addition of wxScrollbar (thanks to Hans Harmon of Pinnacle Technologies Inc) * Addition of wxGrid event handlers (thanks

I''ve checked a number of new .i files into the wxruby-swig tree. Not all of them are fully tested, but I thought it would be better for them to be there than to have somebody start duplicating the work. I''ve also added the ''caret'' and ''image'' samples, as well as the generic etc/test.rb. These need the unreleased SWIG-1.3.22. The current

Bugs item #17013, was opened at 2008-01-11 06:00 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=218&aid=17013&group_id=35 Category: Missing API call Group: None Status: Open Resolution: None Priority: 3 Submitted By: Daniel Brumbaugh Keeney (db-keen) Assigned to: Nobody (None) Summary: Notebook#get_current_page Initial Comment: Notebook#get_current_page

Hi Everyone, Over the past couple of weeks wxruby-swig has made a lot of progress. Over 100 classes have been added with attempts to mimic the existing wxruby interfaces. While still not as stable as wxruby, stability has increased dramatically. Finally, it has been built on Linux, Mac, and MSVC. This email is an invitation to try out wxruby-swig for yourself. The source code is in CVS and

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

Here''s a patch to fix Wx::Window#get_text_extent - it requires that the patches from teh last message are applied, to enable *INPUT etc typemaps. Roy - though the function works correctly when called from Ruby, it still causes a crash when called internally when clicking on a Wx::Grid cell. Saw your message on SWIG mailing list, hopefully someone there can help out. alex

Hi, What about releasing a new version shortly ? This is a long-awaited request from several users especially for recent ruby-1.9.1 versions on MinGW. Cheers. Chauk-Mean.

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

I found some ugly legacy while working on wxruby-swig. wxBusyCursor, wxBusyInfo, and wxWindowDisabler all use a free method that directly calls the destructor. In the wxruby-swig version of these, I created a static method (named busy,busy, and disable) that runs an attached block while under the influence of the class. I suggest changing the wxruby we change API to match, and get rid of

Sorry for the lameness, but I need things explained to me very slowly... -----Original Message----- Subject: RE: [Wxruby-users] wxGrid Question > > Yes, grab the latest tarball from the above location. Then, you should > install rubygems if you haven''t already: > http://rubyforge.org/projects/rubygems/ > > That should allow you to easily install rake: >

In trying to add wxTextCtrl to wxruby-swig, I''ve been running into a problem with the argument conversion that appears to be a SWIG director bug. It is tied to multiple inheritance, and is related to SWIG specifically making director''s ''initialize'' take a first argument, but because ''initialize'' is static there isn''t a self value

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

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.

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

These files add the virtual function AcceptFocus that was missing from wxWindow.h. In order to make things right I had to make sure it was also declared in all the places where wxWindows also changes it. Also, in wxTextCtrl on Windows GetDefaultAttributes needs to be redeclared. I haven''t downloaded the Unix and Mac headers for 2.6.3 so I couldn''t see if it also applies

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

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