Hello I''m pleased to say that wxruby2-preview 0.0.38 is now available on Rubyforge and via gems. We''re offering source and binaries for Windows, OS X and Linux. == Install gem install wxruby2-preview https://rubyforge.org/frs/?group_id=35 == What''s New * HtmlWindow and HtmlEasyPrinting, plus related classes * HelpController and HtmlHelpController for displaying online help * Enhanced internationalisation support for working with languages and encodings, including the Locale class * Fixed the useful item_data family of functions, for associating ruby objects with UI controls * Numerous fixes and enhancements within existing classes * New and updated docs and samples There''s a full Changelog on the website. == Important This is still a preview/alpha release. There''s still some GC-related crashers, and some platform problems with particular classes. It''s not quite suitable for production use. == TODO I''m hoping we can offer a beta release of wxruby2 within the next couple of release cycles. The main tasks outstanding are: - fix known GC and platform bugs - add the Clipboard and Drag''n''Drop classes - a few odd missing classes and methods - update and tidy the samples and documentation You can really help by reporting bugs and missing features on the rubyforge tracker: https://rubyforge.org/tracker/?group_id=35 == Thanks Big thanks to everyone who helped make this release happen - contributors, builders, bug reporters and enthusiasts. Wishing you all a happy and peaceful christmas from the wxruby2 team Alex
paul.allton at uk.bnpparibas.com
2006-Dec-20 15:09 UTC
[Wxruby-users] wxruby2-preview 0.0.38 released
Great work on the release. Unfortunately, I''m experiencing a lot of segmentation faults on the windows build. I havent yet managed to create a 100% repeatable test case, but there seems to be a problem when selecting items in combo boxes (or updates happening thereafter). The message is as follows: C:/dev/ruby/lib/ruby/gems/1.8/gems/wx_sugar-0.1.13/lib/wx_sugar/accessors.rb:53: [BUG] Segmentation fault ruby 1.8.4 (2006-04-14) [i386-mswin32] This application has requested the Runtime to terminate it in an unusual way. Please contact the application''s support team for more information. This message and any attachments (the "message") is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable for the message if modified. ********************************************************************************************** BNP Paribas Private Bank London Branch is authorised by CECEI & AMF and is regulated by the Financial Services Authority for the conduct of its investment business in the United Kingdom. BNP Paribas Securities Services London Branch is authorised by CECEI & AMF and is regulated by the Financial Services Authority for the conduct of its investment business in the United Kingdom. BNP Paribas Fund Services UK Limited is authorised and regulated by the Financial Services Authority -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wxruby-users/attachments/20061220/0d841428/attachment.html
paul.allton at uk.bnpparibas.com wrote:> Great work on the release. Unfortunately, I''m experiencing a lot of > segmentation faults on the windows build.I hadn''t tried the Windows build until I saw your message, but a quick test gives me the same thing on bigdemo. This is definitely a problem with garbage collection. I am able to work around it by placing GC.disable at the start of my scripts. Not ideal but it should allow you to proceed with developing other functionality. This is a top priority fix. Sorry for the inconvenience, but we have a chicken and egg problem with the Windows build - lots of people want to use it, but very few people have a compiler and build environment on that platform. But without getting a build out there, it''s hard to home in on bugs. I''m think it will not be too hard to trace the problem to one or two more classes which need a bit of extra handcrafted memory management. Unfortunately you need a debugger to track down the problem classes - the segfault line reports are misleading. If anyone already has something set up on Windows a few stack traces from these crashes would be *very* helpful. Alex
I''m curious how the stability of the latest WxRuby2 preview compares to the previous WxRuby (1) release? Jamal
Hi Jamal It depends which platform you look at. IMO, stability for 0.0.38: Windows - worse than wxruby 0.6.0 Linux - similar OS X - similar or better API coverage within classes is much better in wxruby2, so fewer ruby workarounds for missing methods. If you''re considering upgrading your text editor app, I''d suggest waiting for 0.0.39 which will include numerous stability fixes. I''m currently working on one for the Windows crashes. alex Jamal Mazrui wrote:> I''m curious how the stability of the latest WxRuby2 preview compares to > the previous WxRuby (1) release? > > Jamal > > _______________________________________________ > wxruby-users mailing list > wxruby-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-users > > >