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 figure out the exact cause of the problem. I need to learn more about gdb, I guess. Setting that problem aside, SWIG looks very promising. Wrapping additional methods is usually slightly easier than using wxpp. When new types are involved, or for callbacks (like App#on_init), SWIG is *much* easier. There are a couple annoying things, but I can work around them, or try to get them changed in SWIG/Ruby. So far, I am also using "rake", because I hate "make" so much that I didn''t want to bother (re)learning it enough to create a build process that could handle the SWIG stuff. I was able to get a basic rake script working very quickly. Sometime in the next couple weeks, I''ll probably do an initial proof-of-concept release of wxRuby/SWIG using rake, to see how well it works on a variety of systems. If there are too many problems (technical or political), I''ll consider switching back to make. April will probably be a difficult month for me to get much done. If things go according to plan, though, I''ll be able to dedicate quite a bit of time to wxRuby after that. I do hope to release wxRuby 0.3 sometime in April. Assuming we''re switching to SWIG, I don''t want to put more features into the old code. Kevin
How soon will things be checked into DARCS/CVS? The migration will be pretty involved, and some of us could probably help out as soon as we know what you want. Nick Kevin Smith wrote:> 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 > figure out the exact cause of the problem. I need to learn more about > gdb, I guess. > > Setting that problem aside, SWIG looks very promising. Wrapping > additional methods is usually slightly easier than using wxpp. When > new types are involved, or for callbacks (like App#on_init), SWIG is > *much* easier. There are a couple annoying things, but I can work > around them, or try to get them changed in SWIG/Ruby. > > So far, I am also using "rake", because I hate "make" so much that I > didn''t want to bother (re)learning it enough to create a build process > that could handle the SWIG stuff. I was able to get a basic rake > script working very quickly. > > Sometime in the next couple weeks, I''ll probably do an initial > proof-of-concept release of wxRuby/SWIG using rake, to see how well it > works on a variety of systems. If there are too many problems > (technical or political), I''ll consider switching back to make. > > April will probably be a difficult month for me to get much done. If > things go according to plan, though, I''ll be able to dedicate quite a > bit of time to wxRuby after that. I do hope to release wxRuby 0.3 > sometime in April. Assuming we''re switching to SWIG, I don''t want to > put more features into the old code. > > Kevin > _______________________________________________ > wxruby-users mailing list > wxruby-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-users > >
Nick wrote:> > How soon will things be checked into DARCS/CVS? The migration will be > pretty involved, and some of us could probably help out as soon as we > know what you want.Thanks. At this point, I see it as less of a "migration", and more of a big-bang switchover. I''ll put up a darcs repo as soon as the new directory structure becomes stable. That''s easy. I want to put it in CVS soon, too, but it requires a bit more thinking, and assistance. For CVS, assuming we can get help from the rubyforge folks, I''m thinking of creating a new top-level directory on the same level as the current wxruby, perhaps named wxruby-swig. This would be used during "internal" development and testing. When the swig version gets to the point that it supports everything that today''s version supports, on all platforms, both top-level directories would be renamed: wxruby -> wxruby-old wxruby-swig -> wxruby Shortly after that, we would release wxruby-0.5, which would be the swig version. Sound good? Kevin
Kevin Smith wrote:> I''ll put up a darcs repo as soon as the new directory structure becomes > stable. That''s easy.Ok. A **VERY** rough, completely minimal ruby-swig is available at: http://qualitycode.com/repos/wxruby-swig/ You can retrieve it with darcs or wget. You can view the README here: http://qualitycode.com/repos/wxruby-swig/README It only has five classes, and most of those classes have ZERO methods. I have not yet attempted to bring any of the Windows or Mac stuff over from the existing Makefile. It is so premature, it doesn''t even have a version number. The only reason to try this version is if you want to help get it working on other platforms, with SWIG and rake. If you are not up for an adventure, stay away from it! Cheers, Kevin P.S. If anyone can tell my why Apache refuses to include the README file in the directory listing, I would greatly appreciate it!
On 2004 Apr 4, at 18:49, Kevin Smith wrote:> P.S. If anyone can tell my why Apache refuses to include the README > file in the directory listing, I would greatly appreciate it!README is a special file by default in Apache''s auto index pages; see: http://httpd.apache.org/docs/mod/mod_autoindex.html#readmename -- Ryan "John" Platte Custom services, NIKA Consulting http://nikaconsulting.com/
John Platte wrote:> On 2004 Apr 4, at 18:49, Kevin Smith wrote: > >> P.S. If anyone can tell my why Apache refuses to include the README >> file in the directory listing, I would greatly appreciate it! > > README is a special file by default in Apache''s auto index pages;True. Apparently *by default*, Apache excludes README files from directory listings in a way that cannot be overridden in specific directories. What were they thinking??? Anyway, my web host has now changed a system configuration, so the wxruby and wxruby-swig README files appear in the repo directories. Cheers, Kevin