Hi all, I spent about 8 more hours tonight, and I think I''m close to having a wxruby2 build that works with wxWidgets 2.6.3 and SWIG 1.3.29. It should run bigdemo as well as the other samples. Unfortunately, I probably won''t have much time to work on it until next weekend :-( Tonight''s frustration was with wxART_INFORMATION. It''s sort of a wxArtID and sort of a wxString. I finally(!) got the generated C++ code to look pretty good, but it segfaults deep within the wx code. So for now I plan to disable wxArtProvider#get_icon and #get_bitmap, and comment those calls out in the controls.rb sample. One other quirk: In bigdemo, my splitter is stuck at the top of the right pane. I think I saw this before (months ago), and can''t remember what caused it. I think I found a solution back then. If anyone knows the answer, it will save me a visit to the mailing list archives. Kevin P.S. I wish we had an RCS that allowed easy branching so I could publish my not-quite-working code in case anyone wanted to play with it. I''m just not comfortable branching in CVS for something like this.
I''m certainly interested in taking a look at what you''ve got. I''ve been working a bit more on things and just started adding %predicate and %alias to some of the .i files so that we have a more rubyish interface to wx. However, I don''t see any reason for you to fork things just for that. I think we''ll all be happier when we''ve got a baseline checked into the RCS that we can begin working from again. Roy Kevin Smith wrote:> Hi all, > > I spent about 8 more hours tonight, and I think I''m close to having a > wxruby2 build that works with wxWidgets 2.6.3 and SWIG 1.3.29. It should > run bigdemo as well as the other samples. Unfortunately, I probably > won''t have much time to work on it until next weekend :-( > > Tonight''s frustration was with wxART_INFORMATION. It''s sort of a wxArtID > and sort of a wxString. I finally(!) got the generated C++ code to look > pretty good, but it segfaults deep within the wx code. So for now I plan > to disable wxArtProvider#get_icon and #get_bitmap, and comment those > calls out in the controls.rb sample. > > One other quirk: In bigdemo, my splitter is stuck at the top of the > right pane. I think I saw this before (months ago), and can''t remember > what caused it. I think I found a solution back then. If anyone knows > the answer, it will save me a visit to the mailing list archives. > > Kevin > > P.S. I wish we had an RCS that allowed easy branching so I could publish > my not-quite-working code in case anyone wanted to play with it. I''m > just not comfortable branching in CVS for something like this. > > > _______________________________________________ > wxruby-users mailing list > wxruby-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-users > > > >
On 4/17/06, Kevin Smith <wxruby at qualitycode.com> wrote:> > P.S. I wish we had an RCS that allowed easy branching so I could publish > my not-quite-working code in case anyone wanted to play with it. I''m > just not comfortable branching in CVS for something like this. >RubyForge now supports both Subversion and CVS. Tom Copeland can switch us to a subversion repo (the conversion process saves all change history). I''ve already done this with the one-click installer and instant rails -- it worked beautifully. Just make sure you''ve got everything checked in and sen Tom a note asking for the conversion (or I can do it if you like). Curt -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wxruby-users/attachments/20060417/02910026/attachment.htm
On Mon, 2006-04-17 at 21:55 -0500, Curt Hibbs wrote:> RubyForge now supports both Subversion and CVS.Thanks for the reminder. I still view svn as "merely" an incremental improvement over cvs, so I tend to forget that it''s even an option. My attention is on bzr (bazaar-ng) and other distributed RCS tools. My hope is that wxruby can switch to a d-rcs system within the next year or so. Since it is unlikely to happen within the next few months, it might be worthwhile switching to svn for now, and switching again later. Any strong opinions from the rest of you? Should we jump to svn now? Kevin
The only problem with Darcs right now is that the GHC compiler does not work on Intel based Macs (which is my main home machine where I work on wxRuby, if I have time). Hopefully the GHC group will get it up and running soon so I can compile Darcs. Sean On 4/18/06, Kevin Smith <wxruby at qualitycode.com> wrote:> On Mon, 2006-04-17 at 21:55 -0500, Curt Hibbs wrote: > > RubyForge now supports both Subversion and CVS. > > Thanks for the reminder. I still view svn as "merely" an incremental > improvement over cvs, so I tend to forget that it''s even an option. My > attention is on bzr (bazaar-ng) and other distributed RCS tools. > > My hope is that wxruby can switch to a d-rcs system within the next year > or so. Since it is unlikely to happen within the next few months, it > might be worthwhile switching to svn for now, and switching again > later. > > Any strong opinions from the rest of you? Should we jump to svn now? > > Kevin > > > _______________________________________________ > wxruby-users mailing list > wxruby-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-users >