An update on status: Today I fixed the last bug on the tracker which was marked MUSTFIX for 2.0 - can''t paste text to clipboard on Linux. I also did a big rework of the DataObject classes, so that wxRuby now supports exchanging user-defined data formats. However there are still a few problems with some DataObjects - these are noted as FIXMEs in the file tests/test_clipboard.rb. The most serious is not being able to exchange BitmapData. I''ve got to a point of being fed up working on these classes for a while (it''s taken several days again) so if everything''s still looking good, I''m inclined to do a release to get the many other fixes out there. Just wondering if it should be 1.9.10 or 2.0? My heart says 2.0, my head says 1.9.10... alex
Alex Fenton wrote:> However there are still a few problems with some DataObjects - these > are noted as FIXMEs in the file tests/test_clipboard.rb. The most > serious is not being able to exchange BitmapData.This turns out to be have been a shortcoming of the test case; BitmapData is working fine, internally at least. a
Hi, 2009/1/14 Alex Fenton <alex at pressure.to>:> Alex Fenton wrote: >> >> However there are still a few problems with some DataObjects - these are >> noted as FIXMEs in the file tests/test_clipboard.rb. The most serious is not >> being able to exchange BitmapData. > > This turns out to be have been a shortcoming of the test case; BitmapData is > working fine, internally at least.So, there is no blocking issue :-). The latest revision I tested (r1971) was very stable. And I think that a 2.0 stable release will attract more people to wxRuby especially with the indication that wxRuby works fine with ruby-1.9. But obviously, we need to make some tests on the latest revision especially as there have been some big reworks. Also, we have to be sure that the wxruby-1.9-mingw gem will work with mswin60 ruby-1.9. On another point, what about the results of your Ruby + GUI survey ? There was a question on this yesterday (http://www.ruby-forum.com/topic/171252#769246). I answered the survey, so I''m also interested by the results. Cheers, Chauk-Mean.
Chauk-Mean P wrote:> Hi, > > 2009/1/14 Alex Fenton <alex at pressure.to>: > >> Alex Fenton wrote: >> >>> However there are still a few problems with some DataObjects - these are >>> noted as FIXMEs in the file tests/test_clipboard.rb. The most serious is not >>> being able to exchange BitmapData. >>> >> This turns out to be have been a shortcoming of the test case; BitmapData is >> working fine, internally at least. >> > > So, there is no blocking issue :-). >I also managed to resolve one of the other DataObject issues, so there''s only one left, and it''s one that can be worked round. I don''t want to look at that code for a while ...> The latest revision I tested (r1971) was very stable. And I think that > a 2.0 stable release will attract more people to wxRuby especially > with the indication that wxRuby works fine with ruby-1.9. >Good, I agree. I made a further set of commits since 1971, but hopefully nothing breaking. Have tested on OS X 1.8/19 and Linux 1.9> But obviously, we need to make some tests on the latest revision > especially as there have been some big reworks. > Also, we have to be sure that the wxruby-1.9-mingw gem will work with > mswin60 ruby-1.9. >I''ll build a wxruby-1.9 mingw gem today and make it available to you, as I don''t have an mswin32 version of 1.9.> On another point, what about the results of your Ruby + GUI survey ? > There was a question on this yesterday > (http://www.ruby-forum.com/topic/171252#769246). > I answered the survey, so I''m also interested by the results. >Basically - I wrote most of the report, then Christmas hit, then since new year I''ve been busting a gut to get wxRuby 2.0 finished. Anyway, my plan is to publish it next week, at least the main findings and raw data. I''ll drop you a line off-list a
Hey Guys, I''m sitting on #wxruby @ irc.freenode.net, if you guys wanna hop over there, and we can discuss any finalizations we need to do, to get wxRuby 2.0 out the door. L8ers, On Thu, Jan 15, 2009 at 3:03 AM, Alex Fenton <alex at pressure.to> wrote:> Chauk-Mean P wrote: > >> Hi, >> >> 2009/1/14 Alex Fenton <alex at pressure.to>: >> >> >>> Alex Fenton wrote: >>> >>> >>>> However there are still a few problems with some DataObjects - these are >>>> noted as FIXMEs in the file tests/test_clipboard.rb. The most serious is >>>> not >>>> being able to exchange BitmapData. >>>> >>>> >>> This turns out to be have been a shortcoming of the test case; BitmapData >>> is >>> working fine, internally at least. >>> >>> >> >> So, there is no blocking issue :-). >> >> > > I also managed to resolve one of the other DataObject issues, so there''s > only one left, and it''s one that can be worked round. I don''t want to look > at that code for a while ... > > The latest revision I tested (r1971) was very stable. And I think that >> a 2.0 stable release will attract more people to wxRuby especially >> with the indication that wxRuby works fine with ruby-1.9. >> >> > > Good, I agree. I made a further set of commits since 1971, but hopefully > nothing breaking. Have tested on OS X 1.8/19 and Linux 1.9 > > But obviously, we need to make some tests on the latest revision >> especially as there have been some big reworks. >> Also, we have to be sure that the wxruby-1.9-mingw gem will work with >> mswin60 ruby-1.9. >> >> > > I''ll build a wxruby-1.9 mingw gem today and make it available to you, as I > don''t have an mswin32 version of 1.9. > > On another point, what about the results of your Ruby + GUI survey ? >> There was a question on this yesterday >> (http://www.ruby-forum.com/topic/171252#769246). >> I answered the survey, so I''m also interested by the results. >> >> > > Basically - I wrote most of the report, then Christmas hit, then since new > year I''ve been busting a gut to get wxRuby 2.0 finished. Anyway, my plan is > to publish it next week, at least the main findings and raw data. I''ll drop > you a line off-list > > > a > > > _______________________________________________ > wxruby-development mailing list > wxruby-development at rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-development >-- Mario Steele http://www.trilake.net http://www.ruby-im.net http://rubyforge.org/projects/wxruby/ http://rubyforge.org/projects/wxride/ -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/wxruby-development/attachments/20090115/cbdcf13e/attachment-0001.html>
Hi, 2009/1/15 Alex Fenton <alex at pressure.to>:> > I''ll build a wxruby-1.9 mingw gem today and make it available to you, as I > don''t have an mswin32 version of 1.9.Don''t worry about the mingw build. I''m currently doing the build myself.> Basically - I wrote most of the report, then Christmas hit, then since new > year I''ve been busting a gut to get wxRuby 2.0 finished.No problem. Chauk-Mean.
Chauk-Mean P wrote:> But obviously, we need to make some tests on the latest revision > especially as there have been some big reworks. >I think there is a regression with Wx::Clipboard on Windows. I''ve only tried with Ruby-19 MingW, but the clipboard test is segfaulting. Gah. a
2009/1/15 Alex Fenton <alex at pressure.to>:> Chauk-Mean P wrote: >> >> But obviously, we need to make some tests on the latest revision >> especially as there have been some big reworks. > > I think there is a regression with Wx::Clipboard on Windows. I''ve only tried > with Ruby-19 MingW, but the clipboard test is segfaulting. Gah.I also experienced some seg faults occasionnaly with revision1988 and with ruby-19 on MinGW. I''m trying to reproduce the issues. One thing I can reproduce with the dragdrop / clipboard sample : - pressing the paste button raises an exception from line #129 of dragdrop.rb related with is_supported method. - but copy/paste of text with keyboard (CTRL-C / CTRL-V) works for me Chauk-Mean.
2009/1/15 Chauk-Mean P <chauk.mean at gmail.com>:> 2009/1/15 Alex Fenton <alex at pressure.to>: >> Chauk-Mean P wrote: >>> >>> But obviously, we need to make some tests on the latest revision >>> especially as there have been some big reworks. >> >> I think there is a regression with Wx::Clipboard on Windows. I''ve only tried >> with Ruby-19 MingW, but the clipboard test is segfaulting. Gah.I have the same problem with Ruby-19 MinGW and Ruby-1.8 MSVC 7.1.> I also experienced some seg faults occasionnaly with revision1988 and > with ruby-19 on MinGW. > I''m trying to reproduce the issues.I tried again from a new Windows command prompt, and wxRuby samples work well with Ruby-19 MingW. wxRuby samples work also well with Ruby-18 MSVC 7.1.> One thing I can reproduce with the dragdrop / clipboard sample : > - pressing the paste button raises an exception from line #129 of dragdrop.rb related with is_supported method.This issue remains. Chauk-Mean.