Hi I''d like to tag and release 0.0.38 in the next week or so. I know we still have a nasty GC bug on windows, but I''m thinking we could just tell people to use GC.disable for the time being if that avoids the problem. After all, it''s not meant for production use yet. This would make other recent bugfixes and enhancements available. Plus having a binary build out there might help isolate where the crasher bug is being trigger on mswin by getting more eyes on it. The main things I''d want to get in before tagging: - exception handling in html sample - htmlhelpcontroller sample - TreeCtrl#traverse method Thoughts? alex
Alex, You have been doing all the work lately and if you think 0.0.38 is ready you would know better than anyone. It has been a week or two since I last tested SVN HEAD and it was working well. Between being busy at work and the holidays I have not had a chance to do much of anything on wxRuby, hopefully that will change soon. Keep up the good work Alex. Sean On 12/3/06, Alex Fenton <alex at pressure.to> wrote:> Hi > > I''d like to tag and release 0.0.38 in the next week or so. > > I know we still have a nasty GC bug on windows, but I''m thinking we > could just tell people to use GC.disable for the time being if that > avoids the problem. After all, it''s not meant for production use yet. > > This would make other recent bugfixes and enhancements available. Plus > having a binary build out there might help isolate where the crasher bug > is being trigger on mswin by getting more eyes on it. > > The main things I''d want to get in before tagging: > > - exception handling in html sample > - htmlhelpcontroller sample > - TreeCtrl#traverse method > > Thoughts? > > alex > _______________________________________________ > Wxruby-development mailing list > Wxruby-development at rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-development >
Alex Fenton wrote:> Hi > > I''d like to tag and release 0.0.38 in the next week or so. > > I know we still have a nasty GC bug on windows, but I''m thinking we > could just tell people to use GC.disable for the time being if that > avoids the problem. After all, it''s not meant for production use yet.I''m good with a release. I''ll build it if you want. I''m lukewarm on the traverse method, frankly. It seems easy enough to implement in Ruby using existing methods. I suppose it adds a nice new functionality. Roy
Roy Sutton wrote:> I''m good with a release. I''ll build it if you want.Thanks. I''ll look to tag on the weekend then.> I''m lukewarm on > the traverse method, frankly. It seems easy enough to implement in Ruby > using existing methods.Sorry didn''t see your message til after I''d committed. You''re right. I did a benchmark of the C++ version vs a pure-ruby implementation and the speed gain is only about double in C++. Both are fast on pretty large trees. To my mind the ease of maintaining and debugging methods written in ruby is worth more than that minor speed up. Well, it was an interesting way to learn about function pointers in C++; enough to make me glad for blocks in ruby. The cookie passing for iterating over children in wxTreeCtrl#get_next_child is a pain though and weird for ruby programmers. I''d suggest we at least implement TreeCtrl#get_children, returning an array of items alex