Hi! Is the wxruby project stalled? ps: at least the list... 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 kellene jarnom" | +-- Magyar php mirror es magyar php dokumentacio: http://hu.php.net --+
Gergely Kontra wrote:> > Is the wxruby project stalled?No, Kevin is on vacation. Curt --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.610 / Virus Database: 390 - Release Date: 3/3/2004
Curt Hibbs wrote:> Gergely Kontra wrote: > >>Is the wxruby project stalled? > > No, Kevin is on vacation.Actually, Kevin is now back from vacation. I arrived home late last night. Since no patches have been submitted for Nick''s problem report on 2/24, I propose that I simply tag the existing tree as 0.2. The existing Mac and Windows "pre-builds" will be official 0.2 builds which will be available from rubyforge. I will not build Linux binaries at this time. I haven''t yet had a chance to review the readme(s) to see if they should be updated prior to tagging. If so, that would be the only reason a rebuild would be required. If someone already knows the answer, please let me know. Otherwise, I should be able to evaluate the decision by this weekend. In keeping with my normal Agile philosophy of "release early and often", I hope to crank out a 0.3 release MUCH faster than the last two releases have taken. Let''s say by June 1, as a target. Sooner would be better. Concerns? Kevin
Kevin Smith wrote:> > I haven''t yet had a chance to review the readme(s) to see if they should > be updated prior to tagging. If so, that would be the only reason a > rebuild would be required. If someone already knows the answer, please > let me know. Otherwise, I should be able to evaluate the decision by > this weekend.The windows readme is fine and ready to go. Curt --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.610 / Virus Database: 390 - Release Date: 3/3/2004
I agree. I''ve made the fixes, but haven''t had the time to test them out, so I say we wait for 0x03. Nick Curt Hibbs wrote:>Kevin Smith wrote: > > >>I haven''t yet had a chance to review the readme(s) to see if they should >>be updated prior to tagging. If so, that would be the only reason a >>rebuild would be required. If someone already knows the answer, please >>let me know. Otherwise, I should be able to evaluate the decision by >>this weekend. >> >> > >The windows readme is fine and ready to go. > >Curt >--- >Outgoing mail is certified Virus Free. >Checked by AVG anti-virus system (http://www.grisoft.com). >Version: 6.0.610 / Virus Database: 390 - Release Date: 3/3/2004 > >_______________________________________________ >wxruby-users mailing list >wxruby-users@rubyforge.org >http://rubyforge.org/mailman/listinfo/wxruby-users > > > >
Curt Hibbs wrote:> The windows readme is fine and ready to go.Ok. I see it already says 0.2. I need to update the others, including the main README, to also say 0.2. I think I can make that change and a couple other minor README tweaks, tag the tree, and call it good. Presumably you (Curt and Nick) would need to rebuild the final binary packages for Windows and OSX, respectively, to include the README change(s). Nick: Are there any other OSX README changes that should be included in 0.2, or is the checked-in version accurate (aside from the version number)? Assuming I hear back soon, we should have our 0.2 release early this week, and I can start making 0.3 changes. Thanks, Kevin
Kevin Smith wrote:> > > Assuming I hear back soon, we should have our 0.2 release early this > week, and I can start making 0.3 changes. >I''m ready, just let me know when to redo the build. Curt --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.610 / Virus Database: 390 - Release Date: 3/3/2004
The OS X readme was tweaked, but I didn''t check in the changes. I''ll send the changes off list. Nick Curt Hibbs wrote:>Kevin Smith wrote: > > >>Assuming I hear back soon, we should have our 0.2 release early this >>week, and I can start making 0.3 changes. >> >> >> > >I''m ready, just let me know when to redo the build. > >Curt >--- >Outgoing mail is certified Virus Free. >Checked by AVG anti-virus system (http://www.grisoft.com). >Version: 6.0.610 / Virus Database: 390 - Release Date: 3/3/2004 > >_______________________________________________ >wxruby-users mailing list >wxruby-users@rubyforge.org >http://rubyforge.org/mailman/listinfo/wxruby-users > > > >
Ok. I have checked in Nick''s README changes, and also updated a couple of the other README files. I didn''t make any other changes. Both the CVS and darcs repositories are up to date. The tree has now been tagged as v0_2 in cvs and v0.2 in darcs. Curt and Nick: Please build binaries, and let me know when they are ready. I will figure out the best way to get them posted on rubyforge. I may also try to build a Linux binary, but I don''t consider that a "must have" for 0.2. Thanks all, Kevin
On 0310, Kevin Smith wrote: Hey, wait a minute! Missing line in the depend file: textattr.o: textattr.cpp wx.h textattr.h textdataobject.o: textdataobject.cpp textdataobject.h textdataobject.h One textdataobject.h is enough, but wx.h could be useful... In listctrl.cpp Obsolate ruby method names: OnGetItemText, OnGetItemAttr, OnGetItemImage The last two has default implementations, wxruby should respect it! wxbitmap.cc Instead of wxBitmapType type = wxBITMAP_TYPE_XPM cannot we write wxBITMAP_TYPE_ANY What about my last proposal to simplify the makefile generation? And what about memory management? 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 kellene jarnom" | +-- Magyar php mirror es magyar php dokumentacio: http://hu.php.net --+
Gergely Kontra wrote:> Hey, wait a minute!Thanks for reporting some new problems, as well as reminding me of some known issues. I''ll try to get them all in to 0.3. Would you be willing to add them to the "Bugs" tracker on rubyforge? (Memory management is already there). Thanks, Kevin> > Missing line in the depend file: > textattr.o: textattr.cpp wx.h textattr.h > > textdataobject.o: textdataobject.cpp textdataobject.h textdataobject.h > One textdataobject.h is enough, but wx.h could be useful... > > In listctrl.cpp > Obsolate ruby method names: > OnGetItemText, OnGetItemAttr, OnGetItemImage > > The last two has default implementations, wxruby should respect it! > > wxbitmap.cc > Instead of > wxBitmapType type = wxBITMAP_TYPE_XPM > cannot we write > wxBITMAP_TYPE_ANY > > What about my last proposal to simplify the makefile generation? > > And what about memory management? > > Gergo