Seems the gems and tarball have been downloaded a bit with no reported problems. I suggest we do an alpha release incorporating Roy''s useful recent fixes and announce it more publicly e.g. on the mailing list. It''s not perfect, but again we have made a lot of progress since late July and we should build on it; it was our dev goal. I now personally have to put some effort into other projects for a few weeks, though still around to help building, troubleshooting and committing. I don''t know of anything in the works that will radically improve wxruby2 in the short term - SWIG 1.3.30 may help a lot if it includes Roy''s patches, but there''s no release schedule I can see. So maybe it''s a good time to get some wider feedback and let people know the project is very much alive. A few things maybe to fix for a first public alpha release (maybe-views?) - move to SVN (or just after the release) - bundled documentation (I can have a go at this if desired) - ruby method names?? - checking windows binary gems work OK cheers alex
I got wxScintilla working again. Not sure if we want to plug this in or not. I think it would be great to get the public alpha out ASAP. I don''t know what else really needs to get done right now. I like the ruby method names patch you sent in recently, though I haven''t tested it. I know I tried this before but I think I took a different route. I haven''t yet gotten to the point of trying to build wxPython to see how they manage to wrap everything. Roy Alex Fenton wrote:> Seems the gems and tarball have been downloaded a bit with no reported > problems. I suggest we do an alpha release incorporating Roy''s useful > recent fixes and announce it more publicly e.g. on the mailing list. > > It''s not perfect, but again we have made a lot of progress since late > July and we should build on it; it was our dev goal. I now personally > have to put some effort into other projects for a few weeks, though > still around to help building, troubleshooting and committing. > > I don''t know of anything in the works that will radically improve > wxruby2 in the short term - SWIG 1.3.30 may help a lot if it includes > Roy''s patches, but there''s no release schedule I can see. So maybe it''s > a good time to get some wider feedback and let people know the project > is very much alive. > > A few things maybe to fix for a first public alpha release (maybe-views?) > - move to SVN (or just after the release) > - bundled documentation (I can have a go at this if desired) > - ruby method names?? > - checking windows binary gems work OK > > cheers > alex > > > > > _______________________________________________ > wxruby-users mailing list > wxruby-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-users > > > >
Roy Sutton wrote:> I got wxScintilla working again. Not sure if we want to plug this in or > not. >Nice work. I would favour plugging this in and bundling it in the first gem, so long as we don''t run into any very tricky platform problems. I think it should be optional for source builds. Please post a patch whenever you''re ready.> I like the ruby method names patch you sent in recently, though I haven''t tested it. I > know I tried this before but I think I took a different route. >Like Sean said, I tried but can''t think of any edge cases here (eg classes which already have methods Foo and GetFoo that do different things). It could be done in the .i interface files, but since the SWIG output the patch modifies are standard Ruby C API calls rather than SWIG wrapper code I think it''s a fairly stable target.> I haven''t yet gotten to the point of trying to build wxPython to see how > they manage to wrap everything. >Nor have I - thank you for the reminder as I ought to look here for some inspiration on the Clipboard etc classes. alex
Alex Fenton wrote:> Seems the gems and tarball have been downloaded a bit with no reported > problems. I suggest we do an alpha release incorporating Roy''s useful > recent fixes and announce it more publicly e.g. on the mailing list.I would like to do one more internal release first, and this time include a Windows gem. If we are going to include scintilla, that would also be a big enough item I would like to do an internal test for that. It''s too bad rubyforge doesn''t track gem installations (as opposed to gem downloads). We really don''t know how many people have tried it.> A few things maybe to fix for a first public alpha release (maybe-views?) > - move to SVN (or just after the release)I have been thinking that moving to svn before the public release might make sense. That way, if we get a flood of patches, or a flood of interested contributors, we won''t be struggling with a vcs migration at the same time.> - bundled documentation (I can have a go at this if desired) > - ruby method names??Both of those would be nice, but I don''t consider them showstoppers at this point. So here is my proposal: - Migrate to SVN - Integrate scintilla - Possibly include the new ruby naming patch - Build all 4 binary gems and upload them quietly - After "enough" time and testing, announce THOSE gems as the first alpha release of wxruby2...perhaps early next week Kevin
Kevin Smith wrote:> So here is my proposal: > - Migrate to SVN > - Integrate scintilla > - Possibly include the new ruby naming patch > - Build all 4 binary gems and upload them quietly > - After "enough" time and testing, announce THOSE gems as the first > alpha release of wxruby2...perhaps early next week >Sounds good to me. Shall we ask Rubyforge to migrate us? alex
Alex Fenton wrote:> Shall we ask Rubyforge to migrate us?I guess I''m ready. Fingers crossed! Kevin
Kevin Smith
2006-Sep-13 03:24 UTC
[Wxruby-users] Migrated to SVN! (was: next steps - public alpha?)
Kevin Smith wrote:> Alex Fenton wrote: >> Shall we ask Rubyforge to migrate us? > > I guess I''m ready. Fingers crossed!It is done. We are now using SVN instead of CVS. Woo-hoo! Tom at rubyforge said ours was one of the largest projects he has migrated so far. If you follow the SVN checkout instructions on the rubyforge wxruby SCM page, you will end up with tons and tons of stuff you don''t need. Trust me, I did it. Here is the command you really want for an anonymous (readonly) checkout: svn checkout svn://rubyforge.org/var/svn/wxruby/trunk/wxruby2 And if you are a developer with write privileges, use this: svn checkout svn+ssh://xxx at rubyforge.org/var/svn/wxruby/trunk/wxruby2 (replace ''xxx'' with your rubyforge login name). Either will create a wxruby2 directory under your current directory, just as a CVS checkout of the wxruby2 module used to do. As a quick test, I updated Changelog to mention that the repository was migrated to SVN. My tool (meld) and process worked flawlessly for the commit, so I think we are in good shape. I probably won''t have time to integrate Roy''s 3 recent patches for a day or two. All three (wxMouseEvent, wxScrolledWindow, and Unicode/Windows) look good to me, so if you (Alex) want to merge them in before I get to them, feel free. Kevin P.S. Should we post a news item about the migration? Normally, I would, but in this case it might draw more attention than we really want while we are in stealth pre-alpha mode. Thoughts?
Sean Long
2006-Sep-15 05:40 UTC
[Wxruby-users] Migrated to SVN! (was: next steps - public alpha?)
A note for OS X users: I have svn 1.3.2 installed via darwin ports and this command: svn checkout svn://rubyforge.org/var/svn/wxruby/trunk/wxruby2 does not work! but this one does: svn co svn://rubyforge.org/var/svn/wxruby/trunk/wxruby2 They should be the same, I have no idea why it did not work with checkout. I wasted 15 minutes on that one. Sean On 9/12/06, Kevin Smith <wxruby at qualitycode.com> wrote:> Kevin Smith wrote: > > Alex Fenton wrote: > >> Shall we ask Rubyforge to migrate us? > > > > I guess I''m ready. Fingers crossed! > > It is done. We are now using SVN instead of CVS. Woo-hoo! Tom at > rubyforge said ours was one of the largest projects he has migrated so far. > > If you follow the SVN checkout instructions on the rubyforge wxruby SCM > page, you will end up with tons and tons of stuff you don''t need. Trust > me, I did it. Here is the command you really want for an anonymous > (readonly) checkout: > > svn checkout svn://rubyforge.org/var/svn/wxruby/trunk/wxruby2 > > And if you are a developer with write privileges, use this: > > svn checkout svn+ssh://xxx at rubyforge.org/var/svn/wxruby/trunk/wxruby2 > > (replace ''xxx'' with your rubyforge login name). > > Either will create a wxruby2 directory under your current directory, > just as a CVS checkout of the wxruby2 module used to do. > > As a quick test, I updated Changelog to mention that the repository was > migrated to SVN. My tool (meld) and process worked flawlessly for the > commit, so I think we are in good shape. > > I probably won''t have time to integrate Roy''s 3 recent patches for a day > or two. All three (wxMouseEvent, wxScrolledWindow, and Unicode/Windows) > look good to me, so if you (Alex) want to merge them in before I get to > them, feel free. > > Kevin > > > P.S. Should we post a news item about the migration? Normally, I would, > but in this case it might draw more attention than we really want while > we are in stealth pre-alpha mode. Thoughts? > _______________________________________________ > wxruby-users mailing list > wxruby-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-users >
Kevin Smith wrote:> It is done. We are now using SVN instead of CVS. Woo-hoo! >Great, thanks. Diffs and commits seem much faster to me. Have updated the wiki. The emacs PSVN mode doesn''t look quite as nice as the in-built CVS mode, and I can''t get the 1.4 subversion release to compile, but other than that all well.> P.S. Should we post a news item about the migration? Normally, I would, > but in this case it might draw more attention than we really want while > we are in stealth pre-alpha mode. Thoughts?I''ve posted a comment on the wiki but I think better to wait until release to post a rubyforge news item for the reasons you give. Anyone who''s actually gone to the home page is probably interested enough already. a