Jeremy Stell-Smith wrote:> Thanks a lot for the help, guys. I''m up and running with 2.4.2, but I > did have a few questions.Excellent.> So first, a friend and I basically have this month to dedicate to trying > to get a ruby ide pilot built on top of wxRuby. So, no, I really can''t > wait a few weeks to start. Any chance you could commit changes into cvs > as you make them? or is it really more of a it either all works or none > of it works type thing? It''s not a huge deal, but it means that we''ll > be writing some code that we''ll have to throw away after you guys are done.Moving to swig is really an all-or-nothing deal. I am creating wxruby-swig in parallel, in a completely separate code tree (which is public). It shares absolutely nothing with the existing code. I always prefer incremental approaches, but I could not figure out any way to blend swig and non-swig code together in an interim state. So, any work you do on the wxruby code base will, unfortunately, be thrown away. On the other hand, you could throw some effort behind wxruby-swig, and perhaps it could become usable quickly enough for your project. The nice thing about wxruby-swig is that it is FAR easier to add support for many classes and methods, and somewhat easer for the rest. Already, wxruby-swig supports about 25% of the classes in wxruby 0.3.0. If you want to try that route, let me know (perhaps off-list), and we can discuss logistics.> Second, we need the scintilla stc widget, the "StyledTextControl". This > doesn''t get installed by default by wxWindows/wxWidgets, and lives in > their contrib folder. What is your advice about this? > * should the ruby wrappers for scintilla live in wxRuby? It''s a contrib > package and not installed by default, should there be a contrib package > in wxRuby? If so, how does an application that wants this functionality > (like ours) go about installing it? > * should the user have to make and install this widget manually? that''s > currently what happens. at least on mac and linux.Eventually, I would like to include wxScintilla (and probably some other contrib''d items) as part of wxruby. For the moment, I would recommend whatever is the least amount of work to actually get it functional. I haven''t yet figured out how add-ons like that should be structured in wxruby.> 2.5.2, changes this and calls wxInitializeStockObjects from an instance > method wxApp, which means that an app needs to be created BEFORE any > constants can be loaded into the Wx module in ruby. This breaks all the > examples :)Very interesting. In wxruby-swig, I was forced into the same pattern even with wxWindows 2.4.2, due to how SWIG works. I actually invoke Init_wxRubyStockObjects() from inside a callback made by the App object that got created. So, fortunately, the problem goes away with wxruby-swig. Thus, it''s probably not worth adding wxWidgets 2.5 support to the non-swig wxruby.> Anyway, these are my thoughts after poking around in the code for a > couple days. Does this make sense, what do you guys think? I''m > assuming that you want to port to 2.5.x.Support for wxWidgets 2.5 (though perhaps not until 2.6) will definitely be important at some point. I appreciate you trying it and reporting the results. I am encouraged that it looks like it may be easier than I had feared. Thanks, Kevin
Kevin, Will WxRuby stop development once WxRuby-SWIG is up to pace? Should I start using wxruby-swig instead of wxruby itself? I don''t want to spend a lot of time with one if it is going to be replaced by the other. Thanks, Zach --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.705 / Virus Database: 461 - Release Date: 6/12/2004
Zach Dennis wrote:> > Kevin, > > Will WxRuby stop development once WxRuby-SWIG is up to pace? > Should I start > using wxruby-swig instead of wxruby itself? I don''t want to spend a lot of > time with one if it is going to be replaced by the other. Thanks,You can use the current wxRuby without worry. The swig version will have the same interface as the current version. The reason for switching to a swig based code base is to make it easier and faster to add support for more wxWidgets classes. Curt
Curt Hibbs wrote:> Zach Dennis wrote: > >>Kevin, >> >>Will WxRuby stop development once WxRuby-SWIG is up to pace? >>Should I start >>using wxruby-swig instead of wxruby itself? I don''t want to spend a lot of >>time with one if it is going to be replaced by the other. Thanks, > > > You can use the current wxRuby without worry. The swig version will have the > same interface as the current version. The reason for switching to a swig > based code base is to make it easier and faster to add support for more > wxWidgets classes.Right. As Curt says, if you just want to _use_ wxruby, the transition from the current version to a future swig-based version should be very easy, and in most cases, completely transparent. If you want to contribute code to wxruby itself, then you should focus on the swig-based code, because the swig-based code will replace the existing code within a few months. I hope that''s clear. If not, please ask more questions. Kevin
>Right. As Curt says, if you just want to _use_ wxruby, the transition >from the current version to a future swig-based version should be very >easy, and in most cases, completely transparent.Good to know.>If you want to contribute code to wxruby itself, then you should focus >on the swig-based code, because the swig-based code will replace the >existing code within a few months.As much as I would love to focus on contributing to the *code*, I am much more excited in figuring out how to use wxRuby. I am also mucho inclined to write documentation. So after the wedding this weekend (yep mine) and the honeymoon next week (mine too;) I will start writing gobs of tutorials and documentation for wxRuby. Once I feel that I understand it well enough on a whole level I will then try contributing to the code, but for now I''d like to start writing docs so other folks can feel more inclined to use wxRuby and not so intimidated by it. So expect sometime in July for doc submissions by yours truly. Zach P.S. - I love wxRuby....thanks to Curt Hibbs for mentioning it on the Ruby list when I volunteered to make the miniSpreadsheet app for Andrea''s Practical Language Comparison. Which by the way will be posted sometime this week. --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.688 / Virus Database: 449 - Release Date: 5/18/2004
Zach Dennis> > As much as I would love to focus on contributing to the *code*, I am much > more excited in figuring out how to use wxRuby. I am also mucho > inclined to > write documentation. So after the wedding this weekend (yep mine) and the > honeymoon next week (mine too;) I will start writing gobs of tutorials and > documentation for wxRuby. Once I feel that I understand it well > enough on a > whole level I will then try contributing to the code, but for now I''d like > to start writing docs so other folks can feel more inclined to use wxRuby > and not so intimidated by it.Many congrats on the marriage -- hopefully her name is not Ruby... I''d hate for there to be a "conflict of interest". ;-) Thanks so much for being excited and willing to contribute docs & tutorials, that will be a tremendous help.> So expect sometime in July for doc submissions by yours truly. > > Zach > > P.S. - I love wxRuby....thanks to Curt Hibbs for mentioning it on the Ruby > list when I volunteered to make the miniSpreadsheet app for Andrea''s > Practical Language Comparison. Which by the way will be posted > sometime this > week.Your welcome! Curt