similar to: Is wxRuby-SWIG version usable enough to package for download?

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

Hello all. This gets past the problem in bigdemo where it won''t start the application at all. That was where it was overflowing the stack on get_label. Roy _______________________________________________ wxruby-users mailing list wxruby-users@rubyforge.org http://rubyforge.org/mailman/listinfo/wxruby-users

I''m fairly new to the Ruby world, particularly WxRuby, so please forgive me if this is ground that''s been covered in the past. I''m trying to load a frame from an XRC file (created using DialogBlocks), and I''m having trouble getting an instance of the Gauge object using the Wx::Window.find_window_by_xxx methods. I''m trying this on Windows XP,

The previous TreeCtrl.i was very messy and just plain wrong, for instance it had GetFirstChild as depreciated when in fact only 1 version of it was depreciated not both. I changed GetFirstChild and GetNextChild to return an array of values to match the wxPython and wxPerl usage. I also noticed that wxTreeCtrl is inherited from wxControl on Windows and wxScrolledWindow on everything else so I #if

What I''d like to be able to do is use a wxTreeCtrl to manage a tree layout of not only text, but several buttons which would line up adjacent to the text in the tree items. I''ve googled around a bit on this and it doesn''t seem straightforward, if it is possible at all. Can anyone provide any pointers for attempting this? In a simple ASCI schematic, it would be like

Hello guys, Alright Alex..... I need a few tips on where to start. I know that I''m going to need to rewrite the wxSocket header files, in order to incorperate them into wxRuby. But some advice on stuff such as wxSocketClient::new/connect, where it takes a wxIPAddress, and so forth. I know they are pretty friviolous structures for holding information about Addresses in which to make

OS is smeserver, based on CentOS/RHEL 4. After update to samba 3.0.25b (included in RHEL U6) users who had "mapped" their home in Network places were unable to access the share. All other shares worked. On every attempt a line similar to the following was logged: Feb 14 10:11:49 nethservice smbd[6258]: '/home/e-smith/files/users/FRANCESCA/home' does not exist or permission

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 just pushed a new wxruby-swig, which includes the known MSWin rakefile changes. It also has some significant internal improvements that will make it easier to add classes, and it includes support for one new class (wxEvent). wxruby-swig is now licensed under the "MIT license". wxRuby will remain under the wxWindows license as long as we are releasing the old code base. When we

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

Hi all Have been taking a look at the samples to see what''s broken. Not looking TOO bad overall, but a few problems we should try and tackle before alpha: Firstly, I have a few commits (minimal, dialogs, unicode) - anyone else been working on these or can I go ahead? One general issue is that many of the samples rely on being run from their own directory, but don''t enforce

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

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

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

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.

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''m trying to build wxruby-swig on windows with the idea of building a windows installer for it. I think that this would go a long way toward encouraging windows developers to try out wxruby-swig. What do you think? Are we far enough along to contemplate a release? Building wxruby-swig on windows is actually going pretty smoothly, but I want to build it with vc++ 7.1 to match the

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

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)

Hi! Is drag''n''drop works currently under wxruby? I want an app, where you can drag files from a wxlistctrl to a wxtreectrl. Can anyone show a little example? Gergo -- +-[ 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