From zdennis at mktec.com Tue Feb 1 22:05:17 2005 From: zdennis at mktec.com (Zach Dennis) Date: Tue Feb 1 22:06:29 2005 Subject: [Wxruby-users] New Doc Status In-Reply-To: <41EB01F8.2050600@nicreations.com> References: <41EAFAF1.8040907@mktec.com> <41EB01F8.2050600@nicreations.com> Message-ID: <4200436D.5050204@mktec.com> Ok another update. Work has been fluxing...so bare with me. - Parsing xml doc into individual class files is complete - Parsing wx windows source for ruby classes, modules, instance methods, singleton methods, module methods, etc.. is complete - recreating ruby source files based on the parsed xml doc and the parsed wx windows source is about 50% Once recreating ruby source files with documentation from the parsed xml doc is complete I will first (test of course) and then create the new rdoc template. If any questions, comments or concerns please feel free to let me know. Also Nick if it would be helpful, I can setup Trac software tracking system on a server. http://www.edgewall.com/trac/ Zach From devel at nicreations.com Tue Feb 1 23:18:00 2005 From: devel at nicreations.com (Nick) Date: Tue Feb 1 23:17:33 2005 Subject: [Wxruby-users] New Doc Status In-Reply-To: <4200436D.5050204@mktec.com> References: <41EAFAF1.8040907@mktec.com> <41EB01F8.2050600@nicreations.com> <4200436D.5050204@mktec.com> Message-ID: <42005478.1080505@nicreations.com> Zach Dennis wrote: > Ok another update. Work has been fluxing...so bare with me. > > - Parsing xml doc into individual class files is complete > - Parsing wx windows source for ruby classes, modules, instance > methods, singleton methods, module methods, etc.. is complete > - recreating ruby source files based on the parsed xml doc and the > parsed wx windows source is about 50% > > Once recreating ruby source files with documentation from the parsed xml > doc is complete I will first (test of course) and then create the new > rdoc template. Great news, Zach! > If any questions, comments or concerns please feel free to let me know. > Also Nick if it would be helpful, I can setup Trac software tracking > system on a server. http://www.edgewall.com/trac/ Rubyforge provides simple tracking, so for now I think we can stick to that. If you think there are some features this has, then I won't stop you. :-D Nick From devel at nicreations.com Fri Feb 4 00:18:30 2005 From: devel at nicreations.com (Nick) Date: Fri Feb 4 00:18:02 2005 Subject: [Wxruby-users] wxruby swig update Message-ID: <420305A6.7060904@nicreations.com> Good news and bad news. First he good news. wxruby-swig now compiles on Linux, Mac, and Windows using wxWidgets 2.5. I just patched a bug with the paint method today, but it's getting very close to the first release of wxruby. With a little more cleanup, I think we're getting ready to do a first release of it, which will hopefully replaced wxruby. Of course, the debug spew needs to be removed, and Zach's new documentation will be a great addition, so we should probably come up with a list of things that should be done to make it "releaseable". Now the bad news: SWIG has made progress, and I haven't been folowing along. While initially you needed the most recent SWIG to build wxruby-swig, it appears now you need to use 1.3.22 or it just won't work. I hope to leave this alone for now, and fix it after we get a release out. Thats all from here, Nick From zdennis at mktec.com Fri Feb 4 10:36:25 2005 From: zdennis at mktec.com (Zach Dennis) Date: Fri Feb 4 10:33:21 2005 Subject: [Wxruby-users] wxruby swig update In-Reply-To: <420305A6.7060904@nicreations.com> References: <420305A6.7060904@nicreations.com> Message-ID: <42039679.6010302@mktec.com> Nick wrote: > > Good news and bad news. > > First he good news. wxruby-swig now compiles on Linux, Mac, and Windows > using wxWidgets 2.5. I just patched a bug with the paint method today, > but it's getting very close to the first release of wxruby. With a > little more cleanup, I think we're getting ready to do a first release > of it, which will hopefully replaced wxruby. Of course, the debug spew > needs to be removed, and Zach's new documentation will be a great > addition, so we should probably come up with a list of things that > should be done to make it "releaseable". > > Now the bad news: SWIG has made progress, and I haven't been folowing > along. While initially you needed the most recent SWIG to build > wxruby-swig, it appears now you need to use 1.3.22 or it just won't > work. I hope to leave this alone for now, and fix it after we get a > release out. > Great news!! So is the swig-version going to be first released with 2.5 support? The documentation I'm working on parses the 2.4 xml file. Will the original parser create a xml file in the same format for 2.5 ? Thanks, Zach From melfstrand at maf.org Fri Feb 4 14:13:26 2005 From: melfstrand at maf.org (Marshall Elfstrand) Date: Fri Feb 4 14:10:19 2005 Subject: [Wxruby-users] wxruby swig update In-Reply-To: <420305A6.7060904@nicreations.com> References: <420305A6.7060904@nicreations.com> Message-ID: That's excellent, Nick! Thanks! I think a while back there was some talk of having methods like "set_label" be changed to a more Ruby-attribute-like "label=" syntax. Is this still being considered? I'm very much in favor of it, but I'm wondering how the switch will be handled. Would both sets of methods be kept, or would the get_xxx and set_xxx methods be dropped? In the case of the latter, I'm wondering if it would be good to consider this a basic part of the switchover to wxruby-swig. Thanks again for your work and Zach's work on this. This is great stuff! Marshall On Feb 3, 2005, at 9:18 PM, Nick wrote: > > Good news and bad news. > > First he good news. wxruby-swig now compiles on Linux, Mac, and > Windows using wxWidgets 2.5. I just patched a bug with the paint > method today, but it's getting very close to the first release of > wxruby. With a little more cleanup, I think we're getting ready to do > a first release of it, which will hopefully replaced wxruby. Of > course, the debug spew needs to be removed, and Zach's new > documentation will be a great addition, so we should probably come up > with a list of things that should be done to make it "releaseable". > > Now the bad news: SWIG has made progress, and I haven't been folowing > along. While initially you needed the most recent SWIG to build > wxruby-swig, it appears now you need to use 1.3.22 or it just won't > work. I hope to leave this alone for now, and fix it after we get a > release out. > > Thats all from here, > > Nick > _______________________________________________ > wxruby-users mailing list > wxruby-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-users > From devel at nicreations.com Fri Feb 4 15:34:21 2005 From: devel at nicreations.com (Nick) Date: Fri Feb 4 15:30:18 2005 Subject: [Wxruby-users] wxruby-swig update Message-ID: > Great news!! So is the swig-version going to be first released with 2.5 > support? The documentation I'm working on parses the 2.4 xml file. Will > the original parser create a xml file in the same format for 2.5 ? Thankfully, the XML hasn't changed - I'm using the same file and removing the stripped methods. > I think a while back there was some talk of having methods like > "set_label" be changed to a more Ruby-attribute-like "label=" syntax. > Is this still being considered? I'm very much in favor of it, but I'm > wondering how the switch will be handled. Would both sets of methods > be kept, or would the get_xxx and set_xxx methods be dropped? In the > case of the latter, I'm wondering if it would be good to consider this > a basic part of the switchover to wxruby-swig. Thats still the intention, but it probably won't be until we get wxruby-swig to match the wxruby functionality. It has to be done by hand, which isn't something I want to mess with at the moment. Nick From zdennis at mktec.com Mon Feb 7 16:33:11 2005 From: zdennis at mktec.com (Zach Dennis) Date: Mon Feb 7 16:29:59 2005 Subject: [Wxruby-users] New Docs - First Look Message-ID: <4207DE97.5010608@mktec.com> Ok, my first complete swipe for the new docs (but still with old rdoc default output templates) can be seen at: http://www.mktec.com/dev_www/wxruby-docs/ Most of the classes/methods documentation came out fine, but I still need finetune because some methods don't get documented at all, like methods in the classes Bitmap and Frame. Once I can get it so all things get documented I'm going to work on the template for rdoc output. After the template is done, I am going to work on filtering the documenation and to create links and modify cpp style method names to ruby-style names. For example where it would say "wxApp::SetTopWindow" I would change that into a link "App::set_top_window" I hope to have more progress later tonight. Zach From alex at pressure.to Mon Feb 7 17:01:34 2005 From: alex at pressure.to (alex fenton) Date: Mon Feb 7 18:18:48 2005 Subject: [Wxruby-users] New Docs - First Look In-Reply-To: <4207DE97.5010608@mktec.com> References: <4207DE97.5010608@mktec.com> Message-ID: <4207E53E.90103@pressure.to> Hi Zach Nice one. Just a couple of things from a first scan = you maybe picked them up already - the methods don't show up with the argument description - they all show as 0-args - the class listing seems to end after Wx::Image, nothing for Wx::ImageList onwards but basically just wanted to say great, thanks alex Zach Dennis wrote: > Ok, my first complete swipe for the new docs (but still with old rdoc > default output templates) can be seen at: > > http://www.mktec.com/dev_www/wxruby-docs/ > > Most of the classes/methods documentation came out fine, but I still > need finetune because some methods don't get documented at all, like > methods in the classes Bitmap and Frame. > > Once I can get it so all things get documented I'm going to work on the > template for rdoc output. After the template is done, I am going to work > on filtering the documenation and to create links and modify cpp style > method names to ruby-style names. For example where it would say > "wxApp::SetTopWindow" I would change that into a link "App::set_top_window" > > I hope to have more progress later tonight. > > Zach > _______________________________________________ > wxruby-users mailing list > wxruby-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-users > > From assaph at gmail.com Mon Feb 7 18:34:25 2005 From: assaph at gmail.com (Assaph Mehr) Date: Mon Feb 7 18:31:10 2005 Subject: [Wxruby-users] New Docs - First Look In-Reply-To: <4207E53E.90103@pressure.to> References: <4207DE97.5010608@mktec.com> <4207E53E.90103@pressure.to> Message-ID: <3ff47be9050207153433ee5534@mail.gmail.com> > - the class listing seems to end after Wx::Image, nothing for > Wx::ImageList onwards Actrually it may be a browser issue - I can see those fine (Firefox 1.0 on WinXP). Zach, I know it's early but you have a typo... In the headers for the classes you have: "This class documentation has been created automatically generated". Hope I'll get the chance to go over it in more detail soon. Cheers, Assaph From devel at nicreations.com Mon Feb 7 23:49:04 2005 From: devel at nicreations.com (Nick) Date: Mon Feb 7 23:48:29 2005 Subject: [Wxruby-users] New Docs - First Look In-Reply-To: <4207DE97.5010608@mktec.com> References: <4207DE97.5010608@mktec.com> Message-ID: <420844C0.1000401@nicreations.com> Totally awesome! :-) Great progress, Zach. This will be far superior to the current docs. Nick Zach Dennis wrote: > Ok, my first complete swipe for the new docs (but still with old rdoc > default output templates) can be seen at: > > http://www.mktec.com/dev_www/wxruby-docs/ > > Most of the classes/methods documentation came out fine, but I still > need finetune because some methods don't get documented at all, like > methods in the classes Bitmap and Frame. > > Once I can get it so all things get documented I'm going to work on the > template for rdoc output. After the template is done, I am going to work > on filtering the documenation and to create links and modify cpp style > method names to ruby-style names. For example where it would say > "wxApp::SetTopWindow" I would change that into a link "App::set_top_window" > > I hope to have more progress later tonight. > > Zach > _______________________________________________ > wxruby-users mailing list > wxruby-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-users > > > From zdennis at mktec.com Tue Feb 8 08:41:06 2005 From: zdennis at mktec.com (Zach Dennis) Date: Tue Feb 8 08:37:54 2005 Subject: [Wxruby-users] New Docs - First Look In-Reply-To: <4207E53E.90103@pressure.to> References: <4207DE97.5010608@mktec.com> <4207E53E.90103@pressure.to> Message-ID: <4208C172.3010702@mktec.com> alex fenton wrote: > Hi Zach > > Nice one. Just a couple of things from a first scan = you maybe picked > them up already > > - the methods don't show up with the argument description - they all > show as 0-args Thanks for pointing this out, this is another thing I need to implement. Right now I'm not parsing out arguments, but this should be easy to add functionality for how the documentation is getting parsed. Zach From zdennis at mktec.com Tue Feb 8 08:42:24 2005 From: zdennis at mktec.com (Zach Dennis) Date: Tue Feb 8 08:39:11 2005 Subject: [Wxruby-users] New Docs - First Look In-Reply-To: <3ff47be9050207153433ee5534@mail.gmail.com> References: <4207DE97.5010608@mktec.com> <4207E53E.90103@pressure.to> <3ff47be9050207153433ee5534@mail.gmail.com> Message-ID: <4208C1C0.3020307@mktec.com> Assaph Mehr wrote: >>- the class listing seems to end after Wx::Image, nothing for >>Wx::ImageList onwards > > > Actrually it may be a browser issue - I can see those fine (Firefox > 1.0 on WinXP). > > Zach, I know it's early but you have a typo... > In the headers for the classes you have: "This class documentation has > been created automatically generated". Thanks for pointing this out, I wrote it once, then decided to change it, then started changing it, then my wife called me to eat...and I forgot about it since! I'll change this and add a date/time stamp. Zach From curt at hibbs.com Tue Feb 8 08:52:37 2005 From: curt at hibbs.com (Curt Hibbs) Date: Tue Feb 8 08:49:10 2005 Subject: [Wxruby-users] New Docs - First Look In-Reply-To: <420844C0.1000401@nicreations.com> Message-ID: Nick wrote: > > Totally awesome! :-) > > Great progress, Zach. This will be far superior to the current docs. > > Nick +1+1+1+1+1+1... Curt > Zach Dennis wrote: > > Ok, my first complete swipe for the new docs (but still with old rdoc > > default output templates) can be seen at: > > > > http://www.mktec.com/dev_www/wxruby-docs/ > > > > Most of the classes/methods documentation came out fine, but I still > > need finetune because some methods don't get documented at all, like > > methods in the classes Bitmap and Frame. > > > > Once I can get it so all things get documented I'm going to work on the > > template for rdoc output. After the template is done, I am > going to work > > on filtering the documenation and to create links and modify cpp style > > method names to ruby-style names. For example where it would say > > "wxApp::SetTopWindow" I would change that into a link > "App::set_top_window" > > > > I hope to have more progress later tonight. > > > > Zach > > _______________________________________________ > > wxruby-users mailing list > > wxruby-users@rubyforge.org > > http://rubyforge.org/mailman/listinfo/wxruby-users > > > > > > > > _______________________________________________ > wxruby-users mailing list > wxruby-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-users > > -- > No virus found in this incoming message. > Checked by AVG Anti-Virus. > Version: 7.0.300 / Virus Database: 265.8.5 - Release Date: 2/3/2005 > From zdennis at mktec.com Tue Feb 8 09:18:01 2005 From: zdennis at mktec.com (Zach Dennis) Date: Tue Feb 8 09:14:48 2005 Subject: [Wxruby-users] New Docs - First Look In-Reply-To: <4207E53E.90103@pressure.to> References: <4207DE97.5010608@mktec.com> <4207E53E.90103@pressure.to> Message-ID: <4208CA19.8020003@mktec.com> alex fenton wrote: > - the class listing seems to end after Wx::Image, nothing for > Wx::ImageList onwards Ah, i see what you are saying. They show up on the list, but not when you click on the link for the classes after Image. I think this was an ftp problem. I saw it error'd out on something, but didn't pay to much attention to what it was. On the Second Look I'll make sure they're all up there. thx Alex, Zach From zdennis at mktec.com Tue Feb 8 23:37:02 2005 From: zdennis at mktec.com (Zach Dennis) Date: Tue Feb 8 23:38:06 2005 Subject: [Wxruby-users] New Docs - One Look and a Partial Glance Message-ID: <4209936E.5060003@mktec.com> Ok, same url as before: http://www.mktec.com/dev_www/wxruby-docs/ We aren't at the second look yet (because i dont' have arguments in the docs yet), but that is coming. This fixes the bug where classes after Image didn't have any docs, and this fixes the issue where many methods weren't documented (like the class Frame). Now the only methods that are not documented are those that don't have a description. I was going to wait until it was all finished before showing everyone, but I couldn't wait and I wanted to let the community know I wasn't pulling their leg. And this way I can get feedback before I get to far along with some of the ideas floating in my head. Any more feedback you guys get would be great. Right now I've gathered: - put arguments and descriptions in rdoc - fix typo in header - convert cpp names in documented source into actual links using the ruby method, (ex: "WxApp::SetTopFrame" => "App::set_top_frame" ) I have some more possible ideas, but would like your feedback. I have the following information and I am thinking of adding it into the rdoc: - the lineno of the ruby method declaration, and the lineno of the declaration for the cpp that is assigned to it. would this be helpful or just confusing in the rdoc to say, "App.cpp line 543"? - Provide actual link to cpp documentation on http://www.wxwidgets.org and correspond classes and methods to their actual correpsonding wxwidgets.org page (perhaps this would make the above idea go away?) - Add the ability for a developer to add comments to a third-party file which my script will read in and add to the documentation. Example (say a file, addondocs.txt): Class: App method: set_top_frame description=<<-"ENDMETHOD" set_top_frame can also be used in this manner. etc.... ENDMETHOD This would be done by running my script with a command line option or allowing the developer to manually enter information into the file, and it would check syntax of 'addondocs.txt'? I don't want to go overkill, but I want to really make these docs be all they can be. Nick, I'm taking guidance from you on this explicitly, so if you have any order or precedence for the docs, the template for rdoc, etc... just hollar. I dont' want to get stuck if it isn't in the spot you feel is most beneficial to the project. I plan to work throughout the week on it as I get time. The next few days I have my sister visiting and a funeral to go to so I'll do as much as I can, but it may not be much. =( Thanks you all for your feedback, it is encouraging and guiding all at the same time, and I'm excited to get this docs polished and out there for the community to use. Zach From melfstrand at maf.org Wed Feb 9 11:13:09 2005 From: melfstrand at maf.org (Marshall Elfstrand) Date: Wed Feb 9 11:09:51 2005 Subject: [Wxruby-users] New Docs - One Look and a Partial Glance In-Reply-To: <4209936E.5060003@mktec.com> References: <4209936E.5060003@mktec.com> Message-ID: <7cc3fe08782db7e898d2318b160228a1@maf.org> This is great, Zach! Thanks! Yes, the arguments and descriptions would be useful (including the expected type and default parameters). The only other thing I've noticed is that some of the docs (App.rb for example) jump between paragraph and preformatted text when it's supposed to be all one sentence, which is rather jarring. I gather that it's some strange indenting in the original docs, so I don't know how much that can be fixed up. Line numbers wouldn't help me personally, although linking to the C++ docs isn't a bad idea. Thank you again. This is going to make a world of difference in the usability of the API. Marshall On Feb 8, 2005, at 8:37 PM, Zach Dennis wrote: > Ok, same url as before: > > http://www.mktec.com/dev_www/wxruby-docs/ > > We aren't at the second look yet (because i dont' have arguments in > the docs yet), but that is coming. This fixes the bug where classes > after Image didn't have any docs, and this fixes the issue where many > methods weren't documented (like the class Frame). Now the only > methods that are not documented are those that don't have a > description. I was going to wait until it was all finished before > showing everyone, but I couldn't wait and I wanted to let the > community know I wasn't pulling their leg. And this way I can get > feedback before I get to far along with some of the ideas floating in > my head. > > Any more feedback you guys get would be great. Right now I've gathered: > - put arguments and descriptions in rdoc > - fix typo in header > - convert cpp names in documented source into actual links using the > ruby method, (ex: "WxApp::SetTopFrame" => "App::set_top_frame" ) > > I have some more possible ideas, but would like your feedback. I have > the following information and I am thinking of adding it into the > rdoc: > > - the lineno of the ruby method declaration, and the lineno of the > declaration for the cpp that is assigned to it. would this be helpful > or just confusing in the rdoc to say, "App.cpp line 543"? > > - Provide actual link to cpp documentation on > http://www.wxwidgets.org and correspond classes and methods to their > actual correpsonding wxwidgets.org page (perhaps this would make the > above idea go away?) > > - Add the ability for a developer to add comments to a third-party > file which my script will read in and add to the documentation. > Example (say a file, addondocs.txt): > Class: App > method: set_top_frame > description=<<-"ENDMETHOD" > set_top_frame can also be used in this manner. etc.... > ENDMETHOD > > This would be done by running my script with a command line option or > allowing the developer to manually enter information into the file, > and it would check syntax of 'addondocs.txt'? > > I don't want to go overkill, but I want to really make these docs be > all they can be. Nick, I'm taking guidance from you on this > explicitly, so if you have any order or precedence for the docs, the > template for rdoc, etc... just hollar. I dont' want to get stuck if it > isn't in the spot you feel is most beneficial to the project. > > I plan to work throughout the week on it as I get time. The next few > days I have my sister visiting and a funeral to go to so I'll do as > much as I can, but it may not be much. =( > > Thanks you all for your feedback, it is encouraging and guiding all at > the same time, and I'm excited to get this docs polished and out there > for the community to use. > > Zach > _______________________________________________ > wxruby-users mailing list > wxruby-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-users > From seanlong at smccabinets.com Wed Feb 9 12:12:29 2005 From: seanlong at smccabinets.com (Sean Long) Date: Wed Feb 9 12:09:14 2005 Subject: [Wxruby-users] New Docs - One Look and a Partial Glance In-Reply-To: <4209936E.5060003@mktec.com> Message-ID: <000001c50eca$8c59df90$0b00a8c0@SeansLaptop> Zach, The docs are looking great. When clicking around I came upon this in the BusyInfo class: wxBusyInfo wait("Please wait, working..."); for (int i = 0; i < 100000; i++) It looks like you need to replace " , < and > with " , < , > In the HTML code they are showing up as &quot; , &lt; and &gt; Keep up the good work. Sean Long -----Original Message----- From: wxruby-users-bounces@rubyforge.org [mailto:wxruby-users-bounces@rubyforge.org] On Behalf Of Zach Dennis Sent: Tuesday, February 08, 2005 8:37 PM To: General discussion of wxRuby Subject: [Wxruby-users] New Docs - One Look and a Partial Glance Ok, same url as before: http://www.mktec.com/dev_www/wxruby-docs/ We aren't at the second look yet (because i dont' have arguments in the docs yet), but that is coming. This fixes the bug where classes after Image didn't have any docs, and this fixes the issue where many methods weren't documented (like the class Frame). Now the only methods that are not documented are those that don't have a description. I was going to wait until it was all finished before showing everyone, but I couldn't wait and I wanted to let the community know I wasn't pulling their leg. And this way I can get feedback before I get to far along with some of the ideas floating in my head. Any more feedback you guys get would be great. Right now I've gathered: - put arguments and descriptions in rdoc - fix typo in header - convert cpp names in documented source into actual links using the ruby method, (ex: "WxApp::SetTopFrame" => "App::set_top_frame" ) I have some more possible ideas, but would like your feedback. I have the following information and I am thinking of adding it into the rdoc: - the lineno of the ruby method declaration, and the lineno of the declaration for the cpp that is assigned to it. would this be helpful or just confusing in the rdoc to say, "App.cpp line 543"? - Provide actual link to cpp documentation on http://www.wxwidgets.org and correspond classes and methods to their actual correpsonding wxwidgets.org page (perhaps this would make the above idea go away?) - Add the ability for a developer to add comments to a third-party file which my script will read in and add to the documentation. Example (say a file, addondocs.txt): Class: App method: set_top_frame description=<<-"ENDMETHOD" set_top_frame can also be used in this manner. etc.... ENDMETHOD This would be done by running my script with a command line option or allowing the developer to manually enter information into the file, and it would check syntax of 'addondocs.txt'? I don't want to go overkill, but I want to really make these docs be all they can be. Nick, I'm taking guidance from you on this explicitly, so if you have any order or precedence for the docs, the template for rdoc, etc... just hollar. I dont' want to get stuck if it isn't in the spot you feel is most beneficial to the project. I plan to work throughout the week on it as I get time. The next few days I have my sister visiting and a funeral to go to so I'll do as much as I can, but it may not be much. =( Thanks you all for your feedback, it is encouraging and guiding all at the same time, and I'm excited to get this docs polished and out there for the community to use. Zach _______________________________________________ wxruby-users mailing list wxruby-users@rubyforge.org http://rubyforge.org/mailman/listinfo/wxruby-users From devel at nicreations.com Wed Feb 9 23:42:37 2005 From: devel at nicreations.com (Nick) Date: Wed Feb 9 23:41:57 2005 Subject: [Wxruby-users] New Docs - One Look and a Partial Glance In-Reply-To: <4209936E.5060003@mktec.com> References: <4209936E.5060003@mktec.com> Message-ID: <420AE63D.4050500@nicreations.com> > Nick, I'm taking guidance from you on this explicitly, so > if you have any order or precedence for the docs, the template for rdoc, > etc... just hollar. I dont' want to get stuck if it isn't in the spot > you feel is most beneficial to the project. I think you know what's easiest at this point. I'll go through what's listed... > - put arguments and descriptions in rdoc This is pretty high up there. > - fix typo in header When you can fix it, fix it. > - convert cpp names in documented source into actual links using the > ruby method, (ex: "WxApp::SetTopFrame" => "App::set_top_frame" ) That doesn't bother me too much; it's something that could be corrected later (see below) > - the lineno of the ruby method declaration, and the lineno of the > declaration for the cpp that is assigned to it. would this be helpful or > just confusing in the rdoc to say, "App.cpp line 543"? I think this would be confusing. > - Provide actual link to cpp documentation on http://www.wxwidgets.org > and correspond classes and methods to their actual correpsonding > wxwidgets.org page (perhaps this would make the above idea go away?) If the XML has that information, it would be helpful, but don't break your back on it. > - Add the ability for a developer to add comments to a third-party > file which my script will read in and add to the documentation. > Example (say a file, addondocs.txt): > Class: App > method: set_top_frame > description=<<-"ENDMETHOD" > set_top_frame can also be used in this manner. etc.... > ENDMETHOD This is important to me. My personal dream would be to enable some sort of Wiki system on the docs, but that would take a ton of work. Really, some way for developers to edit the documentation is necessary, because the XML will have errors. (Making a documentation editor might be a good wxruby project...) Other than that, my only issues are rdoc issues - why are all methods of the system listed? Why are all files listed? Why are those things at the top? My personal preference would be to stick the class list on the side, and leave the other two off. But that may start a holy war. Once again, great work Zach. Nick Zach Dennis wrote: > Ok, same url as before: > > http://www.mktec.com/dev_www/wxruby-docs/ > > We aren't at the second look yet (because i dont' have arguments in the > docs yet), but that is coming. This fixes the bug where classes after > Image didn't have any docs, and this fixes the issue where many methods > weren't documented (like the class Frame). Now the only methods that are > not documented are those that don't have a description. I was going to > wait until it was all finished before showing everyone, but I couldn't > wait and I wanted to let the community know I wasn't pulling their leg. > And this way I can get feedback before I get to far along with some of > the ideas floating in my head. > > Any more feedback you guys get would be great. Right now I've gathered: > - put arguments and descriptions in rdoc > - fix typo in header > - convert cpp names in documented source into actual links using the > ruby method, (ex: "WxApp::SetTopFrame" => "App::set_top_frame" ) > > I have some more possible ideas, but would like your feedback. I have > the following information and I am thinking of adding it into the rdoc: > > - the lineno of the ruby method declaration, and the lineno of the > declaration for the cpp that is assigned to it. would this be helpful or > just confusing in the rdoc to say, "App.cpp line 543"? > > - Provide actual link to cpp documentation on http://www.wxwidgets.org > and correspond classes and methods to their actual correpsonding > wxwidgets.org page (perhaps this would make the above idea go away?) > > - Add the ability for a developer to add comments to a third-party > file which my script will read in and add to the documentation. > Example (say a file, addondocs.txt): > Class: App > method: set_top_frame > description=<<-"ENDMETHOD" > set_top_frame can also be used in this manner. etc.... > ENDMETHOD > > This would be done by running my script with a command line option or > allowing the developer to manually enter information into the file, and > it would check syntax of 'addondocs.txt'? > > I don't want to go overkill, but I want to really make these docs be all > they can be. Nick, I'm taking guidance from you on this explicitly, so > if you have any order or precedence for the docs, the template for rdoc, > etc... just hollar. I dont' want to get stuck if it isn't in the spot > you feel is most beneficial to the project. > > I plan to work throughout the week on it as I get time. The next few > days I have my sister visiting and a funeral to go to so I'll do as much > as I can, but it may not be much. =( > > Thanks you all for your feedback, it is encouraging and guiding all at > the same time, and I'm excited to get this docs polished and out there > for the community to use. > > Zach > _______________________________________________ > wxruby-users mailing list > wxruby-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-users > > > From jani at email.ro Sun Feb 13 17:23:42 2005 From: jani at email.ro (jani) Date: Mon Feb 14 06:39:33 2005 Subject: [Wxruby-users] Re: wxruby swig update In-Reply-To: <420305A6.7060904@nicreations.com> References: <420305A6.7060904@nicreations.com> Message-ID: > First he good news. wxruby-swig now compiles on Linux, Mac, and Windows > using wxWidgets 2.5. I just patched a bug with the paint method today, I compiled for 2.5 on linux and there's a problem. wxEntry's prototype has changed since 2.4 the first arg is int& instead of int, so trying to run an app complains because of the unknown symbol. ruby: relocation error: /usr/lib/ruby/1.8/wx.so: undefined symbol: _Z7wxEntryiPPc the latter should end in RiPPC (Reference to int instead of int) I changed it in src/App.c (quick hack, no clean #ifdefing on wxgtk version) and now apps start, but no fonts are displayed. I'll try to invesatigate why later. (wxruby:21972): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text() Jani From zdennis at mktec.com Mon Feb 14 08:43:35 2005 From: zdennis at mktec.com (Zach Dennis) Date: Mon Feb 14 08:40:11 2005 Subject: [Wxruby-users] Re: wxruby swig update In-Reply-To: References: <420305A6.7060904@nicreations.com> Message-ID: <4210AB07.7030102@mktec.com> jani wrote: > > First he good news. wxruby-swig now compiles on Linux, Mac, and Windows > >> using wxWidgets 2.5. I just patched a bug with the paint method today, > > > I compiled for 2.5 on linux and there's a problem. wxEntry's prototype > has changed since 2.4 the first arg is int& instead of int, so trying to > run an app complains because of the unknown symbol. > ruby: relocation error: /usr/lib/ruby/1.8/wx.so: undefined symbol: > _Z7wxEntryiPPc > > the latter should end in RiPPC (Reference to int instead of int) > I changed it in src/App.c (quick hack, no clean #ifdefing on wxgtk > version) and now apps start, but no fonts are displayed. I'll try to > invesatigate why later. > > (wxruby:21972): Pango-WARNING **: Invalid UTF-8 string passed to > pango_layout_set_text() I do remember Nick saying not to compile wxWindows with Unicode enabled, to use ASCII, on an off-list discussion we had. I hope I remember this correctly, if it doesn't sound right, ignore me, until Nick has a chance to respond. Thanks, Zach From devel at nicreations.com Tue Feb 15 00:21:23 2005 From: devel at nicreations.com (Nick) Date: Tue Feb 15 00:20:34 2005 Subject: [Wxruby-users] Re: wxruby swig update In-Reply-To: References: <420305A6.7060904@nicreations.com> Message-ID: <421186D3.6010902@nicreations.com> > the latter should end in RiPPC (Reference to int instead of int) > I changed it in src/App.c (quick hack, no clean #ifdefing on wxgtk > version) and now apps start, but no fonts are displayed. I'll try to > invesatigate why later. I actually spent a good part of the weekend trying to track down two missing references. I got the first one (what you refer to) fixed, but on my OS X 10.3 machine I get an exception on load because I have a reference to WebKit that doesn't exist. Did you see anything similar? Nick jani wrote: > > First he good news. wxruby-swig now compiles on Linux, Mac, and Windows > >> using wxWidgets 2.5. I just patched a bug with the paint method today, > > > I compiled for 2.5 on linux and there's a problem. wxEntry's prototype > has changed since 2.4 the first arg is int& instead of int, so trying to > run an app complains because of the unknown symbol. > ruby: relocation error: /usr/lib/ruby/1.8/wx.so: undefined symbol: > _Z7wxEntryiPPc > > the latter should end in RiPPC (Reference to int instead of int) > I changed it in src/App.c (quick hack, no clean #ifdefing on wxgtk > version) and now apps start, but no fonts are displayed. I'll try to > invesatigate why later. > > (wxruby:21972): Pango-WARNING **: Invalid UTF-8 string passed to > pango_layout_set_text() > > > Jani > > _______________________________________________ > wxruby-users mailing list > wxruby-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-users > > > From jani at iv.ro Tue Feb 15 04:33:43 2005 From: jani at iv.ro (Jani Monoses) Date: Tue Feb 15 04:31:08 2005 Subject: [Wxruby-users] Re: wxruby swig update In-Reply-To: <421186D3.6010902@nicreations.com> References: <420305A6.7060904@nicreations.com> <421186D3.6010902@nicreations.com> Message-ID: > I actually spent a good part of the weekend trying to track down two > missing references. I got the first one (what you refer to) fixed, but > on my OS X 10.3 machine I get an exception on load because I have a > reference to WebKit that doesn't exist. Did you see anything similar? No. I am using ubuntu with wxgtk2.5 compiled with unicode support and gtk2 The only thing after the programs could run was the pango warning I pasted and no text whatsoever in the controls :) What are the impediments of using an unicode enabled wx? Need to transform all wxChar uses to char? thanks Jani From devel at nicreations.com Tue Feb 15 11:33:52 2005 From: devel at nicreations.com (devel@nicreations.com) Date: Tue Feb 15 11:30:13 2005 Subject: [Wxruby-users] Re: wxruby swig update Message-ID: <200502151633.j1FGXms26155@BIGDIPPER.wyith.com> > No. I am using ubuntu with wxgtk2.5 compiled with unicode support and gtk2 > The only thing after the programs could run was the pango warning I pasted > and no text whatsoever in the controls :) > What are the impediments of using an unicode enabled wx? Need to transform > all wxChar uses > to char? Ruby appears to use const char * for all of it's string work (which completely caught me off guard, because it is a Japanese scripting language). It may be that I'm just not using a UNICODE build of Ruby, but I don't think most of the binary releases are. Right now I'm just casting the output strings to wxChar * (I know - bad! bad!), but I'd ask not to use wxWidgets in UNICODE for building wxRuby until this is resolved. Nick From wxruby at qualitycode.com Tue Feb 15 19:35:16 2005 From: wxruby at qualitycode.com (Kevin Smith) Date: Tue Feb 15 19:31:53 2005 Subject: [Wxruby-users] Unicode (was: wxruby swig update) In-Reply-To: <200502151633.j1FGXms26155@BIGDIPPER.wyith.com> References: <200502151633.j1FGXms26155@BIGDIPPER.wyith.com> Message-ID: <42129544.4050604@qualitycode.com> devel@nicreations.com wrote: > Ruby appears to use const char * for all of it's string work (which > completely caught me off guard, because it is a Japanese scripting > language). When I looked into unicode support with wxRuby a couple years ago, I had a similar reaction. I also chose to postpone dealing with it. Hopefully a straightforward solution will present itself at some point. Kevin From zdennis at mktec.com Thu Feb 17 16:24:57 2005 From: zdennis at mktec.com (Zach Dennis) Date: Thu Feb 17 16:21:23 2005 Subject: [Wxruby-users] New Docs - One Look and a Partial Glance In-Reply-To: <4209936E.5060003@mktec.com> References: <4209936E.5060003@mktec.com> Message-ID: <42150BA9.2080607@mktec.com> No need for anyone to reply to this, I just want to let you know I didn't fall off the face of the earth in the last week. Had a funeral last weekend you can imagine the types of neat family fun and emotions that involves. I will be back going this weekend on finishing my docs upgrades. thanks, Zach From devel at nicreations.com Fri Feb 18 10:27:44 2005 From: devel at nicreations.com (Nick) Date: Fri Feb 18 10:26:49 2005 Subject: [Wxruby-users] New Docs - One Look and a Partial Glance In-Reply-To: <42150BA9.2080607@mktec.com> References: <4209936E.5060003@mktec.com> <42150BA9.2080607@mktec.com> Message-ID: <42160970.4060506@nicreations.com> > No need for anyone to reply to this, I just want to let you know I > didn't fall off the face of the earth in the last week. Had a funeral > last weekend you can imagine the types of neat family fun and emotions > that involves. I will be back going this weekend on finishing my docs > upgrades. It's ok Zach - I just got hit with a bad case of the stomach flu, so my productivity has been shot. Nick Zach Dennis wrote: > No need for anyone to reply to this, I just want to let you know I > didn't fall off the face of the earth in the last week. Had a funeral > last weekend you can imagine the types of neat family fun and emotions > that involves. I will be back going this weekend on finishing my docs > upgrades. > > thanks, > > Zach > > _______________________________________________ > wxruby-users mailing list > wxruby-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-users > > > From devel at nicreations.com Sun Feb 20 18:42:18 2005 From: devel at nicreations.com (Nick) Date: Sun Feb 20 18:41:18 2005 Subject: [Wxruby-users] Suggestion for wxruby name change Message-ID: <4219205A.8070206@nicreations.com> We've had some discussion in the past about the wxruby vs wxruby-swig name, and how they are a bit confusing. My big problem with 'wxruby-swig' is that unless you know what 'swig' is, it's not a terribly useful (or sexy) postfix. It's like naming a car after it's manufacturing process - "the all new Acura NSX-smoke-burning-factory" just wouldn't sell cars. In the past, there was a good reason for the naming - one was supposed to replace the other quickly and silently. Well, that didn't happen as expected. However, wxruby-swig has gained two real features. First, as you hungry list followers have heard, Zach has been completly redoing our documentation system with Rubydoc. As much as I complain about the web-layout defaults of rubydoc, no one can deny that these will be a huge improvement over our original docs. Second, wxruby-swig now works with wxWidgets 2.5.3 (tested with both Mac OS X and Win32). Windows users won't be able to see much, but let me tell you (five) Mac OS X developers out there - It's a big improvement. This brings me to the point of the email - what if we we changed the names "wxruby / wxruby-swig" to "wxruby-2.4 / wxruby-2.5", after the version of wxWidgets they supported? To me this makes more sense than the 'swig' postfix, because it passes useful information. I'd like some discussion on this, because I'd like a proper name before this gets released. In closing, I'm really excited how wxruby-swig/2.5 is shaping up. It's one of the only GUI's for Ruby that really support Linux, Mac, and OS X well. Nick From curt at hibbs.com Sun Feb 20 18:54:10 2005 From: curt at hibbs.com (Curt Hibbs) Date: Sun Feb 20 18:50:27 2005 Subject: [Wxruby-users] Suggestion for wxruby name change In-Reply-To: <4219205A.8070206@nicreations.com> Message-ID: I like it! Curt > -----Original Message----- > From: wxruby-users-bounces@rubyforge.org > [mailto:wxruby-users-bounces@rubyforge.org]On Behalf Of Nick > Sent: Sunday, February 20, 2005 5:42 PM > To: General discussion of wxRuby > Subject: [Wxruby-users] Suggestion for wxruby name change > > > > We've had some discussion in the past about the wxruby vs wxruby-swig > name, and how they are a bit confusing. My big problem with > 'wxruby-swig' is that unless you know what 'swig' is, it's not a > terribly useful (or sexy) postfix. It's like naming a car after it's > manufacturing process - "the all new Acura NSX-smoke-burning-factory" > just wouldn't sell cars. > > In the past, there was a good reason for the naming - one was supposed > to replace the other quickly and silently. Well, that didn't happen as > expected. However, wxruby-swig has gained two real features. First, as > you hungry list followers have heard, Zach has been completly redoing > our documentation system with Rubydoc. As much as I complain about the > web-layout defaults of rubydoc, no one can deny that these will be a > huge improvement over our original docs. Second, wxruby-swig now works > with wxWidgets 2.5.3 (tested with both Mac OS X and Win32). Windows > users won't be able to see much, but let me tell you (five) Mac OS X > developers out there - It's a big improvement. > > This brings me to the point of the email - what if we we changed the > names "wxruby / wxruby-swig" to "wxruby-2.4 / wxruby-2.5", after the > version of wxWidgets they supported? To me this makes more sense than > the 'swig' postfix, because it passes useful information. I'd like some > discussion on this, because I'd like a proper name before this gets > released. > > In closing, I'm really excited how wxruby-swig/2.5 is shaping up. It's > one of the only GUI's for Ruby that really support Linux, Mac, and OS X > well. > > Nick > _______________________________________________ > wxruby-users mailing list > wxruby-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-users > > -- > No virus found in this incoming message. > Checked by AVG Anti-Virus. > Version: 7.0.300 / Virus Database: 266.1.0 - Release Date: 2/18/2005 > From wxruby at qualitycode.com Sun Feb 20 19:28:33 2005 From: wxruby at qualitycode.com (Kevin Smith) Date: Sun Feb 20 19:24:56 2005 Subject: [Wxruby-users] Suggestion for wxruby name change In-Reply-To: <4219205A.8070206@nicreations.com> References: <4219205A.8070206@nicreations.com> Message-ID: <42192B31.5020605@qualitycode.com> Nick wrote: > In the past, there was a good reason for the naming - one was supposed > to replace the other quickly and silently. Well, that didn't happen as > expected. ...or hasn't happened _yet_. Well, I suppose the "quickly and silently" bit is hopeless, but the "replace" could still happen. How far are we from saying that the swig version of wxruby is THE main, supported version? > This brings me to the point of the email - what if we we changed the > names "wxruby / wxruby-swig" to "wxruby-2.4 / wxruby-2.5", after the > version of wxWidgets they supported? I don't really like this, partly because of the possible confusion when wxWidgets 2.6 is released. > To me this makes more sense than the 'swig' postfix, Yes, clearly. wxruby-swig was really intended to be an internal name, and not the public project name. Perhaps wxruby-swig should become wxruby-2.0? Or perhaps wxruby should be renamed to wxruby-legacy? Those are my thoughts, but it's definitely your decision. Kevin From sdate at everestkc.net Sun Feb 20 19:44:57 2005 From: sdate at everestkc.net (Shashank Date) Date: Sun Feb 20 19:41:18 2005 Subject: [Wxruby-users] Suggestion for wxruby name change In-Reply-To: <4219205A.8070206@nicreations.com> References: <4219205A.8070206@nicreations.com> Message-ID: <42192F09.9000400@everestkc.net> Hi, Nick wrote: > It's like naming a car after it's manufacturing process - "the all > new Acura NSX-smoke-burning-factory" just wouldn't sell cars. LOL ! > In the past, there was a good reason for the naming - one was supposed > to replace the other quickly and silently. Well, that didn't happen as > expected. However, wxruby-swig has gained two real features. First, as > you hungry list followers have heard, Zach has been completly redoing > our documentation system with Rubydoc. As much as I complain about the > web-layout defaults of rubydoc, no one can deny that these will be a > huge improvement over our original docs. No denying that ! Terrific work, Zach! > Second, wxruby-swig now works with wxWidgets 2.5.3 (tested with both > Mac OS X and Win32). Windows users won't be able to see much, but let > me tell you (five) Mac OS X developers out there - It's a big > improvement. > > This brings me to the point of the email - what if we we changed the > names "wxruby / wxruby-swig" to "wxruby-2.4 / wxruby-2.5", after the > version of wxWidgets they supported? To me this makes more sense than > the 'swig' postfix, because it passes useful information. I'd like > some discussion on this, because I'd like a proper name before this > gets released. I do not see any compelling reason to change the name. Of course, non-swig to swig is a big jump and we can denote that by setting the version to 1.0 (or even 2.0 as Kevin suggested). But the name can still stay simply wxRuby. Just my $0.02. > In closing, I'm really excited how wxruby-swig/2.5 is shaping up. It's > one of the only GUI's for Ruby that really support Linux, Mac, and OS > X well. We all share your excitement. > Nick Thanks, -- shanko From zdennis at mktec.com Sun Feb 20 20:43:50 2005 From: zdennis at mktec.com (Zach Dennis) Date: Sun Feb 20 20:44:41 2005 Subject: [Wxruby-users] Suggestion for wxruby name change In-Reply-To: <4219205A.8070206@nicreations.com> References: <4219205A.8070206@nicreations.com> Message-ID: <42193CD6.2030709@mktec.com> Nick wrote: > > We've had some discussion in the past about the wxruby vs wxruby-swig > name, and how they are a bit confusing. My big problem with > 'wxruby-swig' is that unless you know what 'swig' is, it's not a > terribly useful (or sexy) postfix. It's like naming a car after it's > manufacturing process - "the all new Acura NSX-smoke-burning-factory" > just wouldn't sell cars. I agree. > In the past, there was a good reason for the naming - one was supposed > > to replace the other quickly and silently. Well, that didn't happen as > expected. However, wxruby-swig has gained two real features. First, as > you hungry list followers have heard, Zach has been completly redoing > our documentation system with Rubydoc. As much as I complain about the > web-layout defaults of rubydoc, no one can deny that these will be a > huge improvement over our original docs. Second, wxruby-swig now works > with wxWidgets 2.5.3 (tested with both Mac OS X and Win32). Windows > users won't be able to see much, but let me tell you (five) Mac OS X > developers out there - It's a big improvement. I'm excited about wxRuby using wxWindows 2.5.3, as i'm sure others are. This is awesome for wxRuby on sooo many levels (wxWindows 2.5.x supports alpha transparency to!) > > This brings me to the point of the email - what if we we changed the > names "wxruby / wxruby-swig" to "wxruby-2.4 / wxruby-2.5", after the > version of wxWidgets they supported? To me this makes more sense than > the 'swig' postfix, because it passes useful information. I'd like some > discussion on this, because I'd like a proper name before this gets > released. I think naming wxRuby after the wxWindows version will be more confusing then helpful, since wxRuby will need it's own versioning to support its own features, compatibility with wxWindows and of course bug fixes, etc... but i agree about dropping the '-swig' postfix. > > In closing, I'm really excited how wxruby-swig/2.5 is shaping up. It's > one of the only GUI's for Ruby that really support Linux, Mac, and OS X > well. > I'm very excited as well, keep up the great work! Zach From devel at nicreations.com Sun Feb 20 22:30:33 2005 From: devel at nicreations.com (Nick) Date: Sun Feb 20 22:29:34 2005 Subject: [Wxruby-users] Suggestion for wxruby name change In-Reply-To: <42192B31.5020605@qualitycode.com> References: <4219205A.8070206@nicreations.com> <42192B31.5020605@qualitycode.com> Message-ID: <421955D9.1040007@nicreations.com> > How far are we from saying that the swig version of wxruby is THE main, > supported version? That's not really the issue - the issue is "when is a good time to get a binary built for people to try?" What has been holding that up is feature creep on the Mac OS X side. First, the issue was that wxruby-swig didn't work with ruby 1.6.8 which is the ruby installed by default on the Mac. Because of this there really wasn't a way to make a generic "installer" for the Mac (who are you installing for? Where is the distro?) so I changed gears and tried to make it into a Mac OS X "framework" that could be installed, hoping the stub library that would connect to it would work against all rubies (quick answer: no, its never that easy). At that point, the list "voted" that wxruby-swig needed to support wxWidgets 2.5, so once again I had to take on new development. In the meantime, I told Zach to begin working on the new docs for wxruby-swig. Just today I've gotten the Mac OS X build to link and run off the wxwidgets 2.5 library. As far as the original problem of installers on Mac OS X, the two main "binary ruby maintainers" on the Mac (Fink and Darwinports) have both said they would provide wxruby in packages for their distros. I conclude that they provide installers for their users, and anybody else on the Mac needs to build it from source because if they're using ruby 1.8 on the Mac they had to build it from source in the first place. Zach's docs are making progress, and are a definite improvement. I know I should have put out a Linux/Win32 binary build out for people to test (since thats the majority of our downloads), but when we lost you we lost our main Linux developer, and I was not in a position to handle bug requests on the Win32/Linux side and do the necessary Mac OS X development (and start a new job...). So now my goal is to tune up wxruby-swig and let Zach get the documentation ready, and release a test version to the masses. As far as being *the* version - experience tells me the migration won't be without bumps. I've ported a lot of the classes, but I know I'm missing somebody's favorite control/class and all this infrastructure work has taken time away from the addition of classes. The Layout classes are currently not functioning which I need to investigate (I was always more of an XRC fan, so it hasn't been a high priority). And some people may just like the old widgets. Change never comes without friction. > I don't really like this, partly because of the possible confusion when > wxWidgets 2.6 is released. Really, I see this as a naming scheme for the binaries. So our released files would be wxruby-2.4-src-0.7.tar.gz wxruby-2.4-msw-0.7.exe wxruby-2.4-osx-panther-0.7.dmg wxruby-2.5-src-0.1.tar.gz wxruby-2.5-msw-0.1.exe wxruby-2.5-osx-panther-0.1.dmg Some comments. First, the current tree would "stick around", possibly until downloads for the new surpass downloads for the old. It does require keeping up maintenance on the old tree. However, there are many good reasons to do so. First, the old tree supports more systems (Free BSD, MinGW) than the new one does, and it will for a long time. Second, the old tree has been tested and passed over a lot more eyes than the new system has. About the "dual version numbers" - yeah, I dunno about that. It's confusing, I'll admit. I think it's clearer to wxWidgets users, but scarier to ruby users. > Perhaps wxruby-swig should become wxruby-2.0? Or perhaps wxruby should > be renamed to wxruby-legacy? To me, "legacy" = "less", and the current tree is still more battle tested. Same with 2.0 on wxruby-swig - it suggests it's the superior version, which it won't be until the migration is done. Nick Kevin Smith wrote: > Nick wrote: > >> In the past, there was a good reason for the naming - one was supposed >> to replace the other quickly and silently. Well, that didn't happen as >> expected. > > > ...or hasn't happened _yet_. Well, I suppose the "quickly and silently" > bit is hopeless, but the "replace" could still happen. > > How far are we from saying that the swig version of wxruby is THE main, > supported version? > >> This brings me to the point of the email - what if we we changed the >> names "wxruby / wxruby-swig" to "wxruby-2.4 / wxruby-2.5", after the >> version of wxWidgets they supported? > > > I don't really like this, partly because of the possible confusion when > wxWidgets 2.6 is released. > >> To me this makes more sense than the 'swig' postfix, > > > Yes, clearly. wxruby-swig was really intended to be an internal name, > and not the public project name. > > Perhaps wxruby-swig should become wxruby-2.0? Or perhaps wxruby should > be renamed to wxruby-legacy? > > Those are my thoughts, but it's definitely your decision. > > Kevin > _______________________________________________ > wxruby-users mailing list > wxruby-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-users > > > From jani at iv.ro Mon Feb 21 06:34:24 2005 From: jani at iv.ro (Jani Monoses) Date: Mon Feb 21 06:30:24 2005 Subject: [Wxruby-users] Re: Suggestion for wxruby name change In-Reply-To: <4219205A.8070206@nicreations.com> References: <4219205A.8070206@nicreations.com> Message-ID: > This brings me to the point of the email - what if we we changed the > names "wxruby / wxruby-swig" to "wxruby-2.4 / wxruby-2.5", after the > version of wxWidgets they supported? To me this makes more sense than > the 'swig' postfix, because it passes useful information. I'd like some > discussion on this, because I'd like a proper name before this gets > released. > Hello I intend to package wxruby (both versions) for ubuntu/debian and was about to ask something similar :) . FWIW the packages providing python bindings are named after the wxgtk versions there so 2.4 and 2.5.3 right now. I too would vote for dropping -swig from the name. But would wxruby-swig only support wx >=2.5? If it built against both versions of wx then calling it wxruby-2.5 would be confusing. maybe instead of naming the old wxruby-legacy the new could be wxruby-ng? Equally subjective, but still preferable to -legacy IMHO Jani From curt at hibbs.com Mon Feb 21 07:08:45 2005 From: curt at hibbs.com (Curt Hibbs) Date: Mon Feb 21 07:04:59 2005 Subject: [Wxruby-users] Suggestion for wxruby name change In-Reply-To: <42192B31.5020605@qualitycode.com> Message-ID: Kevin Smith wrote: > > Nick wrote: > > In the past, there was a good reason for the naming - one was supposed > > to replace the other quickly and silently. Well, that didn't happen as > > expected. > > ...or hasn't happened _yet_. Well, I suppose the "quickly and silently" > bit is hopeless, but the "replace" could still happen. > > How far are we from saying that the swig version of wxruby is THE main, > supported version? > > > This brings me to the point of the email - what if we we changed the > > names "wxruby / wxruby-swig" to "wxruby-2.4 / wxruby-2.5", after the > > version of wxWidgets they supported? > > I don't really like this, partly because of the possible confusion when > wxWidgets 2.6 is released. > > > To me this makes more sense than the 'swig' postfix, > > Yes, clearly. wxruby-swig was really intended to be an internal name, > and not the public project name. > > Perhaps wxruby-swig should become wxruby-2.0? Or perhaps wxruby should > be renamed to wxruby-legacy? Interesting, that was precisely what I thought (the "legacy" part) as I was part way through reading Nick's email. Anyway, your approach sounds perfectly reasonable to me. Curt > Those are my thoughts, but it's definitely your decision. > > Kevin From zdennis at mktec.com Mon Feb 21 07:53:38 2005 From: zdennis at mktec.com (Zach Dennis) Date: Mon Feb 21 07:54:30 2005 Subject: [Wxruby-users] Suggestion for wxruby name change In-Reply-To: <421955D9.1040007@nicreations.com> References: <4219205A.8070206@nicreations.com> <42192B31.5020605@qualitycode.com> <421955D9.1040007@nicreations.com> Message-ID: <4219D9D2.5090608@mktec.com> Nick wrote: > > > Really, I see this as a naming scheme for the binaries. So our released > files would be > > wxruby-2.4-src-0.7.tar.gz > wxruby-2.4-msw-0.7.exe > wxruby-2.4-osx-panther-0.7.dmg > wxruby-2.5-src-0.1.tar.gz > wxruby-2.5-msw-0.1.exe > wxruby-2.5-osx-panther-0.1.dmg This seems reasonable to me, I was just thinking it'd be wxruby-2.5.3, or wxruby-2.6. I didn't realize the two sets of numbers in my first reply. Zach From wxruby at qualitycode.com Mon Feb 21 09:18:46 2005 From: wxruby at qualitycode.com (Kevin Smith) Date: Mon Feb 21 09:15:10 2005 Subject: [Wxruby-users] Re: Suggestion for wxruby name change In-Reply-To: References: <4219205A.8070206@nicreations.com> Message-ID: <4219EDC6.9060005@qualitycode.com> Jani Monoses wrote: > I too would vote for dropping -swig from the name. I think we are unanimous in that. > But would wxruby-swig only support wx >=2.5? If it built against both > versions of wx then calling it wxruby-2.5 would be confusing. That's a very good point. I can definitely imagine wxruby-swig being back-ported to wx 2.4 at some point. And, for that matter, if wxruby-swig doesn't become a superset of the older wxruby, the older codebase might be tweaked to work with wx 2.5. I think linking the wxruby version numbers to wx version numbers is risky, but might be workable. I think trying to do that *AND* to also use version numbers to distinguish between swig and non-swig codebases at the same time is just too confusing. > maybe instead of naming the old wxruby-legacy the new could be > wxruby-ng? Equally subjective, but still preferable to -legacy IMHO I guess I look forward to the day when wxruby (the legacy version) no longer exists. At that point, I would hope that the current, modern, working, supported version would simply be named 'wxruby'. I suppose that shift could happen when it's ready, but I would err on the side of renaming earlier rather than later, to try to steer people toward the swig version. That's one way to get more people working on it. Perhaps a compromise would be to rename wxruby to wxruby-1 and wxruby-swig to wxruby-2 or wxruby-ng. Then, when wxruby-1 no longer has any advantage over wxruby-ng, wxruby-ng could be renamed to just wxruby? Kevin From melfstrand at maf.org Mon Feb 21 15:00:48 2005 From: melfstrand at maf.org (Marshall Elfstrand) Date: Mon Feb 21 14:57:16 2005 Subject: [Wxruby-users] Suggestion for wxruby name change In-Reply-To: <421955D9.1040007@nicreations.com> References: <4219205A.8070206@nicreations.com> <42192B31.5020605@qualitycode.com> <421955D9.1040007@nicreations.com> Message-ID: <2e6b97d96f12c334f8357e46e10a3095@maf.org> On Feb 20, 2005, at 7:30 PM, Nick wrote: > Really, I see this as a naming scheme for the binaries. So our > released files would be > > wxruby-2.4-src-0.7.tar.gz > wxruby-2.4-msw-0.7.exe > wxruby-2.4-osx-panther-0.7.dmg > wxruby-2.5-src-0.1.tar.gz > wxruby-2.5-msw-0.1.exe > wxruby-2.5-osx-panther-0.1.dmg FWIW, I believe this is the scheme that wxPython uses, although they seem to have their normal version numbers incorporating the wxWidgets version as well (e.g. wxPython2.5-osx-ansi-2.5.3.1.dmg). wxPerl doesn't seem to have a consistent versioning scheme, but the help files are named: wxPerl-0.19-wx-2.4.2-docs. I think either one of these is good. wxruby2.5-src-0.1.tar.gz, or wxruby-0.1-wx2.5.3-src.tar.gz. The first seems to say, "this is a product known as wxruby 2.5, and it's the 0.1 version of it." The latter seems to say, "this is version 0.1 of wxruby, and it's built against wxWidgets 2.5.3". I'm leaning slightly toward the first, but I think they both have merits. Marshall From devel at nicreations.com Mon Feb 21 19:08:22 2005 From: devel at nicreations.com (Nick) Date: Mon Feb 21 19:07:25 2005 Subject: [Wxruby-users] Re: Suggestion for wxruby name change In-Reply-To: <4219EDC6.9060005@qualitycode.com> References: <4219205A.8070206@nicreations.com> <4219EDC6.9060005@qualitycode.com> Message-ID: <421A77F6.6080305@nicreations.com> > That's a very good point. I can definitely imagine wxruby-swig being > back-ported to wx 2.4 at some point. And, for that matter, if > wxruby-swig doesn't become a superset of the older wxruby, the older > codebase might be tweaked to work with wx 2.5. See, I don't see that happening, and here's why: while the older code can be made to support multiple wxWidgets versions via #ifdefs, wxruby-swig has to have the choose which library it is going to support at code-generation time. The generated code for 2.5 won't really work with 2.4, and vice versa, unless we limit wxruby-swig to the overlap of 2.4 and 2.5 (which is a huge limit). I really don't see a majority of the users learning the Rake build enviroment, and hence don't expect any but a few power users to ever be able to use wxruby-swig for 2.4 > I guess I look forward to the day when wxruby (the legacy version) no > longer exists. At that point, I would hope that the current, modern, > working, supported version would simply be named 'wxruby'. That will only happen when the new version is in all ways superior to the old, and even then it's questionable (See: Linux, Apache, PhP, Perl, Ruby...) I just want to know what a good naming scheme would be before I put this out. I guess I'm not a big fan of "2.0" or "next gen" because that usually goes with features (not "fatter code and less classes"). Since wxruby-swig has moved to support the more bleeding edge 2.5, it seems a more logical way to name it for new users. Nick Kevin Smith wrote: > Jani Monoses wrote: > >> I too would vote for dropping -swig from the name. > > > I think we are unanimous in that. > >> But would wxruby-swig only support wx >=2.5? If it built against both >> versions of wx then calling it wxruby-2.5 would be confusing. > > > That's a very good point. I can definitely imagine wxruby-swig being > back-ported to wx 2.4 at some point. And, for that matter, if > wxruby-swig doesn't become a superset of the older wxruby, the older > codebase might be tweaked to work with wx 2.5. > > I think linking the wxruby version numbers to wx version numbers is > risky, but might be workable. I think trying to do that *AND* to also > use version numbers to distinguish between swig and non-swig codebases > at the same time is just too confusing. > >> maybe instead of naming the old wxruby-legacy the new could be >> wxruby-ng? Equally subjective, but still preferable to -legacy IMHO > > > I guess I look forward to the day when wxruby (the legacy version) no > longer exists. At that point, I would hope that the current, modern, > working, supported version would simply be named 'wxruby'. I suppose > that shift could happen when it's ready, but I would err on the side of > renaming earlier rather than later, to try to steer people toward the > swig version. That's one way to get more people working on it. > > Perhaps a compromise would be to rename wxruby to wxruby-1 and > wxruby-swig to wxruby-2 or wxruby-ng. Then, when wxruby-1 no longer has > any advantage over wxruby-ng, wxruby-ng could be renamed to just wxruby? > > Kevin > _______________________________________________ > wxruby-users mailing list > wxruby-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-users > > > From zdennis at mktec.com Thu Feb 24 02:19:47 2005 From: zdennis at mktec.com (Zach Dennis) Date: Thu Feb 24 02:20:36 2005 Subject: [Wxruby-users] New Docs - One and Three Quarter Look Message-ID: <421D8013.1030503@mktec.com> Ok, the link: http://www.mktec.com/dev_www/wxrubydocs/ (try http://www.mktec.com/dev_www/wxruby-docs/ ,it does not work for me, although this is the actual directory, could you email me privately if this does/doesn't work for you, thx) Updates in this preview of the new docs: - a new RDOC template courtesty of Nick - fixed paragraph jumping and monospace text where it shouldn't be - added method arguments to rdoc output Things left to do yet: - Scan for cpp names and change them to the corresponding ruby names (for classes, method, etc..) in descriptive text, and in methods arguments - Allow developers to add comments to the documentation If you spot any bugs or things that look wrong please feel free to let me know. The docs will be added in the next release as well I do believe. Zach From melfstrand at maf.org Thu Feb 24 11:19:45 2005 From: melfstrand at maf.org (Marshall Elfstrand) Date: Thu Feb 24 11:15:55 2005 Subject: [Wxruby-users] New Docs - One and Three Quarter Look In-Reply-To: <421D8013.1030503@mktec.com> References: <421D8013.1030503@mktec.com> Message-ID: <7bc65fc87b143b8ed615cd837266d940@maf.org> That's awesome, Zach! I really like Nick's template; I agree that it's much easier to work with. A few things I noticed in the TextCtrl documentation: 1) There's still a line in the class docs for TextCtrl that is monospaced and separated where it shouldn't be. 2) There are some formatting codes still in there, like $\, $r, $n, \pythonnote{}, \perlnote{} 3) The code samples in the class docs don't appear at all. Not sure if this is intentional. I wonder if there might be a way of marking/identifying the code samples and having some way of replacing them with the equivalent Ruby code that one of us would write? Like maybe have some extra code samples file that it uses to replace the C++ code. Minor aesthetic note: the description at the top says: "This class documentation has automatically generated" -- should this be "was automatically generated"? Thanks so much for your work on this. It's a huge help, and it's looking great! Marshall On Feb 23, 2005, at 11:19 PM, Zach Dennis wrote: > Ok, the link: > > http://www.mktec.com/dev_www/wxrubydocs/ > > (try http://www.mktec.com/dev_www/wxruby-docs/ ,it does not work for > me, although this is the actual directory, could you email me > privately if this does/doesn't work for you, thx) > > Updates in this preview of the new docs: > - a new RDOC template courtesty of Nick > - fixed paragraph jumping and monospace text where it shouldn't be > - added method arguments to rdoc output > > Things left to do yet: > - Scan for cpp names and change them to the corresponding ruby names > (for classes, method, etc..) in descriptive text, and in methods > arguments > - Allow developers to add comments to the documentation > > If you spot any bugs or things that look wrong please feel free to let > me know. The docs will be added in the next release as well I do > believe. > > Zach > _______________________________________________ > wxruby-users mailing list > wxruby-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-users > From melfstrand at maf.org Thu Feb 24 12:05:02 2005 From: melfstrand at maf.org (Marshall Elfstrand) Date: Thu Feb 24 12:01:14 2005 Subject: [Wxruby-users] New Docs - One and Three Quarter Look In-Reply-To: <421D8013.1030503@mktec.com> References: <421D8013.1030503@mktec.com> Message-ID: Some more things I've noticed as I'm browsing: 1) The new() methods don't currently have arguments or a description 2) The docs for methods don't currently include the documentation for what the parameters mean or what the return value is 3) The docs for methods don't include the default value for arguments that have defaults (see Bitmap#save_file for example) 4) The class docs for controls (e.g. TextCtrl) don't include the window style or event handling sections. 5) The "In" and "Parent" lines at the top of each file aren't really useful (especially Parent since it always says Object). There should probably be a "Derived From" list like the WxWidgets docs instead. One thing that's much more of a feature request than a bug report: neither rdoc-generated docs nor the original WxWidgets docs list the methods that are defined by parent classes. If I want to see all of the methods a given class supports, I have to manually click on every link for every parent class and every mix-in. This is one thing I really miss from Javadoc. If there were a way to list all the methods the class supports (perhaps in a section that links them to the parent class's documentation, a la Javadoc), that would be a huge help. Thanks again! Marshall On Feb 23, 2005, at 11:19 PM, Zach Dennis wrote: > Ok, the link: > > http://www.mktec.com/dev_www/wxrubydocs/ > > (try http://www.mktec.com/dev_www/wxruby-docs/ ,it does not work for > me, although this is the actual directory, could you email me > privately if this does/doesn't work for you, thx) > > Updates in this preview of the new docs: > - a new RDOC template courtesty of Nick > - fixed paragraph jumping and monospace text where it shouldn't be > - added method arguments to rdoc output > > Things left to do yet: > - Scan for cpp names and change them to the corresponding ruby names > (for classes, method, etc..) in descriptive text, and in methods > arguments > - Allow developers to add comments to the documentation > > If you spot any bugs or things that look wrong please feel free to let > me know. The docs will be added in the next release as well I do > believe. > > Zach > _______________________________________________ > wxruby-users mailing list > wxruby-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-users > From zdennis at mktec.com Thu Feb 24 12:19:22 2005 From: zdennis at mktec.com (Zach Dennis) Date: Thu Feb 24 12:15:31 2005 Subject: [Wxruby-users] New Docs - One and Three Quarter Look In-Reply-To: References: <421D8013.1030503@mktec.com> Message-ID: <421E0C9A.4090405@mktec.com> Marshall Elfstrand wrote: > Some more things I've noticed as I'm browsing: > > 1) The new() methods don't currently have arguments or a description Ah yes, right now I'm just matching ruby methods to wx methods. I am not taking into account new() though with the constructor to the corresponding wx class. I will change this behavior to work how you mentioned. > 2) The docs for methods don't currently include the documentation for > what the parameters mean or what the return value is Yes, I haven't done anything with return values yet. And I am not display argument decscriptions because i was having rdoc formatting issues. There does not seem to be any good rdoc documentation anywhere online which doesn't help either. > 3) The docs for methods don't include the default value for arguments > that have defaults (see Bitmap#save_file for example) Yes I see what you're saying. I will add this as well. > 4) The class docs for controls (e.g. TextCtrl) don't include the window > style or event handling sections. Yep, I see this to. I'll look into why it's not being included and get it added. This may be another part though where there is rdoc formatting problems. If anyone is knowledgable in rdoc can assist I'd love to IRC or IM with you for just a few minutes one of these days! > 5) The "In" and "Parent" lines at the top of each file aren't really > useful (especially Parent since it always says Object). There should > probably be a "Derived From" list like the WxWidgets docs instead. This is generic rdoc thing. I'm sure we can change this in the template, but I don't know who we're going for more, wxwindows programmers using ruby, or ruby programmers using wxruby? Consistency across other ruby libs use In/Parent. > > One thing that's much more of a feature request than a bug report: > neither rdoc-generated docs nor the original WxWidgets docs list the > methods that are defined by parent classes. If I want to see all of the > methods a given class supports, I have to manually click on every link > for every parent class and every mix-in. This is one thing I really > miss from Javadoc. If there were a way to list all the methods the > class supports (perhaps in a section that links them to the parent > class's documentation, a la Javadoc), that would be a huge help. I'll start pondering this in my mind, and keep you posted if i come up with a viable solution =) Thanks for the time you took to give this feedback, Zach From melfstrand at maf.org Thu Feb 24 12:50:42 2005 From: melfstrand at maf.org (Marshall Elfstrand) Date: Thu Feb 24 12:46:51 2005 Subject: [Wxruby-users] New Docs - One and Three Quarter Look In-Reply-To: <421E0C9A.4090405@mktec.com> References: <421D8013.1030503@mktec.com> <421E0C9A.4090405@mktec.com> Message-ID: <1a8d7a3d919d7c4eb24a7c44829324db@maf.org> On Feb 24, 2005, at 9:19 AM, Zach Dennis wrote: >> 5) The "In" and "Parent" lines at the top of each file aren't really >> useful (especially Parent since it always says Object). There should >> probably be a "Derived From" list like the WxWidgets docs instead. > > This is generic rdoc thing. I'm sure we can change this in the > template, but I don't know who we're going for more, wxwindows > programmers using ruby, or ruby programmers using wxruby? Consistency > across other ruby libs use In/Parent. I would guess the audience is ruby programmers using wxruby (thus the desire for rdoc-style docs). I was just thinking that currently the "In" field references a stub file -- as opposed to a source file that one could refer to for the inner workings of a method -- and the "Parent" field always says Object, which isn't really accurate in terms of how the class functions. If there's a way of making these fields provide helpful information, great! I just figured it would be easier to drop in the "Derived From" list from the WxWidgets docs. I suppose the "In" field could list both the WxWidgets source file and the wxruby source file, kind of like how the Array class lists multiple files in the core rdoc for the Ruby language. I don't know how difficult it is to do this in rdoc though. Thanks! Marshall From devel at nicreations.com Thu Feb 24 14:34:27 2005 From: devel at nicreations.com (Nick) Date: Thu Feb 24 14:29:23 2005 Subject: [Wxruby-users] New Docs - One and Three Quarter Look Message-ID: Nice work Zach. If you want, I can dig out the cpp name => ruby name out of extractxml.rb for you. I know that we also have a giant ruby hash table of object parents if that would be useful. Do you know what rdoc uses to select it's first page - can it be something like a README? It would be nice to have a pretty first page. Once again, looking great. Nick > Ok, the link: > > http://www.mktec.com/dev_www/wxrubydocs/ > > (try http://www.mktec.com/dev_www/wxruby-docs/ ,it does not work for me, > although this is the actual directory, could you email me privately if > this does/doesn't work for you, thx) > > Updates in this preview of the new docs: > - a new RDOC template courtesty of Nick > - fixed paragraph jumping and monospace text where it shouldn't be > - added method arguments to rdoc output > > Things left to do yet: > - Scan for cpp names and change them to the corresponding ruby names > (for classes, method, etc..) in descriptive text, and in methods arguments > - Allow developers to add comments to the documentation > > If you spot any bugs or things that look wrong please feel free to let > me know. The docs will be added in the next release as well I do believe. > > Zach > _______________________________________________ > wxruby-users mailing list > wxruby-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-users > > -- From melfstrand at maf.org Thu Feb 24 15:43:13 2005 From: melfstrand at maf.org (Marshall Elfstrand) Date: Thu Feb 24 15:39:22 2005 Subject: [Wxruby-users] New Docs - One and Three Quarter Look In-Reply-To: References: Message-ID: <226b62cd987bbef10fec7374d3f0911e@maf.org> On Feb 24, 2005, at 11:34 AM, Nick wrote: > Do you know what rdoc uses to select it's first page - can it be > something like a README? It would be nice to have a pretty first page. rdoc can have a --main option specified that tells it which page to use as its start page, which could just be a readme file. Marshall From devel at nicreations.com Thu Feb 24 22:41:40 2005 From: devel at nicreations.com (Nick) Date: Thu Feb 24 22:40:35 2005 Subject: [Wxruby-users] New Docs - One and Three Quarter Look In-Reply-To: <421D8013.1030503@mktec.com> References: <421D8013.1030503@mktec.com> Message-ID: <421E9E74.2040809@nicreations.com> By the way, I was looking at the DC docs, and the method arguments appear to be in scrambled order. Nick Zach Dennis wrote: > Ok, the link: > > http://www.mktec.com/dev_www/wxrubydocs/ > > (try http://www.mktec.com/dev_www/wxruby-docs/ ,it does not work for me, > although this is the actual directory, could you email me privately if > this does/doesn't work for you, thx) > > Updates in this preview of the new docs: > - a new RDOC template courtesty of Nick > - fixed paragraph jumping and monospace text where it shouldn't be > - added method arguments to rdoc output > > Things left to do yet: > - Scan for cpp names and change them to the corresponding ruby names > (for classes, method, etc..) in descriptive text, and in methods arguments > - Allow developers to add comments to the documentation > > If you spot any bugs or things that look wrong please feel free to let > me know. The docs will be added in the next release as well I do believe. > > Zach > _______________________________________________ > wxruby-users mailing list > wxruby-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-users > > > From zdennis at mktec.com Thu Feb 24 22:53:17 2005 From: zdennis at mktec.com (Zach Dennis) Date: Thu Feb 24 22:54:05 2005 Subject: [Wxruby-users] New Docs - One and Three Quarter Look In-Reply-To: <421E9E74.2040809@nicreations.com> References: <421D8013.1030503@mktec.com> <421E9E74.2040809@nicreations.com> Message-ID: <421EA12D.2010903@mktec.com> Nick wrote: > > By the way, I was looking at the DC docs, and the method arguments > appear to be in scrambled order. > Yeah I noticed that tonight to. That is fixed now and I'll post another link here shortly (either tonight or in the morning) Zach From zdennis at mktec.com Thu Feb 24 23:01:58 2005 From: zdennis at mktec.com (Zach Dennis) Date: Thu Feb 24 23:02:46 2005 Subject: [Wxruby-users] New Docs - One and Three Quarter Look In-Reply-To: <421EA12D.2010903@mktec.com> References: <421D8013.1030503@mktec.com> <421E9E74.2040809@nicreations.com> <421EA12D.2010903@mktec.com> Message-ID: <421EA336.9030204@mktec.com> Ok another link: same one as before: http://www.mktec.com/dev_www/wxruby-docs/ -OR- http://www.mktec.com/dev_www/wxrubydocs/ Changes: - defaults values were added to argument lists - arguments lists are now in the correct order More to come tomorrow! Thanks for your patience, Zach From curt at hibbs.com Fri Feb 25 07:20:59 2005 From: curt at hibbs.com (Curt Hibbs) Date: Fri Feb 25 07:17:06 2005 Subject: [Wxruby-users] CVS for New Docs [was New Docs - One and Three Quarter Look] In-Reply-To: <421EA336.9030204@mktec.com> Message-ID: Great work Zach on all of this! At some appropriate point, you should check your doc tools in to CVS so that we have a secure (and official) copy of them. Curt > -----Original Message----- > From: wxruby-users-bounces@rubyforge.org > [mailto:wxruby-users-bounces@rubyforge.org]On Behalf Of Zach Dennis > Sent: Thursday, February 24, 2005 10:02 PM > To: General discussion of wxRuby > Subject: CVS for New Docs [was New Docs - One and Three Quarter Look] > > > Ok another link: same one as before: > > http://www.mktec.com/dev_www/wxruby-docs/ > -OR- > http://www.mktec.com/dev_www/wxrubydocs/ > > Changes: > - defaults values were added to argument lists > - arguments lists are now in the correct order > > More to come tomorrow! Thanks for your patience, > > Zach > _______________________________________________ > wxruby-users mailing list > wxruby-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-users > > -- > No virus found in this incoming message. > Checked by AVG Anti-Virus. > Version: 7.0.300 / Virus Database: 266.4.0 - Release Date: 2/22/2005 > From zdennis at mktec.com Fri Feb 25 09:52:00 2005 From: zdennis at mktec.com (Zach Dennis) Date: Fri Feb 25 09:48:06 2005 Subject: [Wxruby-users] CVS for New Docs [was New Docs - One and Three Quarter Look] In-Reply-To: References: Message-ID: <421F3B90.5040701@mktec.com> Curt Hibbs wrote: > Great work Zach on all of this! > > At some appropriate point, you should check your doc tools in to CVS so that > we have a secure (and official) copy of them. > I've been trying to hold out so I can clean up my code =). I'll check with Nick and see where he wants me to put them (i have more then 1 file). Zach From curt at hibbs.com Fri Feb 25 10:25:28 2005 From: curt at hibbs.com (Curt Hibbs) Date: Fri Feb 25 10:21:37 2005 Subject: [Wxruby-users] CVS for New Docs [was New Docs - One and ThreeQuarter Look] In-Reply-To: <421F3B90.5040701@mktec.com> Message-ID: Zach Dennis wrote: > > Curt Hibbs wrote: > > Great work Zach on all of this! > > > > At some appropriate point, you should check your doc tools in > to CVS so that > > we have a secure (and official) copy of them. > > > > I've been trying to hold out so I can clean up my code =). I'll check > with Nick and see where he wants me to put them (i have more then 1 file). Sure... I just wanted to mention this in case no had thought about it yet. Curt From alex at pressure.to Fri Feb 25 20:37:23 2005 From: alex at pressure.to (Alex Fenton) Date: Fri Feb 25 20:33:37 2005 Subject: [Wxruby-users] installing from src on OS X Message-ID: <421FD2D3.6090705@pressure.to> Hi I've built WxWidgets (2.5.4) and wxruby-swig (CVS) from source on OS X (.3). I've got something called wx.bundle in lib/ that looks the right sort of size - 2.5MB - but I don't know what to do with it to install it - no rake install or make install? btw - wx on OS X looks fantastic, esp after seeing a Tk interface inside Aqua this am ... cheers alex From devel at nicreations.com Fri Feb 25 21:19:42 2005 From: devel at nicreations.com (Nick) Date: Fri Feb 25 21:18:33 2005 Subject: [Wxruby-users] installing from src on OS X In-Reply-To: <421FD2D3.6090705@pressure.to> References: <421FD2D3.6090705@pressure.to> Message-ID: <421FDCBE.1070209@nicreations.com> You can copy that into /1.8/powerpc-darwinx.x/ - for example: /sw/lib/ruby/1.8/powerpc-darwin7.5.0/ Next time, go into the src directory and use the extconf.rb - it handles a lot of this for you. Nick Alex Fenton wrote: > Hi > > I've built WxWidgets (2.5.4) and wxruby-swig (CVS) from source on OS X > (.3). I've got something called wx.bundle in lib/ that looks the right > sort of size - 2.5MB - but I don't know what to do with it to install it > - no rake install or make install? > > btw - wx on OS X looks fantastic, esp after seeing a Tk interface inside > Aqua this am ... > > cheers > alex > _______________________________________________ > wxruby-users mailing list > wxruby-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-users > > > From zdennis at mktec.com Sat Feb 26 00:42:51 2005 From: zdennis at mktec.com (Zach Dennis) Date: Sat Feb 26 00:43:47 2005 Subject: [Wxruby-users] New Docs - One and Three Quarter Look In-Reply-To: References: <421D8013.1030503@mktec.com> Message-ID: <42200C5B.303@mktec.com> Marshall Elfstrand wrote: > Some more things I've noticed as I'm browsing: > > 1) The new() methods don't currently have arguments or a description working on this... > 2) The docs for methods don't currently include the documentation for > what the parameters mean or what the return value is working on this... > 3) The docs for methods don't include the default value for arguments > that have defaults (see Bitmap#save_file for example) done... > 4) The class docs for controls (e.g. TextCtrl) don't include the window > style or event handling sections. this is because i am parsing an xml file generated from the actual docs themselves, and the xml file includes a tag with this information. Each style has it's own