From sean.m.long at gmail.com Thu Oct 5 18:10:33 2006 From: sean.m.long at gmail.com (Sean Long) Date: Thu, 5 Oct 2006 15:10:33 -0700 Subject: [Wxruby-development] Testing to see if list working yet Message-ID: test Sean From wxruby at qualitycode.com Sat Oct 7 11:02:44 2006 From: wxruby at qualitycode.com (Kevin Smith) Date: Sat, 07 Oct 2006 11:02:44 -0400 Subject: [Wxruby-development] Welcome to wxruby-development Message-ID: <4527C194.4090209@qualitycode.com> This list is intended to be used by developers OF wxruby, to discuss highly technical internals, SWIG issues, the development process, and other topics that would not be of interest to folks who simply want to write an app that uses wxruby. Questions or comments about building or installing wxruby should probably go to the wxruby-users list. Questions about the API or runtime errors also should generally go to the wxruby-users list. Some feature roadmap discussions may be appropriate here, but most would likely be of interest to wxruby-users, so consider posting those to that list. But don't be shy about posting, whether to this list or the other. It is much more valuable to the project if you participate, and posting to the "wrong" list is still much better than not posting at all. This list will also receive automatic notifications whenever code is committed to the repository (Subversion, at the moment). Kevin From alex at pressure.to Thu Oct 12 04:57:28 2006 From: alex at pressure.to (Alex Fenton) Date: Thu, 12 Oct 2006 09:57:28 +0100 Subject: [Wxruby-development] announcement Message-ID: <452E0378.8090709@pressure.to> Hi Now we've got the download problems nailed, shall we do an announcement on comp.lang.ruby? I can do it if you're really busy, but Kevin I think you have first refusal as you're owed the biggest chunk of kudos for getting us this far. re patch backlog: no worries - just clearing the decks before having another go at integrating wxScintilla - but I can't see myself getting it to it til next week. cheers alex From wxruby at qualitycode.com Thu Oct 12 22:34:13 2006 From: wxruby at qualitycode.com (Kevin Smith) Date: Thu, 12 Oct 2006 22:34:13 -0400 Subject: [Wxruby-development] announcement In-Reply-To: <452E0378.8090709@pressure.to> References: <452E0378.8090709@pressure.to> Message-ID: <452EFB25.3000508@qualitycode.com> Alex Fenton wrote: > Now we've got the download problems nailed, shall we do an announcement > on comp.lang.ruby? I can do it if you're really busy, but Kevin I think > you have first refusal as you're owed the biggest chunk of kudos for > getting us this far. I would love to have a shot at proofreading the announcement, but I don't feel a need to author it, partly because I don't subscribe to c.l.r. More importantly, Alex, you are kind of the voice of the project right now, so it seems appropriate to come from you. I feel like somewhere between a figurehead and a guy in the shadows whispering advice to you guys who are doing the real work. I wish I could do more, but I'm really glad you all have stepped up. One of my requirements for any announcement is that within the first sentence, it has to explain what wxruby IS and why someone should care enough to keep reading. The project description on the rubyforge page is a pretty good starting point for that piece of it. Let's announce this thing. Kevin From wxruby at qualitycode.com Thu Oct 12 22:36:30 2006 From: wxruby at qualitycode.com (Kevin Smith) Date: Thu, 12 Oct 2006 22:36:30 -0400 Subject: [Wxruby-development] announcement In-Reply-To: <452E0378.8090709@pressure.to> References: <452E0378.8090709@pressure.to> Message-ID: <452EFBAE.4070207@qualitycode.com> > Now we've got the download problems nailed, shall we do an announcement > on comp.lang.ruby? Forgot to mention: We should post an announcement on rubyforge at the same time. You probably knew that, but just in case... Kevin From wxruby at qualitycode.com Thu Oct 12 22:40:46 2006 From: wxruby at qualitycode.com (Kevin Smith) Date: Thu, 12 Oct 2006 22:40:46 -0400 Subject: [Wxruby-development] List Reply vs. Reply-All Message-ID: <452EFCAE.5000701@qualitycode.com> It seems that the users list is set so Reply => Reply to the group, but this dev list defaulted to Reply => Reply only to the author. I know all the pros and cons of both approaches, but in this case I think the two lists should match, and nobody has complained (recently?) about the way users works. So I was about to flip this list to match it, and then re-read the warnings in the mailman admin interface, "strongly" recommending not replying to the group automatically. Strong opinions one way or the other? Should we change the way the users list works? Maybe now is the right time. Or maybe now is the wrong time. I'm not sure. Kevin From roys at mindspring.com Fri Oct 13 00:42:14 2006 From: roys at mindspring.com (Roy Sutton) Date: Fri, 13 Oct 2006 00:42:14 -0400 Subject: [Wxruby-development] [Wxruby-users] StdDialogButtonSizer In-Reply-To: <4522A7BA.3060308@pressure.to> References: <4522A7BA.3060308@pressure.to> Message-ID: <452F1926.7070407@mindspring.com> Alex Fenton wrote: > A set of extra files and a bigdemo sample patch to implement > StdDialogButtonSizer. > > Committed. Thanks Alex! (probably will see SVN commits soon) I'm just getting to understand svn so will probably be doing things a little funny until I get it all down pat. (Is there a way to assign a message to a file before you commit your changes?) Roy From roys at mindspring.com Fri Oct 13 01:12:07 2006 From: roys at mindspring.com (Roy Sutton) Date: Fri, 13 Oct 2006 01:12:07 -0400 Subject: [Wxruby-development] [Wxruby-users] DragImage In-Reply-To: <4521A0B9.5010002@pressure.to> References: <4521A0B9.5010002@pressure.to> Message-ID: <452F2027.5040304@mindspring.com> Alex Fenton wrote: > Attached a set of patches and new files to implement DragImage + > sample for bigdemo. > Alex, thanks for the patches. These do not compile cleanly on Windows. I haven't tested on Linux. Three functions (DoDrawImage, GetImageRect and UpdateBackingFromWindow) are only available to the Generic version. I guess Mac uses the generic DragImage. I may take a stab at fixing it before checking it in or you can re-submit the patch From roys at mindspring.com Fri Oct 13 03:02:10 2006 From: roys at mindspring.com (Roy Sutton) Date: Fri, 13 Oct 2006 03:02:10 -0400 Subject: [Wxruby-development] [Wxruby-users] DragImage In-Reply-To: <4521A0B9.5010002@pressure.to> References: <4521A0B9.5010002@pressure.to> Message-ID: <452F39F2.1090702@mindspring.com> Alex Fenton wrote: > Attached a set of patches and new files to implement DragImage + > sample for bigdemo. > > OK, I have this working on Windows now. I have removed the deprecated wxPoint argument in the constructors. I also fixed the demo so it will run and added some text to the background. It would be interesting to copy the wxPython sample over at some point. As soon as I get it all set I'll check it in. Roy From roys at mindspring.com Fri Oct 13 03:06:58 2006 From: roys at mindspring.com (Roy Sutton) Date: Fri, 13 Oct 2006 03:06:58 -0400 Subject: [Wxruby-development] rakewx Message-ID: <452F3B12.1000008@mindspring.com> With the recent check-in I accidentally committed my change to rakewx to remove the -fvirtual swig option. -fvirtual is incompatible with SWIG 1.3.30. It's not necessary (as I recall) for 1.3.29 but only reduces the size of the wrapper code slightly. If anyone feels strongly about this I can make it conditional on the SWIG version but simply removing it seems the safest and cleanest approach. Roy From roys at mindspring.com Fri Oct 13 03:17:19 2006 From: roys at mindspring.com (Roy Sutton) Date: Fri, 13 Oct 2006 03:17:19 -0400 Subject: [Wxruby-development] init_all_image_handlers Message-ID: <452F3D7F.1070800@mindspring.com> I removed all the calls to init_all_image_handlers from the samples since we invoke that internally now Roy From roys at mindspring.com Fri Oct 13 03:29:01 2006 From: roys at mindspring.com (Roy Sutton) Date: Fri, 13 Oct 2006 03:29:01 -0400 Subject: [Wxruby-development] Changelog and Docs Message-ID: <452F403D.4000008@mindspring.com> Updated the Changelog and the textile docs for DragImage Roy From alex at pressure.to Fri Oct 13 07:09:00 2006 From: alex at pressure.to (Alex Fenton) Date: Fri, 13 Oct 2006 12:09:00 +0100 Subject: [Wxruby-development] [Fwd: Re: List Reply vs. Reply-All] Message-ID: <452F73CC.2050105@pressure.to> See below, which I meant to send to group. A neat case in point ;) alex -------- Original Message -------- Subject: Re: [Wxruby-development] List Reply vs. Reply-All Date: Fri, 13 Oct 2006 12:07:04 +0100 From: Alex Fenton To: Kevin Smith References: <452EFCAE.5000701 at qualitycode.com> Kevin Smith wrote: > It seems that the users list is set so Reply => Reply to the group, but > this dev list defaulted to Reply => Reply only to the author. I know all > the pros and cons of both approaches, but in this case I think the two > lists should match, and nobody has complained (recently?) about the way > users works. So I was about to flip this list to match it, and then > re-read the warnings in the mailman admin interface, "strongly" > recommending not replying to the group automatically > Honestly, I've never understood why the mailman interface has such a dire warning against reply-to-group. I would prefer that the dev list was set to reply-to-group. thanks alex From roys at mindspring.com Fri Oct 13 10:58:28 2006 From: roys at mindspring.com (Roy Sutton) Date: Fri, 13 Oct 2006 10:58:28 -0400 Subject: [Wxruby-development] reply/reply all Message-ID: <452FA994.4000907@mindspring.com> The fact my reply never showed up is a good indicator that the default should be 'reply to list'. I had rambled about how I hate the SWIG list because I always reply wrongly. Roy From wxruby at qualitycode.com Fri Oct 13 14:40:18 2006 From: wxruby at qualitycode.com (Kevin Smith) Date: Fri, 13 Oct 2006 14:40:18 -0400 Subject: [Wxruby-development] List Reply vs. Reply-All In-Reply-To: <452EFCAE.5000701@qualitycode.com> References: <452EFCAE.5000701@qualitycode.com> Message-ID: <452FDD92.7040207@qualitycode.com> Kevin Smith wrote: > Strong opinions one way or the other? Should we change the way the users > list works? Maybe now is the right time. Or maybe now is the wrong time. > I'm not sure. Well, both Roy and Alex said they prefer replies to go to the group. Ironically, both of their replies came only to me and not to the list, whether intentional or not. I have flipped the dev list to match the users list and have replies go to the list. For the small dev list, especially, this seems appropriate. For a large list that covered sensitive topics (religion, sex) I might feel more strongly that the default should be a private reply. Anyway, it's done. Thanks for the input. Kevin From roys at mindspring.com Fri Oct 13 16:46:45 2006 From: roys at mindspring.com (Roy Sutton) Date: Fri, 13 Oct 2006 16:46:45 -0400 Subject: [Wxruby-development] rakewx In-Reply-To: <452FDE49.1000106@qualitycode.com> References: <452F3B12.1000008@mindspring.com> <452FDE49.1000106@qualitycode.com> Message-ID: <452FFB35.3020103@mindspring.com> Kevin Smith wrote [privately, but for the list, darn mailman]: > I think your change makes sense. Presumably at some point we will go > with 1.3.30 (after it is widely available), so we might as well get > compatible with it now. > Is the incompatibility something in our post-processing that we will > eventually be able to fix? Or is it a fundamental change. It is always > nice to have smaller code, where possible. It's a fundamental change to the way SWIG wraps directors. I'm actually surprised they didn't deprecate/disable -fvirtual since it's incompatible now. It is possible there's a situation where it works correctly I'm unaware of. Roy From roys at mindspring.com Sat Oct 14 03:28:57 2006 From: roys at mindspring.com (Roy Sutton) Date: Sat, 14 Oct 2006 03:28:57 -0400 Subject: [Wxruby-development] test.rb Message-ID: <453091B9.1080705@mindspring.com> Should the test.rb file in samples/ exist or was it added accidentally at some point? Roy From roys at mindspring.com Sat Oct 14 03:32:44 2006 From: roys at mindspring.com (Roy Sutton) Date: Sat, 14 Oct 2006 03:32:44 -0400 Subject: [Wxruby-development] Samples Message-ID: <4530929C.80403@mindspring.com> Updated all the sample files to add the shebang line and the require code we discussed. I also added the wxRuby copyright notice to all the samples I know I added (I may have missed some). Next, how about we rename all the .rbw files to .rb and update bigdemo? Roy From roys at mindspring.com Sat Oct 14 03:58:20 2006 From: roys at mindspring.com (Roy Sutton) Date: Sat, 14 Oct 2006 03:58:20 -0400 Subject: [Wxruby-development] run.rb Message-ID: <4530989C.7090601@mindspring.com> Patched run.rb to work with more of the samples. Should work for most all cases now. From alex at pressure.to Sat Oct 14 10:28:35 2006 From: alex at pressure.to (Alex Fenton) Date: Sat, 14 Oct 2006 15:28:35 +0100 Subject: [Wxruby-development] rakewx In-Reply-To: <452F3B12.1000008@mindspring.com> References: <452F3B12.1000008@mindspring.com> Message-ID: <4530F413.6030206@pressure.to> Roy Sutton wrote: > With the recent check-in I accidentally committed my change to rakewx to > remove the -fvirtual swig option. Seems like a good move to me, for the reasons you give. I just committed a change to restore swig_options as an empty string, b/c it is referenced and changed later in rakemacosx. alex From roys at mindspring.com Sat Oct 14 11:19:34 2006 From: roys at mindspring.com (Roy Sutton) Date: Sat, 14 Oct 2006 11:19:34 -0400 Subject: [Wxruby-development] Scintilla on Linux Message-ID: <45310006.1020608@mindspring.com> Well, I'm having some problems with Scintilla on Linux. I get the same 'uninitialized constant Wxruby2' when I try to compile in Scintilla. I will try changing the Scintilla options some more but it's very frustrating. I wish I got some sort of error message. It's like voodoo building on Linux. If it at least gave some error message it would be helpful. Roy From alex at pressure.to Sat Oct 14 12:27:00 2006 From: alex at pressure.to (Alex Fenton) Date: Sat, 14 Oct 2006 17:27:00 +0100 Subject: [Wxruby-development] announcement In-Reply-To: <452EFB25.3000508@qualitycode.com> References: <452E0378.8090709@pressure.to> <452EFB25.3000508@qualitycode.com> Message-ID: <45310FD4.8020509@pressure.to> Kevin Smith wrote: > I would love to have a shot at proofreading the announcement, but I > don't feel a need to author it, partly because I don't subscribe to > c.l.r. Cool - see a draft below. It's a bit long, but think it's worth it. Let me know if it looks OK, or send me revisions if needed. I follow c.l.r. via Usenet so can look out for feedback. Happy to post a rubyforge announce, but I don't currently have permissions to do that. Will follow it up with a wxSugar announce - I plan to tag and release a new version with some minor updates. alex --- wxRuby2 preview 0.0.36 has been released! wxRuby brings wxWidgets, a mature cross-platform GUI toolkit to Ruby. It uses native widgets on Windows, OS X and Linux/GTK; you can write GUI code once and still give users the look, feel and behaviour they expect from applications. = INSTALLING WXRUBY = Binary gems for major platforms and a source tarball are available at: http://rubyforge.org/frs/?group_id=35&release_id=7185 or via gems: gem install wxruby2-preview NB: this is an alpha-quality release, and is probably not yet stable enough for production use - but it's evolving quickly! Feedback, feature requests and bug reports are very welcome. All the packages come with a wide array of sample code to demonstrate how to use the library. Documentation is available online and can be downloaded for off-line reference. = WHAT'S NEW? = wxRuby2 is the result of a complete - and lengthy - re-engineering of an original port. Here's a few reasons why the wait's been worth it: * based on wxWidgets 2.6, giving vastly improved appearance on OS X and Linux * support for many new windows, controls and widgets * more complete API coverage within classes * unicode (UTF-8) support for creating multilingual apps * uses exceptions rather than segfaults to warn you about incorrect usage ;) * downloadable Ruby documentation * easier to extend and add C++ classes, by using SWIG * simpler and more permissive licence * binary gems for all major platforms = WHY WXRUBY? = There are several great GUI toolkits available for Ruby - but no other has all the features we like about wxRuby2: * cross-platform, with a wide selection of widgets * native widgets mean that applications look and work how users expect * native widgets work well with accessibility tools and assistive software * simple licence that's compatible with free and proprietary software * mature foundation: wxWidgets has been around for over 10 years, and is actively developed * binaries are easy to bundle and redistribute in end-user apps, no external dependencies = TODO = This version still has some memory management problems, which can cause crashes - but we're ironing these out! Before we move to beta, we want to support all the GUI classes that were available in the last (0.6.0) release of the old series of wxruby. And there are improvements to be made to the Ruby documentation. wxRuby is a big project, and volunteers are very welcome. There's opportunities to use all sorts of skills, from Ruby and C++ hacking to documentation and publicity. = CREDITS = wxRuby is a genuine team effort. Kevin Smith, Roy Sutton, Sean Long, Nick and Alex Fenton are major contributors to getting wxRuby2 this far. Thanks also to many others who submitted patches, bug reports and sample code. A special thanks to Rubyforge for providing unfailingly helpful hosting for the project. = FURTHER INFORMATION = * Project wiki: http://wxruby.org/ * Rubyforge homepage: http://rubyforge.org/projects/wxruby * Ruby documentation http://wxruby.rubyforge.org/doc/ * Friendly general mailing list: http://rubyforge.org/mailman/listinfo/wxruby-users * Development mailing list, svn commits: http://rubyforge.org/mailman/listinfo/wxruby-development * Subversion repository browsing: http://rubyforge.org/cgi-bin/viewvc.cgi/trunk/wxruby2/?root=wxruby From alex at pressure.to Sat Oct 14 12:34:51 2006 From: alex at pressure.to (Alex Fenton) Date: Sat, 14 Oct 2006 17:34:51 +0100 Subject: [Wxruby-development] Samples In-Reply-To: <4530929C.80403@mindspring.com> References: <4530929C.80403@mindspring.com> Message-ID: <453111AB.6060302@pressure.to> Roy Sutton wrote: > Updated all the sample files to add the shebang line and the require > code we discussed. > Cool, thank you. Just got these via SVN update. > Next, how about we rename all the .rbw files to .rb and update bigdemo? > What would be the rationale for doing this? I'm not against this, just curious. If we do go ahead, we should use 'svn move' on URLs rather than deleting and adding the files - this will preserve the revision history. alex From alex at pressure.to Sat Oct 14 12:35:56 2006 From: alex at pressure.to (Alex Fenton) Date: Sat, 14 Oct 2006 17:35:56 +0100 Subject: [Wxruby-development] test.rb In-Reply-To: <453091B9.1080705@mindspring.com> References: <453091B9.1080705@mindspring.com> Message-ID: <453111EC.5070806@pressure.to> Roy Sutton wrote: > Should the test.rb file in samples/ exist or was it added accidentally > at some point? > Dunno - looks like Kevin's code? Maybe something useful in there that could go in test/ alex From roys at mindspring.com Sat Oct 14 12:40:10 2006 From: roys at mindspring.com (Roy Sutton) Date: Sat, 14 Oct 2006 12:40:10 -0400 Subject: [Wxruby-development] Announcement Message-ID: <453112EA.7030902@mindspring.com> Alex, did you get a chance to do the announcement yet? Roy From roys at mindspring.com Sat Oct 14 12:51:19 2006 From: roys at mindspring.com (Roy Sutton) Date: Sat, 14 Oct 2006 12:51:19 -0400 Subject: [Wxruby-development] announcement In-Reply-To: <45310FD4.8020509@pressure.to> References: <452E0378.8090709@pressure.to> <452EFB25.3000508@qualitycode.com> <45310FD4.8020509@pressure.to> Message-ID: <45311587.3030506@mindspring.com> Alex Fenton wrote: > Happy to post a rubyforge announce, but I don't currently have > permissions to do that. > Well, that short-cuts what I had just sent. I like it! > Will follow it up with a wxSugar announce - I plan to tag and release a > new version with some minor updates. > > Good deal. I wish I had time to play with wxSugar. I have never used it yet. From alex at pressure.to Sat Oct 14 12:58:46 2006 From: alex at pressure.to (Alex Fenton) Date: Sat, 14 Oct 2006 17:58:46 +0100 Subject: [Wxruby-development] Announcement In-Reply-To: <453112EA.7030902@mindspring.com> References: <453112EA.7030902@mindspring.com> Message-ID: <45311746.3040705@pressure.to> Roy Sutton wrote: > Alex, did you get a chance to do the announcement yet? > Looks like our messages crossed - see the draft in my other email. alex From alex at pressure.to Sat Oct 14 13:11:21 2006 From: alex at pressure.to (Alex Fenton) Date: Sat, 14 Oct 2006 18:11:21 +0100 Subject: [Wxruby-development] SVN commit notification Message-ID: <45311A39.5090903@pressure.to> Tom has kindly set up the subversion hook to send commit notifications to this list. So no need I think now to manually write an email for small changes. alex From wxruby at qualitycode.com Sat Oct 14 13:46:40 2006 From: wxruby at qualitycode.com (Kevin Smith) Date: Sat, 14 Oct 2006 13:46:40 -0400 Subject: [Wxruby-development] announcement In-Reply-To: <45310FD4.8020509@pressure.to> References: <452E0378.8090709@pressure.to> <452EFB25.3000508@qualitycode.com> <45310FD4.8020509@pressure.to> Message-ID: <45312280.90804@qualitycode.com> Hey Alex, Looks awesome! The notes below include a couple things I feel strongly about, and a few "would be nice" tweaks. Feel free to make the changes, and post it whenever you are ready. I will copy the FAQ out of the 0.0.36 readme into the FAQ page of the wiki. Thanks again for all your wxruby work! Kevin Alex Fenton wrote: > --- > wxRuby2 preview 0.0.36 has been released! > > wxRuby brings wxWidgets, a mature cross-platform GUI toolkit to Ruby. It > uses native widgets on Windows, OS X and Linux/GTK; you can write GUI > code once and still give users the look, feel and behaviour they expect > from applications. Just this once, I think at this point we need to say something like: This is the first alpha/preview release of wxRuby2, a complete rewrite of wxRuby. > > = INSTALLING WXRUBY = > > Binary gems for major platforms and a source tarball are available at: > http://rubyforge.org/frs/?group_id=35&release_id=7185 > > or via gems: > gem install wxruby2-preview > > NB: this is an alpha-quality release, and is probably not yet stable > enough for production use - but it's evolving quickly! Feedback, > feature requests and bug reports are very welcome. Would slightly prefer "NOTE:" over "NB:", but no biggie. > > All the packages come with a wide array of sample code to demonstrate > how to use the library. Documentation is available online and can be > downloaded for off-line reference. > > = WHAT'S NEW? = > > wxRuby2 is the result of a complete - and lengthy - re-engineering of an > original port. Here's a few reasons why the wait's been worth it: > > * based on wxWidgets 2.6, giving vastly improved appearance on OS X and > Linux > * support for many new windows, controls and widgets > * more complete API coverage within classes > * unicode (UTF-8) support for creating multilingual apps > * uses exceptions rather than segfaults to warn you about incorrect > usage ;) > * downloadable Ruby documentation Ruby-specific > * easier to extend and add C++ classes, by using SWIG and add support for more wx classes, by > * simpler and more permissive licence > * binary gems for all major platforms > > = WHY WXRUBY? = > > There are several great GUI toolkits available for Ruby - but no other > has all the features we like about wxRuby2: > > * cross-platform, with a wide selection of widgets > * native widgets mean that applications look and work how users expect > * native widgets work well with accessibility tools and assistive software > * simple licence that's compatible with free and proprietary software > * mature foundation: wxWidgets has been around for over 10 years, and is > actively developed > * binaries are easy to bundle and redistribute in end-user apps, no > external dependencies > > = TODO = > > This version still has some memory management problems, which can cause > crashes - but we're ironing these out! Before we move to beta, we want > to support all the GUI classes that were available in the last (0.6.0) > release of the old series of wxruby. And there are improvements to be > made to the Ruby documentation. > > wxRuby is a big project, and volunteers are very welcome. There's Should be "There are" instead of "There's" > opportunities to use all sorts of skills, from Ruby and C++ hacking to > documentation and publicity. > > = CREDITS = > > wxRuby is a genuine team effort. Kevin Smith, Roy Sutton, Sean Long, > Nick and Alex Fenton are major contributors to getting wxRuby2 this far. I would move Nick to the end of the list so it's clear his last name isn't also Fenton :-) Eventually I would love to assemble a full list of contributors back to day one, but this looks fine for now. > Thanks also to many others who submitted patches, bug reports and sample > code. A special thanks to Rubyforge for providing unfailingly helpful > hosting for the project. Maybe we could say "and sample code, and to those who contributed to the original wxruby codebase." > > = FURTHER INFORMATION = > > * Project wiki: > http://wxruby.org/ > * Rubyforge homepage: > http://rubyforge.org/projects/wxruby > * Ruby documentation > http://wxruby.rubyforge.org/doc/ > * Friendly general mailing list: > http://rubyforge.org/mailman/listinfo/wxruby-users > * Development mailing list, svn commits: > http://rubyforge.org/mailman/listinfo/wxruby-development > * Subversion repository browsing: > http://rubyforge.org/cgi-bin/viewvc.cgi/trunk/wxruby2/?root=wxruby > > Not sure we need all these links. Probably the first 3 are enough, since they have links to the rest. Might want to add a link directly to the FAQ page of the wiki, though. From alex at pressure.to Sat Oct 14 14:17:24 2006 From: alex at pressure.to (Alex Fenton) Date: Sat, 14 Oct 2006 19:17:24 +0100 Subject: [Wxruby-development] announcement In-Reply-To: <45312280.90804@qualitycode.com> References: <452E0378.8090709@pressure.to> <452EFB25.3000508@qualitycode.com> <45310FD4.8020509@pressure.to> <45312280.90804@qualitycode.com> Message-ID: <453129B4.6060001@pressure.to> Kevin Smith wrote: > The notes below include a couple things I feel strongly > about, and a few "would be nice" tweaks. Thanks - those all looked good so I added them and just posted it to c.l.r. The windows binary gem especially has been going like hot cakes already so I expect we will see even more interest now. Just on my way out now, but plan to post a short announce to the wxwindows newsgroup too later - with the rapidly rising profile of Ruby there may well be some seasoned C++ programmers there with an interest in this port. I see 2.7.1 has just been released and 2.8.0 is expected in a few weeks. cheers alex From wxruby at qualitycode.com Sat Oct 14 14:17:27 2006 From: wxruby at qualitycode.com (Kevin Smith) Date: Sat, 14 Oct 2006 14:17:27 -0400 Subject: [Wxruby-development] test.rb In-Reply-To: <453111EC.5070806@pressure.to> References: <453091B9.1080705@mindspring.com> <453111EC.5070806@pressure.to> Message-ID: <453129B7.7080300@qualitycode.com> Alex Fenton wrote: > Roy Sutton wrote: >> Should the test.rb file in samples/ exist or was it added accidentally >> at some point? >> > Dunno - looks like Kevin's code? Maybe something useful in there that > could go in test/ My error. Not sure how that got committed. I used it to test the internals of App#main_loop etc. We should probably just delete it. Kevin From roys at mindspring.com Sat Oct 14 15:40:24 2006 From: roys at mindspring.com (Roy Sutton) Date: Sat, 14 Oct 2006 15:40:24 -0400 Subject: [Wxruby-development] Activity Message-ID: <45313D28.9010004@mindspring.com> How is it our activity level on RubyForge continues to fall? What exactly makes up 'activity'? Does anyone know? I would have thought with all the commits and the release that our activity figures would be way up there. Roy From roys at mindspring.com Sat Oct 14 15:42:07 2006 From: roys at mindspring.com (Roy Sutton) Date: Sat, 14 Oct 2006 15:42:07 -0400 Subject: [Wxruby-development] Samples In-Reply-To: <453111AB.6060302@pressure.to> References: <4530929C.80403@mindspring.com> <453111AB.6060302@pressure.to> Message-ID: <45313D8F.9090502@mindspring.com> Alex Fenton wrote: > Roy Sutton wrote: > >> Next, how about we rename all the .rbw files to .rb and update bigdemo? >> >> > What would be the rationale for doing this? I'm not against this, just > curious. > Well, .rbw detaches from the console on Windows, which can make debugging difficult, for one thing. For another, .rbw seems to be a Windows-specific extension. > If we do go ahead, we should use 'svn move' on URLs rather than deleting > and adding the files - this will preserve the revision history. > Of course, that was my plan. Roy From roys at mindspring.com Sat Oct 14 15:45:35 2006 From: roys at mindspring.com (Roy Sutton) Date: Sat, 14 Oct 2006 15:45:35 -0400 Subject: [Wxruby-development] test.rb In-Reply-To: <453129B7.7080300@qualitycode.com> References: <453091B9.1080705@mindspring.com> <453111EC.5070806@pressure.to> <453129B7.7080300@qualitycode.com> Message-ID: <45313E5F.1010104@mindspring.com> Kevin Smith wrote: > My error. Not sure how that got committed. I used it to test the > internals of App#main_loop etc. We should probably just delete it. > > In the immortal words of Strong Bad: DELETED! Roy From wxruby at qualitycode.com Sat Oct 14 17:58:34 2006 From: wxruby at qualitycode.com (Kevin Smith) Date: Sat, 14 Oct 2006 17:58:34 -0400 Subject: [Wxruby-development] Activity In-Reply-To: <45313D28.9010004@mindspring.com> References: <45313D28.9010004@mindspring.com> Message-ID: <45315D8A.6040503@qualitycode.com> Roy Sutton wrote: > How is it our activity level on RubyForge continues to fall? What > exactly makes up 'activity'? Does anyone know? I would have thought > with all the commits and the release that our activity figures would be > way up there. If you're talking about the "91.75%" or whatever it is, according to Tom Copeland: --- Well, the stats are somewhat understood - they're based on totting up all the bugs/downloads/pageviews/CVS checkins/forum posts for a project and then munging them. But if I was pressed to explain exactly why a project had a 0% activity percentile on a particular day, I would wander off for a cup of coffee. --- We had a couple really busy weeks, which pushed our numbers up. Our "moderate" activity recently has been less impressive. But the other thing is that it's on a curve. So no matter how active we are, other projects might be even more active, pushing our percentage down. I'm more frustrated that it is impossible (?) to find out how many people downloaded wxruby2 last week, whether from the Files section or via gem. The "all time" number is available, but not week-by-week. Kevin From wxruby at qualitycode.com Sat Oct 14 17:59:54 2006 From: wxruby at qualitycode.com (Kevin Smith) Date: Sat, 14 Oct 2006 17:59:54 -0400 Subject: [Wxruby-development] Updating RAA Message-ID: <45315DDA.80508@qualitycode.com> I realized we might want to update RAA to mention wxruby2. But should it be a new "wxruby2" entry, or should we add mentions of wxruby2 in the existing entry, or should we switch the entry to only talk about wxruby2? Kevin From roys at mindspring.com Sun Oct 15 02:20:57 2006 From: roys at mindspring.com (Roy Sutton) Date: Sun, 15 Oct 2006 02:20:57 -0400 Subject: [Wxruby-development] bug reports Message-ID: <4531D349.2090000@mindspring.com> I switched bug reports and support request issues to go to this list instead of to Kevin directly. I wasn't sure I could add an additional e-mail to the destination. Anyone have a problem with that? Roy From roys at mindspring.com Sun Oct 15 02:59:26 2006 From: roys at mindspring.com (Roy Sutton) Date: Sun, 15 Oct 2006 02:59:26 -0400 Subject: [Wxruby-development] Activity In-Reply-To: <45315D8A.6040503@qualitycode.com> References: <45313D28.9010004@mindspring.com> <45315D8A.6040503@qualitycode.com> Message-ID: <4531DC4E.8010605@mindspring.com> Kevin Smith wrote: > I'm more frustrated that it is impossible (?) to find out how many > people downloaded wxruby2 last week, whether from the Files section or > via gem. The "all time" number is available, but not week-by-week. > > http://rubyforge.org/project/stats/index.php?group_id=35&area=downloads&SPAN=1&start=1159660800&end=1162339200&submit=Refresh That's Daily. Change the date ranges and period to Weekly if you want that. Not enough weeks in October to really help that. Roy From roys at mindspring.com Sun Oct 15 03:03:04 2006 From: roys at mindspring.com (Roy Sutton) Date: Sun, 15 Oct 2006 03:03:04 -0400 Subject: [Wxruby-development] Activity In-Reply-To: <45315D8A.6040503@qualitycode.com> References: <45313D28.9010004@mindspring.com> <45315D8A.6040503@qualitycode.com> Message-ID: <4531DD28.7@mindspring.com> Kevin Smith wrote: > --- > Well, the stats are somewhat understood - they're based on totting up > all the bugs/downloads/pageviews/CVS checkins/forum posts for a project > and then munging them. But if I was pressed to explain exactly why a > project had a 0% activity percentile on a particular day, I would wander > off for a cup of coffee. > --- > > Also note we don't have a forum. Discussion lists don't count so my guess is that some projects get a boost by having a forum. Roy From roys at mindspring.com Sun Oct 15 04:50:12 2006 From: roys at mindspring.com (Roy Sutton) Date: Sun, 15 Oct 2006 04:50:12 -0400 Subject: [Wxruby-development] TaskBarIcon Message-ID: <4531F644.4040609@mindspring.com> Attached are some patches to implement the TaskBarIcon. Let me know how this works on Linux and OS X. You may want to 'svn update' first and get the new version of ruby.png since I fixed the transparent background. Roy -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: bigdemo.rb.patch Url: http://rubyforge.org/pipermail/wxruby-development/attachments/20061015/a0ece935/attachment.ksh -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: wxTaskBarIcon.h.patch Url: http://rubyforge.org/pipermail/wxruby-development/attachments/20061015/a0ece935/attachment-0001.ksh -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: TaskBarIcon.i Url: http://rubyforge.org/pipermail/wxruby-development/attachments/20061015/a0ece935/attachment.pl From wxruby at qualitycode.com Sun Oct 15 08:43:44 2006 From: wxruby at qualitycode.com (Kevin Smith) Date: Sun, 15 Oct 2006 08:43:44 -0400 Subject: [Wxruby-development] bug reports In-Reply-To: <4531D349.2090000@mindspring.com> References: <4531D349.2090000@mindspring.com> Message-ID: <45322D00.3030502@qualitycode.com> Roy Sutton wrote: > I switched bug reports and support request issues to go to this list > instead of to Kevin directly. I wasn't sure I could add an additional > e-mail to the destination. Anyone have a problem with that? Great idea! Kevin From roys at mindspring.com Sun Oct 15 09:53:13 2006 From: roys at mindspring.com (Roy Sutton) Date: Sun, 15 Oct 2006 09:53:13 -0400 Subject: [Wxruby-development] =?utf-8?q?=5BFwd=3A_=5B_wxruby-Bugs-6144_=5D?= =?utf-8?b?IGVycm9yOiBjYXN0IGZyb20g4oCYdm9pZCrigJkgdG8g4oCYaW504oCZIGxv?= =?utf-8?q?ses_precision=5D?= Message-ID: <45323D49.8050105@mindspring.com> I think we can mark this bug closed and check in the patch. Anyone have any concerns/questions before I do? Roy -------- Original Message -------- Subject: [ wxruby-Bugs-6144 ] error: cast from ?void*? to ?int? loses precision Date: Sun, 15 Oct 2006 08:37:31 -0400 (EDT) From: To: noreply at rubyforge.org Bugs item #6144, was opened at 2006-10-15 00:04 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=218&aid=6144&group_id=35 Category: None Group: None Status: Open Resolution: None Priority: 3 Submitted By: Nobody (None) Assigned to: Nobody (None) Summary: error: cast from ?void*? to ?int? loses precision Initial Comment: When compiling on an AMD Athlon64, I get the following error: g++ -c -I/usr/lib/wx/include/gtk2-unicode-release-2.6 -I/usr/include/wx-2.6 -DGTK_NO_CHECK_CASTS -D__WXGTK__ -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -D_LARGEFILE_SOURCE=1 -DNO_GCC_PRAGMA -Wall -g -fno-strict-aliasing -O2 -fPIC -Wno-unused-function -I /usr/local/lib/site_ruby/1.8 -I /usr/local/lib/site_ruby/1.8/x86_64-linux -I /usr/local/lib/site_ruby -I /usr/lib/ruby/1.8 -I /usr/lib/ruby/1.8/x86_64-linux -I . -I /home/bma/wxruby2-preview-0.0.36/doc/lib -o obj/wx.o src/wx.cpp src/wx.cpp: In function ?void GcMapPtrToValue(void*, VALUE)?: src/wx.cpp:1636: error: cast from ?void*? to ?int? loses precision src/wx.cpp: In function ?VALUE GcGetValueFromPtr(void*)?: src/wx.cpp:1646: error: cast from ?void*? to ?int? loses precision rake aborted! Command failed with status (1): [g++ -c -I/usr/lib/wx/include/gtk2-unicod...] After googling, it seems that this is a common error when porting from 32-bit to 64-bit platforms. ---------------------------------------------------------------------- Comment By: Benjamin A'Lee (bma) Date: 2006-10-15 12:37 Message: Yes, that works. ---------------------------------------------------------------------- Comment By: Roy Sutton (roys) Date: 2006-10-15 05:41 Message: Unfortunately I can't test this myself but can you try applying the attached patch to swig/wx.i. Basically change the (int) to (long) in both functions. According to my reading longs should be 64 bits for you. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=218&aid=6144&group_id=35 From wxruby at qualitycode.com Sun Oct 15 22:34:35 2006 From: wxruby at qualitycode.com (Kevin Smith) Date: Sun, 15 Oct 2006 22:34:35 -0400 Subject: [Wxruby-development] =?utf-8?q?=5BFwd=3A_=5B_wxruby-Bugs-6144_=5D?= =?utf-8?b?IGVycm9yOiBjYXN0IGZyb20g4oCYdm9pZCrigJkgdG8g4oCYaW504oCZIGxv?= =?utf-8?q?ses_precision=5D?= In-Reply-To: <45323D49.8050105@mindspring.com> References: <45323D49.8050105@mindspring.com> Message-ID: <4532EFBB.5090104@qualitycode.com> Well, we would check in the patch first, then close the bug. The way you wrote it sounds like the reverse. But I agree that the fix should work. If not, it can be re-opened. Kevin Roy Sutton wrote: > I think we can mark this bug closed and check in the patch. Anyone have > any concerns/questions before I do? > > Roy > > -------- Original Message -------- > Subject: [ wxruby-Bugs-6144 ] error: cast from ?void*? to ?int? loses > precision > Date: Sun, 15 Oct 2006 08:37:31 -0400 (EDT) > From: > To: noreply at rubyforge.org > > > > Bugs item #6144, was opened at 2006-10-15 00:04 > You can respond by visiting: > http://rubyforge.org/tracker/?func=detail&atid=218&aid=6144&group_id=35 > > Category: None > Group: None > Status: Open > Resolution: None > Priority: 3 > Submitted By: Nobody (None) > Assigned to: Nobody (None) > Summary: error: cast from ?void*? to ?int? loses precision > > Initial Comment: > When compiling on an AMD Athlon64, I get the following error: > > g++ -c -I/usr/lib/wx/include/gtk2-unicode-release-2.6 -I/usr/include/wx-2.6 -DGTK_NO_CHECK_CASTS -D__WXGTK__ -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -D_LARGEFILE_SOURCE=1 -DNO_GCC_PRAGMA -Wall -g -fno-strict-aliasing -O2 -fPIC -Wno-unused-function -I /usr/local/lib/site_ruby/1.8 -I /usr/local/lib/site_ruby/1.8/x86_64-linux -I /usr/local/lib/site_ruby -I /usr/lib/ruby/1.8 -I /usr/lib/ruby/1.8/x86_64-linux -I . -I /home/bma/wxruby2-preview-0.0.36/doc/lib -o obj/wx.o src/wx.cpp > src/wx.cpp: In function ?void GcMapPtrToValue(void*, VALUE)?: > src/wx.cpp:1636: error: cast from ?void*? to ?int? loses precision > src/wx.cpp: In function ?VALUE GcGetValueFromPtr(void*)?: > src/wx.cpp:1646: error: cast from ?void*? to ?int? loses precision > rake aborted! > Command failed with status (1): [g++ -c -I/usr/lib/wx/include/gtk2-unicod...] > > After googling, it seems that this is a common error when porting from 32-bit to 64-bit platforms. > > ---------------------------------------------------------------------- > > Comment By: Benjamin A'Lee (bma) > Date: 2006-10-15 12:37 > > Message: > Yes, that works. > > ---------------------------------------------------------------------- > > Comment By: Roy Sutton (roys) > Date: 2006-10-15 05:41 > > Message: > Unfortunately I can't test this myself but can you try applying the attached patch to swig/wx.i. Basically change the (int) to (long) in both functions. According to my reading longs should be 64 bits for you. > > ---------------------------------------------------------------------- > > You can respond by visiting: > http://rubyforge.org/tracker/?func=detail&atid=218&aid=6144&group_id=35 > > > > > _______________________________________________ > Wxruby-development mailing list > Wxruby-development at rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-development From roys at mindspring.com Sun Oct 15 23:29:28 2006 From: roys at mindspring.com (Roy Sutton) Date: Sun, 15 Oct 2006 23:29:28 -0400 Subject: [Wxruby-development] =?utf-8?q?=5BFwd=3A_=5B_wxruby-Bugs-6144_=5D?= =?utf-8?b?IGVycm9yOiBjYXN0IGZyb20g4oCYdm9pZCrigJkgdG8g4oCYaW504oCZIGxv?= =?utf-8?q?ses_precision=5D?= In-Reply-To: <4532EFBB.5090104@qualitycode.com> References: <45323D49.8050105@mindspring.com> <4532EFBB.5090104@qualitycode.com> Message-ID: <4532FC98.8030803@mindspring.com> Kevin Smith wrote: > Well, we would check in the patch first, then close the bug. The way you > wrote it sounds like the reverse. But I agree that the fix should work. > If not, it can be re-opened. > > I didn't mean for 'and' to imply any time relation between the two items, merely that they both were going to happen. Bug closed. Roy From alex at pressure.to Mon Oct 16 03:17:16 2006 From: alex at pressure.to (Alex Fenton) Date: Mon, 16 Oct 2006 08:17:16 +0100 Subject: [Wxruby-development] TaskBarIcon In-Reply-To: <4531F644.4040609@mindspring.com> References: <4531F644.4040609@mindspring.com> Message-ID: <453331FC.2090200@pressure.to> Roy Sutton wrote: > Attached are some patches to implement the TaskBarIcon. Let me know > how this works on Linux and OS X. Nice. Applied, thanks. I really like that we are adding these smaller classes that will give wxRuby applications polish. I initially got an error running bigdemo, samples/bigdemo/bigdemo.rb:754:in `initialize': undefined method `evt_taskbar_left_dclick' for # (NoMethodError) from samples/bigdemo/bigdemo.rb:238:in `new' from samples/bigdemo/bigdemo.rb:238:in `initialize' from samples/bigdemo/bigdemo.rb:816:in `new' from samples/bigdemo/bigdemo.rb:816:in `on_init' from samples/bigdemo/bigdemo.rb:825:in `main_loop' from samples/bigdemo/bigdemo.rb:825 Not sure if you made some changes to EvtHandler.i that I haven't got, or if there's some broken cross-platform thing going on here. So I commented out that line and checked in the rest of the bigdemo, which works nicely, thanks. > You may want to 'svn update' first and get the new version of ruby.png > since I fixed the transparent background. I did, and the shaped window sample now comes out a bit messy on OS X. About 10-20px of standard window canvas is appearing right and below the image where it should be completely transparent. Thanks for patches alex From alex at pressure.to Mon Oct 16 03:20:17 2006 From: alex at pressure.to (Alex Fenton) Date: Mon, 16 Oct 2006 08:20:17 +0100 Subject: [Wxruby-development] Samples In-Reply-To: <45313D8F.9090502@mindspring.com> References: <4530929C.80403@mindspring.com> <453111AB.6060302@pressure.to> <45313D8F.9090502@mindspring.com> Message-ID: <453332B1.4010906@pressure.to> Roy Sutton wrote: > Well, .rbw detaches from the console on Windows, which can make > debugging difficult, for one thing. For another, .rbw seems to be a > Windows-specific extension. > Sound like sound reasons to me. +1 >> If we do go ahead, we should use 'svn move' on URLs rather than deleting >> and adding the files - this will preserve the revision history. >> >> > Of course, that was my plan. > Cool, I'm still finding my way around SVN does better than CVS. Never used it before wxruby, but i'm glad we made the switch. a From alex at pressure.to Mon Oct 16 03:21:33 2006 From: alex at pressure.to (Alex Fenton) Date: Mon, 16 Oct 2006 08:21:33 +0100 Subject: [Wxruby-development] bug reports In-Reply-To: <4531D349.2090000@mindspring.com> References: <4531D349.2090000@mindspring.com> Message-ID: <453332FD.2040300@pressure.to> > I switched bug reports and support request issues to go to this list > instead of to Kevin directly. +1 thanks a From alex at pressure.to Mon Oct 16 03:28:30 2006 From: alex at pressure.to (Alex Fenton) Date: Mon, 16 Oct 2006 08:28:30 +0100 Subject: [Wxruby-development] 0.0.37 release goals Message-ID: <4533349E.7020805@pressure.to> Hi Could we set some release goals for 0.0.37? I suggest we release sooner rather than later to put the various little build problems behind us. So my only high-priority item for 0.037 at the moment is to port Scintilla to Linux and OS X. I will gladly accept other feature, bugfix and doc patches. Anything else we'd like to be sure to do? alex From alex at pressure.to Mon Oct 16 03:31:57 2006 From: alex at pressure.to (Alex Fenton) Date: Mon, 16 Oct 2006 08:31:57 +0100 Subject: [Wxruby-development] Updating RAA In-Reply-To: <45315DDA.80508@qualitycode.com> References: <45315DDA.80508@qualitycode.com> Message-ID: <4533356D.1020001@pressure.to> Kevin Smith wrote: > I realized we might want to update RAA to mention wxruby2. But should it > be a new "wxruby2" entry, or should we add mentions of wxruby2 in the > existing entry, or should we switch the entry to only talk about wxruby2? > I would be inclined to switch the entry to mention only wxruby2 releases. alex From sean.m.long at gmail.com Mon Oct 16 05:03:41 2006 From: sean.m.long at gmail.com (Sean Long) Date: Mon, 16 Oct 2006 02:03:41 -0700 Subject: [Wxruby-development] 0.0.37 release goals In-Reply-To: <4533349E.7020805@pressure.to> References: <4533349E.7020805@pressure.to> Message-ID: > Anything else we'd like to be sure to do? I would like to see the printing patch I just sent added in. Sean From sean.m.long at gmail.com Mon Oct 16 05:06:01 2006 From: sean.m.long at gmail.com (Sean Long) Date: Mon, 16 Oct 2006 02:06:01 -0700 Subject: [Wxruby-development] Updating RAA In-Reply-To: <4533356D.1020001@pressure.to> References: <45315DDA.80508@qualitycode.com> <4533356D.1020001@pressure.to> Message-ID: How about creating a new wxRuby2 entry and have the old wxRuby tell users it is no longer supported and supply the link to the wxRuby2 entry? I believe I have seen other projects do that. Sean On 10/16/06, Alex Fenton wrote: > Kevin Smith wrote: > > I realized we might want to update RAA to mention wxruby2. But should it > > be a new "wxruby2" entry, or should we add mentions of wxruby2 in the > > existing entry, or should we switch the entry to only talk about wxruby2? > > > I would be inclined to switch the entry to mention only wxruby2 releases. > > alex > _______________________________________________ > Wxruby-development mailing list > Wxruby-development at rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-development > From cabal at myrealbox.com Mon Oct 16 09:28:42 2006 From: cabal at myrealbox.com (Cabal) Date: Mon, 16 Oct 2006 14:28:42 +0100 Subject: [Wxruby-development] wxRuby-0.6.0, wxRuby2, SWIG and.... Message-ID: <200610161428.42377.cabal@myrealbox.com> Hi, my first post here so a little background first... I started out using wxRuby-0.6.0 about 4 months ago while trying to get a grip on Ruby as a means of writing a little budgetting app I've been meaning to write for a couple of years. As I didn't like the way that the wxruby examples are coded (having to punch the individual C++ api methods that way isn't nice) I started work on some ruby/wxruby integration stuff originally based on the rubygtk library. As I got deeper into this work a few issues came up that required me to look at the wxruby C++ wrapper and to have a cursory look at the progress of wxRuby2. wxRuby2 seems to have a work rate issue (compared to progress on the original) that I wouldn't expect to exist when using something like SWIG - I may be wrong and you think SWIG is the best thing since sliced bread - but glancing (and I do mean glancing - this isn't something I've investigated even cursorily - thats what this email is for) SWIG seems to be a mixed bag of really good and really really bad (impression gained from the doc on how to add a class to wxruby2). So at this point I was wondering whether my time would be better spent waiting for wxRuby2 to progress somewhat and contribute code, fix 0.6.0 or to have a go at something else entirely... which is what I did. Being a C++ programmer by trade I've written a slew of templates to essentially do what SWIG is meant to do without the automated nature of SWIG. As wxRuby is of immediate concern to me I'm using it as a testbed for this C++/Ruby wrapper replacement and I'd like to know if you think there is any future where you might find it more useful than SWIG for what you are trying to do. I'm thinking that my template wrappers will have a more linear application curve (ie not as good as SWIG at its best but nowhere near as bad as SWIG in its worse case scenario). My apologies if I have misread what has been said regarding the ease with which SWIG does its job and if thats so just put me straight right away... I've attached button.cpp and button.h which are my current drop-in replacements for the original wxRuby-0.6.0 files of the same name. I may post the code inline if there is an issue with attachments on this mailing list. I haven't made any effort yet to remove the necessity for the init0 functions. The MapRubyObjectToCppObject is there at the moment for compatibility with the rest of the code base and the init/constructor functions will merge soon. I'm fairly sure I can make the instance method definitions disappear altogether when the wrapper is along the same simplistic lines of these. I'm not going to post the template wrappers anywhere for a few weeks yet - the code will be released as a new project on rubyforge barring any unobvious show stoppers. -------------- next part -------------- A non-text attachment was scrubbed... Name: button.cpp Type: text/x-c++src Size: 3424 bytes Desc: not available Url : http://rubyforge.org/pipermail/wxruby-development/attachments/20061016/76fb988e/attachment.bin -------------- next part -------------- A non-text attachment was scrubbed... Name: button.h Type: text/x-c++hdr Size: 909 bytes Desc: not available Url : http://rubyforge.org/pipermail/wxruby-development/attachments/20061016/76fb988e/attachment-0001.bin From roys at mindspring.com Mon Oct 16 09:44:09 2006 From: roys at mindspring.com (Roy Sutton) Date: Mon, 16 Oct 2006 09:44:09 -0400 Subject: [Wxruby-development] TaskBarIcon In-Reply-To: <453331FC.2090200@pressure.to> References: <4531F644.4040609@mindspring.com> <453331FC.2090200@pressure.to> Message-ID: <45338CA9.4000209@mindspring.com> Alex Fenton wrote: > Nice. Applied, thanks. I really like that we are adding these smaller > classes that will give wxRuby applications polish. > > I initially got an error running bigdemo, > > samples/bigdemo/bigdemo.rb:754:in `initialize': undefined method > `evt_taskbar_left_dclick' for # (NoMethodError) > > Not sure if you made some changes to EvtHandler.i that I haven't got, or > if there's some broken cross-platform thing going on here. So I > commented out that line and checked in the rest of the bigdemo, which > works nicely, thanks. > Oddly, I got this same problem on Linux when I tried it there. I don't know why and hadn't had time to investigate. Given all the problems I had there I didn't want to speculate on the origin. Now I guess I have to look into it more. >> You may want to 'svn update' first and get the new version of ruby.png >> since I fixed the transparent background. >> > I did, and the shaped window sample now comes out a bit messy on OS X. > About 10-20px of standard window canvas is appearing right and below the > image where it should be completely transparent. > Hmm, I'll look into that more. I think I may be calling a function to set the transparent color when there isn't one anymore. From roys at mindspring.com Mon Oct 16 11:20:24 2006 From: roys at mindspring.com (Roy Sutton) Date: Mon, 16 Oct 2006 11:20:24 -0400 Subject: [Wxruby-development] 0.0.37 release goals In-Reply-To: References: <4533349E.7020805@pressure.to> Message-ID: <4533A338.7090207@mindspring.com> Sean Long wrote: >> Anything else we'd like to be sure to do? >> > > I would like to see the printing patch I just sent added in. > > Sean, I haven't seen any printing patches recently. Can you re-send them or did they not go out yet? Roy From roys at mindspring.com Mon Oct 16 11:36:50 2006 From: roys at mindspring.com (Roy Sutton) Date: Mon, 16 Oct 2006 11:36:50 -0400 Subject: [Wxruby-development] wxRuby-0.6.0, wxRuby2, SWIG and.... In-Reply-To: <200610161428.42377.cabal@myrealbox.com> References: <200610161428.42377.cabal@myrealbox.com> Message-ID: <4533A712.5000706@mindspring.com> Cabal wrote: > Hi, my first post here so a little background first... Hello Cabal, Are you saying that the button.cpp and button.h files were generated automatically or that you used some templating mechanism you came up with to create them? SWIG is a mixed bag sometimes. The learning curve to implement a project with the complexity of wxWidgets is non-trivial. However, I do feel that with wxRuby2 we've already gotten over the major hurdles presented. If you look at the recent class additions you'd see that they (almost always) consisted of only a .i (SWIG interface) file of about 10 lines. Each .i file is really just a copy of an existing .i file with the names changed. Having said that, if you have a solution to wrapping libraries that's specific to Ruby and can deal with: - overriding C++ methods from Ruby - pointer arguments that could be input, output or both - complex argument and return types - conversion of arguments from ruby types to C/C++ types - collapsing/expanding of arguments (e.g. ruby array to int n, char ** lines) - memory management Then I'd say you're really on to something. At this point what I think we really need is assistance with wxRuby2. wxRuby 0.6.0 is a dead-end project now. We've officially stopped all support for it and closed all open issues associated with it. Roy From roys at mindspring.com Mon Oct 16 11:56:22 2006 From: roys at mindspring.com (Roy Sutton) Date: Mon, 16 Oct 2006 11:56:22 -0400 Subject: [Wxruby-development] 0.0.37 release goals In-Reply-To: <4533349E.7020805@pressure.to> References: <4533349E.7020805@pressure.to> Message-ID: <4533ABA6.40309@mindspring.com> Alex Fenton wrote: > Could we set some release goals for 0.0.37? I suggest we release sooner > rather than later to put the various little build problems behind us. > > So my only high-priority item for 0.037 at the moment is to port > Scintilla to Linux and OS X. I will gladly accept other feature, bugfix > and doc patches. > > Anything else we'd like to be sure to do? I would like to address the TODO file (even if it's removing obsolete items and re-prioritizing the existing items) Also, I would like to update the wiki and perhaps README (or create a new BUILDING) file to discuss the proper flags and options for each component of the build process on each platform. One of the biggest problems we have is building properly on all platforms. Finally, I think we might want to implement Drag and Drop and Clipboard Roy From roys at mindspring.com Mon Oct 16 13:41:44 2006 From: roys at mindspring.com (Roy Sutton) Date: Mon, 16 Oct 2006 13:41:44 -0400 Subject: [Wxruby-development] Printing Message-ID: <4533C458.60706@mindspring.com> I have applied Sean's patches internally. Only print preview is working. I will try to see why page setup and print aren't working later. Be careful applying those patches as they may remove the TaskBarIcon changes that were checked in recently. (I just edited them out before applying) Roy From cabal at myrealbox.com Mon Oct 16 15:25:47 2006 From: cabal at myrealbox.com (Cabal) Date: Mon, 16 Oct 2006 20:25:47 +0100 Subject: [Wxruby-development] wxRuby-0.6.0, wxRuby2, SWIG and.... In-Reply-To: <4533A712.5000706@mindspring.com> References: <200610161428.42377.cabal@myrealbox.com> <4533A712.5000706@mindspring.com> Message-ID: <200610162025.47133.cabal@myrealbox.com> Hi Roy - I'll try and answer your questions inline... On Monday 16 October 2006 16:36, you wrote: > Cabal wrote: > > Hi, my first post here so a little background first... > Hello Cabal, > > Are you saying that the button.cpp and button.h files were generated > automatically or that you used some templating mechanism you came up > with to create them? The button.* files supplied are hand written - Button was the class I chose to get the wrapper up and going fairly easily. I don't intend attempting to write any auto-generation script at this point, I'm still extending the functionality to cover various use cases as I come across them. At the moment I'm proceeding by hijacking the the 0.6.0 files and replacing the code for each function to make use of the wrappers. > > SWIG is a mixed bag sometimes. The learning curve to implement a > project with the complexity of wxWidgets is non-trivial. However, I do > feel that with wxRuby2 we've already gotten over the major hurdles > presented. If you look at the recent class additions you'd see that > they (almost always) consisted of only a .i (SWIG interface) file of > about 10 lines. Each .i file is really just a copy of an existing .i > file with the names changed. I'm glad to hear you've wrestled SWIG into submission :) > > Having said that, if you have a solution to wrapping libraries that's > specific to Ruby and can deal with: > > - overriding C++ methods from Ruby Not sure I understand this one. Do you mean just being able to call the C++ methods from Ruby? Once ruby knows how to call a method then 'overriding' would be an ability handled by ruby in some derived class... > - pointer arguments that could be input, output or both I don't see any issues with handling pointers (not at this point anyway). I've got a few specialisations on wx pointer types already. > - complex argument and return types I presume you're talking about non-pod datatypes and references and pointers to them. No issues upto now for wx types passed as arguments and return values. > - conversion of arguments from ruby types to C/C++ types One of the easier bits. > - collapsing/expanding of arguments (e.g. ruby array to int n, char ** > lines) At the minute I'm concentrating on passing args using 'int argc, VALUE* argv' method signatures and upto 10 VALUE arguments. From the existing code that I've looked at I haven't seen much cause for expanding and collapsing ruby arrays as a separate operation per se. > - memory management I've specialised the templates for wx objects to link memory management into the wxObjectRefData class. The wrapper will require some sort of help along these lines whichever C++ library it is used for - but I can't see that being any different for any other method of wrapping a library. > > Then I'd say you're really on to something. > > At this point what I think we really need is assistance with wxRuby2. > wxRuby 0.6.0 is a dead-end project now. We've officially stopped all > support for it and closed all open issues associated with it. Yes - I'd got that impression :) Unfortunately wxRuby2 didn't look like it was going to be released in a usable form anytime soon (now rectified, possibly :) ) and now I've got my teeth into this I'm keen to see where it leads. I hope it will prove useful somewhere along the lines to wxRuby2 (as you've kindly provided me with a testbed and copious examples in 0.6.0) but I won't go bugging you about it :) Good luck and happy coding... Cabal From sean.m.long at gmail.com Mon Oct 16 15:30:43 2006 From: sean.m.long at gmail.com (Sean Long) Date: Mon, 16 Oct 2006 12:30:43 -0700 Subject: [Wxruby-development] Printing In-Reply-To: <4533C458.60706@mindspring.com> References: <4533C458.60706@mindspring.com> Message-ID: > Be careful applying those patches as they may remove the TaskBarIcon > changes that were checked in recently. (I just edited them out before > applying) Sorry about that, it was very late and I wanted to get it uploaded while I had some available time. Sean From roys at mindspring.com Mon Oct 16 16:39:40 2006 From: roys at mindspring.com (Roy Sutton) Date: Mon, 16 Oct 2006 16:39:40 -0400 Subject: [Wxruby-development] wxRuby-0.6.0, wxRuby2, SWIG and.... In-Reply-To: <200610162025.47133.cabal@myrealbox.com> References: <200610161428.42377.cabal@myrealbox.com> <4533A712.5000706@mindspring.com> <200610162025.47133.cabal@myrealbox.com> Message-ID: <4533EE0C.1050908@mindspring.com> Cabal wrote: > Hi Roy - I'll try and answer your questions inline... > Thanks for the response. >> - overriding C++ methods from Ruby >> > Not sure I understand this one. Do you mean just being able to call the C++ > methods from Ruby? Once ruby knows how to call a method then 'overriding' > would be an ability handled by ruby in some derived class... > I meant does your wrapper handle overriding virtual C++ functions with Ruby functions. As in, can I replace the default C++ behavior with Ruby and call the parent with super(). I also forgot to ask if your method maintains the object heirarchy. Roy From roys at mindspring.com Mon Oct 16 17:50:48 2006 From: roys at mindspring.com (Roy Sutton) Date: Mon, 16 Oct 2006 17:50:48 -0400 Subject: [Wxruby-development] TaskBarIcon In-Reply-To: <453331FC.2090200@pressure.to> References: <4531F644.4040609@mindspring.com> <453331FC.2090200@pressure.to> Message-ID: <4533FEB8.3080201@mindspring.com> Alex Fenton wrote: > Roy Sutton wrote: > >> Attached are some patches to implement the TaskBarIcon. Let me know >> how this works on Linux and OS X. >> > samples/bigdemo/bigdemo.rb:754:in `initialize': undefined method > `evt_taskbar_left_dclick' for # (NoMethodError) > The problem was fixevents.rb. I will soon check in a patch to fixevents.rb as well as check in a change to rakewx.rb (to make events.cpp dependant upon fixevents.rb). Roy From sean.m.long at gmail.com Mon Oct 16 22:56:57 2006 From: sean.m.long at gmail.com (Sean Long) Date: Mon, 16 Oct 2006 19:56:57 -0700 Subject: [Wxruby-development] Printing fix In-Reply-To: <45342896.20005@mindspring.com> References: <45342896.20005@mindspring.com> Message-ID: > The sample doesn't work on Windows as it is now. RUBY_PLATFORM is never > equal to WXMSW. I need to fix all our samples that have something > similar. Oddly, many samples work fine on Windows with icons that are > xpm (since obviously the test always fails). This example does not. The sample runs the same on Windows for me as it does on OS X. > Print does bring up the print dialog but nothing is ever printed for > me. I'll try with another printer later. I tried with a HP laser and it did not work but then when I tried with an HP inkjet it worked. I may have changed from print all to print 1 or 1 on the inkjet printer. > I don't think we should check in anything until we get page setup working. It may only be a problem with the sample code not the API. > (Why aren't we using the list?) I wasn't using the list because the patches did not go to the list yet, or have they now. Sean > Roy > > Sean Long wrote: > > I figured out why the print menu wast not working, a left over & from > > the conversion from C++. The Page Setup is not working for me but > > Print and Print Preview are. > > > > This version of the sample overrides the one I sent earlier. > > > > I just need to get commit access and I could fix all this myself. > > > > > > Sean > From roys at mindspring.com Mon Oct 16 23:21:32 2006 From: roys at mindspring.com (Roy Sutton) Date: Mon, 16 Oct 2006 23:21:32 -0400 Subject: [Wxruby-development] Printing Support Message-ID: <45344C3C.1000401@mindspring.com> Printing support is added to the repository (as you have seen / will see). Kudos to Sean for tackling such a big bear. I'll work on adding the two dialogs to bigdemo later unless Sean tackles it first. Roy From roys at mindspring.com Tue Oct 17 01:33:13 2006 From: roys at mindspring.com (Roy Sutton) Date: Tue, 17 Oct 2006 01:33:13 -0400 Subject: [Wxruby-development] Typemap.i checked in and attached RadioBox.i.patch Message-ID: <45346B19.10906@mindspring.com> I checked in a small change to typemaps.i that adds an enum that was missing Attached is a slightly larger patch. I felt pretty confident checking this in but I'll send it out so others can check it out. This should make the radiobox tab in controls.rb work. Roy -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: RadioBox.i.patch Url: http://rubyforge.org/pipermail/wxruby-development/attachments/20061017/01b371a8/attachment.ksh From roys at mindspring.com Tue Oct 17 01:40:51 2006 From: roys at mindspring.com (Roy Sutton) Date: Tue, 17 Oct 2006 01:40:51 -0400 Subject: [Wxruby-development] Updated samples Message-ID: <45346CE3.10000@mindspring.com> I fixed up a couple crashers in bigdemo.rb and wxTreeCtrl.rb and enabled the images in the TreeCtrl sample. Do an svn update, build and check 'em out. Roy From alex at pressure.to Tue Oct 17 07:22:53 2006 From: alex at pressure.to (Alex Fenton) Date: Tue, 17 Oct 2006 12:22:53 +0100 Subject: [Wxruby-development] 0.0.37 release goals In-Reply-To: <4533ABA6.40309@mindspring.com> References: <4533349E.7020805@pressure.to> <4533ABA6.40309@mindspring.com> Message-ID: <4534BD0D.6060706@pressure.to> Roy Sutton wrote: >> Anything else we'd like to be sure to do? >> > I would like to address the TODO file (even if it's removing obsolete > items and re-prioritizing the existing items) > Sounds good. I have been updating it before the last few releases. There is internals stuff in there I do not really understand, but suspect is obsolete. > Also, I would like to update the wiki and perhaps README (or create a > new BUILDING) file to discuss the proper flags and options for each > component of the build process on each platform. > Sounds good. After the thread on c.l.r I asked Tom to resync the mirrors so they definitely have the current Intel OSX gem, which shouldn't require libpng. I started a page on the wiki last week on this http://wxruby.rubyforge.org/wiki/wiki.pl?Release_HowTo > Finally, I think we might want to implement Drag and Drop and Clipboard > It would be nice to have, but I don't think it's indispensable to 0.0.37. Must do for 1.9 though. Dnd/Clipboard is a tough one - the main problem I have run into is that there is an unexposed base class DataObjectBase, and unclear which methods where should be virtual. From reading the header files, I think if someone with l33t skills could fix DataObjectSimple then the others should fall into place reasonably easily. alex From alex at pressure.to Tue Oct 17 07:38:09 2006 From: alex at pressure.to (Alex Fenton) Date: Tue, 17 Oct 2006 12:38:09 +0100 Subject: [Wxruby-development] TaskBarIcon In-Reply-To: <4533FEB8.3080201@mindspring.com> References: <4531F644.4040609@mindspring.com> <453331FC.2090200@pressure.to> <4533FEB8.3080201@mindspring.com> Message-ID: <4534C0A1.8030509@pressure.to> > The problem was fixevents.rb. I will soon check in a patch to > fixevents.rb as well as check in a change to rakewx.rb (to make > events.cpp dependant upon fixevents.rb). > Nice spot. I removed the non-Windows exclusion for EVT_TOGGLEBUTTON from the same place; compiles fine and the ToggleButton sample works. The EVT_DIALUP exclusion is still needed though. Attached is some code I tried out in the process of trying to fix this - exposes the undocumented TaskbarIconEvent class, and does the type-mapping of this event in EvtHandler. May or may not be useful; please commit if yes. As the docs hint, TaskBarIconEvents don't seem to be fired on OS X. I'm currently unable to do commits or get updates from SVN b/c my home internet connection is broken. Able to keep up with emails a bit from work (but gotta be a bit subtle). cheers alex -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: EvtHandler_i.taskbar_patch Url: http://rubyforge.org/pipermail/wxruby-development/attachments/20061017/346b94d9/attachment-0002.ksh -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: TaskBarIconEvent.i Url: http://rubyforge.org/pipermail/wxruby-development/attachments/20061017/346b94d9/attachment-0003.ksh -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: wxTaskBarIconEvent.h Url: http://rubyforge.org/pipermail/wxruby-development/attachments/20061017/346b94d9/attachment-0001.h From alex at pressure.to Tue Oct 17 07:44:10 2006 From: alex at pressure.to (Alex Fenton) Date: Tue, 17 Oct 2006 12:44:10 +0100 Subject: [Wxruby-development] Printing Support In-Reply-To: <45344C3C.1000401@mindspring.com> References: <45344C3C.1000401@mindspring.com> Message-ID: <4534C20A.1040308@pressure.to> Roy Sutton wrote: > Printing support is added to the repository (as you have seen / will > see). Kudos to Sean for tackling such a big bear. > I'll second that. It's a tremendous bit of work. I hadn't hoped that we would tackle this for some time yet. The patches you sent yday compiled cleanly on OS X PPC. I don't have a printer I can test the output with, but save-to-PDF works, and jobs are getting enqueued correctly. There are couple of issues in the sample, but I think you are aware of these already. Just in case: 1) PageSetupDialog allocator undefined (printing.rb line 165) 2) undefined method 'get_last_error' for Wx::Printer:Class (printing.rb 136) 3) the stray ampersand Thanks again Sean Alex From wxruby at qualitycode.com Tue Oct 17 07:57:46 2006 From: wxruby at qualitycode.com (Kevin Smith) Date: Tue, 17 Oct 2006 07:57:46 -0400 Subject: [Wxruby-development] 0.0.37 release goals In-Reply-To: <4534BD0D.6060706@pressure.to> References: <4533349E.7020805@pressure.to> <4533ABA6.40309@mindspring.com> <4534BD0D.6060706@pressure.to> Message-ID: <4534C53A.3060206@qualitycode.com> Alex Fenton wrote: > Roy Sutton wrote: >>> Anything else we'd like to be sure to do? >>> >> I would like to address the TODO file (even if it's removing obsolete >> items and re-prioritizing the existing items) >> > Sounds good. I have been updating it before the last few releases. There > is internals stuff in there I do not really understand, but suspect is > obsolete. I can try to take a look at the TODO in the next couple days, but definitely don't consider it a .37 showstopper. >> Also, I would like to update the wiki and perhaps README (or create a >> new BUILDING) file to discuss the proper flags and options for each >> component of the build process on each platform. >> > Sounds good. After the thread on c.l.r I asked Tom to resync the mirrors > so they definitely have the current Intel OSX gem, which shouldn't > require libpng. This is probably the #1 reason to push a .37 asap. For me, it is probably the only fix that absolutely has to be in .37. I don't think sync'ing mirrors is really enough, because bad copies of .36 are floating around out there. > I started a page on the wiki last week on this > http://wxruby.rubyforge.org/wiki/wiki.pl?Release_HowTo > >> Finally, I think we might want to implement Drag and Drop and Clipboard >> > It would be nice to have, but I don't think it's indispensable to > 0.0.37. Must do for 1.9 though. Agree. > > Dnd/Clipboard is a tough one - the main problem I have run into is that > there is an unexposed base class DataObjectBase, and unclear which > methods where should be virtual. > > From reading the header files, I think if someone with l33t skills > could fix DataObjectSimple then the others should fall into place > reasonably easily. Maybe I'll have time this weekend to take a look, if that's the most important "deep" C++ issue we have. Kevin From wxruby at qualitycode.com Tue Oct 17 08:09:54 2006 From: wxruby at qualitycode.com (Kevin Smith) Date: Tue, 17 Oct 2006 08:09:54 -0400 Subject: [Wxruby-development] svn commits and other administrivia In-Reply-To: <4534634C.3030809@mindspring.com> References: <4534634C.3030809@mindspring.com> Message-ID: <4534C812.1080401@qualitycode.com> Roy Sutton wrote: > I think commit e-mails are getting rejected by mailman. Here are the > instructions from RubyForge's FAQ: I have not received any bounce messages, and I couldn't find any evidence of svn message bounces within the mailman admin pages. But I followed the instructions anyway, so whether svn has been getting bounces, or isn't yet properly generating commit emails, the list should now be ready. By the way, I also bumped the maximum email size from the default up to 40k. That was why Sean's first printing patch didn't get through. It seems like at least one or two of you should also be mailing list admins so I'm not the bottleneck on this kind of stuff. Volunteers? Kevin From alex at pressure.to Tue Oct 17 10:48:52 2006 From: alex at pressure.to (Alex Fenton) Date: Tue, 17 Oct 2006 15:48:52 +0100 Subject: [Wxruby-development] wxRuby-0.6.0, wxRuby2, SWIG and.... In-Reply-To: <200610161428.42377.cabal@myrealbox.com> References: <200610161428.42377.cabal@myrealbox.com> Message-ID: <4534ED54.5040401@pressure.to> Hi Cabal wrote: > Hi, my first post here so a little background first... > Welcome, thanks for your interest in wxRuby. > wxRuby2 seems to have a work rate > issue (compared to progress on the original) that I wouldn't expect to exist > when using something like SWIG You're right that wxRuby2 progress has not been that even. But that's not mainly because of SWIG - it's primarily the simple reason that there has been a shortage of people with time and willingness to work on the project. At the moment we have a core team of four developers, plust about the same number again submitting occasional patches. If you look at the last three to four months on the m.l and commits, we've made sustained and rapid progress: around 40 new classes, squashed some tricky bugs, plus the additional but important work associated with a project, such as documentation and packaging. SWIG plus our Kevin's early work moulding SWIG to our needs has been key to porting a lot of tricky functionality in that time. > - I may be wrong and you think SWIG is the > best thing since sliced bread - Hehe - I doubt any of the wxruby2 developers would think that! SWIG is a very mixed blessing. You aren't the first person to question its use for wxruby. But the consensus probably is that its the the best available tool, under active development and with a future. > but glancing (and I do mean glancing - this > isn't something I've investigated even cursorily - thats what this email is > for) SWIG seems to be a mixed bag of really good and really really bad > True. The way it parses header files to automatically wrap methods is slick. Typemaps are very important for us - but the way they are declared and used is horrible. Directors are also really important - but completely undocumented for Ruby. SWIG-ruby is also pretty immature, and using it on wxWidgets has tested its limits - the size of the library, plus the typical difficulties of GUI programming (highly platform specific; long-running; event-driven in unpredictable ways). > I'd like to know if you think there is any > future where you might find it more useful than SWIG for what you are trying > to do. Thanks for posting the sample code for button.cpp. To be honest, I can't see us switching from SWIG for the upcoming version 2. There would have to be a compelling reason to switch in the future. Roy has given you some specific feedback on C++ constructs that might be challenging. My feedback would be: I don't know C, or C++. Your solution seems geared to people who want to simplify and reduce repetition in writing wrapper code. But it doesn't help those who don't know or want to know C++. It just seems more of the macro/template madness that makes C++, to me, such an unappealing language to learn (SWIG is like this too). Anyway, overall, I think there is definitely still space out there for a very well-designed, easy to use, library wrapping tool for Ruby. It would be more than just us interested in such a tool. But, to be a compelling alternative, it would have to enable wrapping work to be done *in* Ruby. Kevin's suggested before that a more useful project might be to develop a higher-level Ruby-based abstraction on top of SWIG (or your own work), and I agree. Your potential user base would be much wider: all Ruby programmers, not just the limited set of Ruby programmers who are also keen C++ programmers. If your main goal is to get a pretty complete WxRuby pretty soon, I'd say you're definitely best off contributing to this project. We have roughly 90% of the API ported (not including C++ classes that are redundant in Ruby), and an active team to share the work. We'll be happy to help explain how the SWIGgy mess works. If you have an itch to scratch about C++ wrapping in general, and don't want to build on SWIG, then it's probalby not for you. Either way, thanks again for your interest, keep in touch, and good luck. alex From roys at mindspring.com Tue Oct 17 11:03:59 2006 From: roys at mindspring.com (Roy Sutton) Date: Tue, 17 Oct 2006 11:03:59 -0400 Subject: [Wxruby-development] svn commits and other administrivia In-Reply-To: <4534C812.1080401@qualitycode.com> References: <4534634C.3030809@mindspring.com> <4534C812.1080401@qualitycode.com> Message-ID: <4534F0DF.4050801@mindspring.com> Kevin Smith wrote: > It seems like at least one or two of you should also be mailing list > admins so I'm not the bottleneck on this kind of stuff. Volunteers? Not that volunteering is at the top of my list but I'll do it. :) Roy From alex at pressure.to Tue Oct 17 11:22:18 2006 From: alex at pressure.to (Alex Fenton) Date: Tue, 17 Oct 2006 16:22:18 +0100 Subject: [Wxruby-development] svn commits and other administrivia In-Reply-To: <4534F0DF.4050801@mindspring.com> References: <4534634C.3030809@mindspring.com> <4534C812.1080401@qualitycode.com> <4534F0DF.4050801@mindspring.com> Message-ID: <4534F52A.8050605@pressure.to> Roy Sutton wrote: > Kevin Smith wrote: > >> It seems like at least one or two of you should also be mailing list >> admins so I'm not the bottleneck on this kind of stuff. Volunteers? >> > Not that volunteering is at the top of my list but I'll do it. :) > Thanks - I'm also happy to do it. Also happy to take a lead on it if it would help Roy focus on all the other stuff he is better qualified than me to tackle. alex From nobody at rubyforge.org Tue Oct 17 12:49:33 2006 From: nobody at rubyforge.org (nobody at rubyforge.org) Date: Tue, 17 Oct 2006 12:49:33 -0400 (EDT) Subject: [Wxruby-development] [677] trunk/wxruby2/doc/textile/index.txtl: Removed line from printing framework section stating that printing is not in wxRuby. Message-ID: <20061017164933.6A3EE52413BA@rubyforge.org> An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wxruby-development/attachments/20061017/e915f52e/attachment.html From nobody at rubyforge.org Tue Oct 17 13:00:00 2006 From: nobody at rubyforge.org (nobody at rubyforge.org) Date: Tue, 17 Oct 2006 13:00:00 -0400 (EDT) Subject: [Wxruby-development] [678] trunk/wxruby2/doc/textile/commandevent.txtl: Fixed a few event macros that did not get fixed by the parser. Message-ID: <20061017170000.DBB7DA97002A@rubyforge.org> An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wxruby-development/attachments/20061017/b1f77dee/attachment-0001.html From nobody at rubyforge.org Tue Oct 17 13:15:43 2006 From: nobody at rubyforge.org (nobody at rubyforge.org) Date: Tue, 17 Oct 2006 13:15:43 -0400 (EDT) Subject: [Wxruby-development] [679] trunk/wxruby2/doc/textile/previewframe.txtl: Changed the initialize() method to init() so it matches the API also added a remark alerting the user to this. Message-ID: <20061017171544.B0B015240970@rubyforge.org> An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wxruby-development/attachments/20061017/da069f2d/attachment.html From nobody at rubyforge.org Tue Oct 17 14:03:30 2006 From: nobody at rubyforge.org (nobody at rubyforge.org) Date: Tue, 17 Oct 2006 14:03:30 -0400 (EDT) Subject: [Wxruby-development] [680] trunk/wxruby2/samples/printing/printing.rb: Cleaned up to use the Ruby naming convention, added #! line, now uses Wx default ID's in standard menu items. Message-ID: <20061017180330.BB9F8A970014@rubyforge.org> An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wxruby-development/attachments/20061017/f6687c61/attachment.html From sean.m.long at gmail.com Tue Oct 17 14:11:31 2006 From: sean.m.long at gmail.com (Sean Long) Date: Tue, 17 Oct 2006 11:11:31 -0700 Subject: [Wxruby-development] Patch for Wx::Printer Message-ID: This patch adds the get_abort and get_last_error methods to Wx::Printer and also the error constants to RubyConstants.i. With out these changes the printing sample will crash if you decide to cancel the print dialog. The change worked well for me just would like to make sure it works on 1 other platform before committing. Sean -------------- next part -------------- A non-text attachment was scrubbed... Name: printer.patch Type: application/octet-stream Size: 1387 bytes Desc: not available Url : http://rubyforge.org/pipermail/wxruby-development/attachments/20061017/ef375fbd/attachment-0001.obj From nobody at rubyforge.org Tue Oct 17 14:47:28 2006 From: nobody at rubyforge.org (nobody at rubyforge.org) Date: Tue, 17 Oct 2006 14:47:28 -0400 (EDT) Subject: [Wxruby-development] [681] trunk/wxruby2/samples/treectrl/treectrl.rb: wxMAC does not like menu id's of 0 so I fixed that also made set_item_text_colour Message-ID: <20061017184729.287F15241473@rubyforge.org> An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wxruby-development/attachments/20061017/b7550cc6/attachment.html From roys at mindspring.com Tue Oct 17 15:01:43 2006 From: roys at mindspring.com (Roy Sutton) Date: Tue, 17 Oct 2006 15:01:43 -0400 Subject: [Wxruby-development] Printing Support In-Reply-To: <4534C20A.1040308@pressure.to> References: <45344C3C.1000401@mindspring.com> <4534C20A.1040308@pressure.to> Message-ID: <45352897.6010701@mindspring.com> [Note: I see Sean proposed a patch already similar to what I'm posting here. This one has his changes and some others] Alex Fenton wrote: > There are couple of issues in the sample, but I think you are aware of > these already. Just in case: > > 1) PageSetupDialog allocator undefined (printing.rb line 165) > Hmm, I didn't see this one. How did you get that to happen so I can reproduce it? Or did I fix it in the checked in sample already? > 2) undefined method 'get_last_error' for Wx::Printer:Class (printing.rb 136) > I missed this completely. See attached patches. I also had to apply several enum typemaps to fix problems with wrapping. > 3) the stray ampersand > Already fixed in checked in version > Thanks again Sean > -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: typedefs.i.patch Url: http://rubyforge.org/pipermail/wxruby-development/attachments/20061017/9e75856f/attachment.pl -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: RubyConstants.i.patch Url: http://rubyforge.org/pipermail/wxruby-development/attachments/20061017/9e75856f/attachment-0001.pl -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: wxPrinter.h.patch Url: http://rubyforge.org/pipermail/wxruby-development/attachments/20061017/9e75856f/attachment-0002.pl From nobody at rubyforge.org Tue Oct 17 15:21:04 2006 From: nobody at rubyforge.org (nobody at rubyforge.org) Date: Tue, 17 Oct 2006 15:21:04 -0400 (EDT) Subject: [Wxruby-development] [682] trunk/wxruby2/doc/textile/htmlwindow.txtl: Fix some little formatting errors that were causing the page to be unreadable Message-ID: <20061017192104.AE065A970025@rubyforge.org> An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wxruby-development/attachments/20061017/653c0e0f/attachment.html From nobody at rubyforge.org Tue Oct 17 15:25:03 2006 From: nobody at rubyforge.org (nobody at rubyforge.org) Date: Tue, 17 Oct 2006 15:25:03 -0400 (EDT) Subject: [Wxruby-development] [683] trunk/wxruby2/doc/textile/index.txtl: Fix a table Message-ID: <20061017192505.5707D52415C1@rubyforge.org> An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wxruby-development/attachments/20061017/22d504bc/attachment.html From nobody at rubyforge.org Tue Oct 17 15:29:02 2006 From: nobody at rubyforge.org (nobody at rubyforge.org) Date: Tue, 17 Oct 2006 15:29:02 -0400 (EDT) Subject: [Wxruby-development] [684] trunk/wxruby2/swig/classes/RadioBox.i: Un-ignored some methods that now work fine (Roy Sutton) Message-ID: <20061017192902.A78985241555@rubyforge.org> An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wxruby-development/attachments/20061017/2927daa1/attachment.html From nobody at rubyforge.org Tue Oct 17 17:49:07 2006 From: nobody at rubyforge.org (nobody at rubyforge.org) Date: Tue, 17 Oct 2006 17:49:07 -0400 (EDT) Subject: [Wxruby-development] [685] trunk/wxruby2/swig: Add Printing constants and typedefs, add two missing methods (Roy Message-ID: <20061017214907.403E45241688@rubyforge.org> An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wxruby-development/attachments/20061017/57bef664/attachment-0001.html From nobody at rubyforge.org Tue Oct 17 17:50:07 2006 From: nobody at rubyforge.org (nobody at rubyforge.org) Date: Tue, 17 Oct 2006 17:50:07 -0400 (EDT) Subject: [Wxruby-development] [686] trunk/wxruby2/Changelog: Add Printing constants and typedefs, printing missing methods (Roy Message-ID: <20061017215007.B544FA970032@rubyforge.org> An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wxruby-development/attachments/20061017/4fcca415/attachment.html From alex at pressure.to Tue Oct 17 17:51:15 2006 From: alex at pressure.to (Alex Fenton) Date: Tue, 17 Oct 2006 22:51:15 +0100 Subject: [Wxruby-development] Printing Support In-Reply-To: <45352897.6010701@mindspring.com> References: <45344C3C.1000401@mindspring.com> <4534C20A.1040308@pressure.to> <45352897.6010701@mindspring.com> Message-ID: <45355053.1080504@pressure.to> Roy Sutton wrote: > [Note: I see Sean proposed a patch already similar to what I'm > posting here. This one has his changes and some others] Committed. I used Roy's code because it came from Windows, and b/c it had the extra stuff in typedefs.i. Thanks both for the patches. alex From wxruby at qualitycode.com Tue Oct 17 23:26:29 2006 From: wxruby at qualitycode.com (Kevin Smith) Date: Tue, 17 Oct 2006 23:26:29 -0400 Subject: [Wxruby-development] svn commits and other administrivia In-Reply-To: <4534F52A.8050605@pressure.to> References: <4534634C.3030809@mindspring.com> <4534C812.1080401@qualitycode.com> <4534F0DF.4050801@mindspring.com> <4534F52A.8050605@pressure.to> Message-ID: <45359EE5.1080708@qualitycode.com> Alex Fenton wrote: > Thanks - I'm also happy to do it. Also happy to take a lead on it if it > would help Roy focus on all the other stuff he is better qualified than > me to tackle. So let's try it with Alex and me as admins and moderators. If the two of us aren't enough, we'll pull in someone else. Thanks! Kevin From cabal at myrealbox.com Wed Oct 18 03:27:20 2006 From: cabal at myrealbox.com (Cabal) Date: Wed, 18 Oct 2006 08:27:20 +0100 Subject: [Wxruby-development] wxRuby-0.6.0, wxRuby2, SWIG and.... In-Reply-To: <45352F99.502@mindspring.com> References: <200610161428.42377.cabal@myrealbox.com> <200610171116.54751.cabal@myrealbox.com> <45352F99.502@mindspring.com> Message-ID: <200610180827.20647.cabal@myrealbox.com> > My understanding (which may be flawed!) of your code is that you have a > one-way wrapper that only allows Ruby to call into C++, not to allow C++ > to call into Ruby. > Roy, Thnx for the clarification - you are indeed correct. I have made no attempt or given any thought to someone wanting to get execution going the other way. At this stage I'm attempting a straight forward wrapper to enable Ruby access to functionality in C/C++ libs. Do you have any examples or projects where what you are suggesting has been done systematically (wxRuby2 perhaps?) - I wouldn't mind getting a heads up on the techniques involved. While it would be something to add after initial release, it would be a good idea to factor in requirements right now. Though having said that, if you say you get this for free from SWIG I have a feeling I'm going to be working on this for the next week or so... Cabal From alex at pressure.to Wed Oct 18 04:55:21 2006 From: alex at pressure.to (Alex Fenton) Date: Wed, 18 Oct 2006 09:55:21 +0100 Subject: [Wxruby-development] wxRuby-0.6.0, wxRuby2, SWIG and.... In-Reply-To: <200610180827.20647.cabal@myrealbox.com> References: <200610161428.42377.cabal@myrealbox.com> <200610171116.54751.cabal@myrealbox.com> <45352F99.502@mindspring.com> <200610180827.20647.cabal@myrealbox.com> Message-ID: <4535EBF9.9060908@pressure.to> Cabal wrote: > Do you have any examples or projects where what you are suggesting has been > done systematically (wxRuby2 perhaps?) WxRuby2 is one. We often want to inherit from the core classes but have them call Ruby methods. For example TreeCtrl implements a method 'on_compare_items' to control the sort order. Users can define this method in a Ruby subclass to customise how items in the tree are sorted. The library will pick this up and call the ruby subclass method from the C++ internals. > I wouldn't mind getting a heads up > on the techniques involved. Read up on 'directors' in the SWIG docs. There's little on Ruby specifically, but the python page should be helpful: http://www.swig.org/Doc1.3/Python.html (seems down at the moment) cheers alex From sean.m.long at gmail.com Wed Oct 18 18:52:08 2006 From: sean.m.long at gmail.com (Sean Long) Date: Wed, 18 Oct 2006 15:52:08 -0700 Subject: [Wxruby-development] Nightly automatic documentation generation Message-ID: Is there a way to have RubyForge run our 'rake html_docs' on SVN Head each night and if successful copy to http://wxruby.rubyforge.org/doc/? I do not know all the features RubyForge provides to us but this one would be pretty nice. Sean From alex at pressure.to Wed Oct 18 19:06:39 2006 From: alex at pressure.to (Alex Fenton) Date: Thu, 19 Oct 2006 00:06:39 +0100 Subject: [Wxruby-development] Nightly automatic documentation generation In-Reply-To: References: Message-ID: <4536B37F.9070904@pressure.to> Sean Long wrote: > Is there a way to have RubyForge run our 'rake html_docs' on SVN Head > each night and if successful copy to http://wxruby.rubyforge.org/doc/? > Good idea. I never get round to uploading the revised documentation. But I don't think Rubyforge offers a way to do this - they are limited user accounts. It's probably a bit much to ask Tom to run a custom cron job. I guess one way for now would be to run the process on a remote server which does an svn update, rake html_doc, scp, using someone's private key to authenticate. But it's a fiddly thing to set up. alex From alex at pressure.to Wed Oct 18 19:47:27 2006 From: alex at pressure.to (Alex Fenton) Date: Thu, 19 Oct 2006 00:47:27 +0100 Subject: [Wxruby-development] progress on porting wxscintilla Message-ID: <4536BD0F.5050605@pressure.to> I've made some progress on getting Scintilla to work on OS X. I got a static build of wxscintilla as libwxscintilla.a. To do this, turns out all I needed to do was make release But I had to go a tortuous route to find this out. Anyway, this gives me a library against which I can build the wxscintilla sample. It also builds without error when added to wxruby (following the model of rakemswin). I get a Scintilla.o, and a libwxscintilla.a is linked into wxruby2.bundle. All seems good, but when I run bigdemo.rb, I don't get Scintilla - it seems Scintilla isn't a constant. Any tips as to what might be happening? I wondered if I needed to build a unicode wxscintilla? thanks alex From roys at mindspring.com Wed Oct 18 22:53:47 2006 From: roys at mindspring.com (Roy Sutton) Date: Wed, 18 Oct 2006 22:53:47 -0400 Subject: [Wxruby-development] RubyConf Message-ID: <4536E8BB.9050200@mindspring.com> I might be a bit scarce this weekend -- I managed to score a late ticket to RubyConf! I'll be in Denver hobnobbing with Matz. :) Roy From roys at mindspring.com Thu Oct 19 00:26:54 2006 From: roys at mindspring.com (Roy Sutton) Date: Thu, 19 Oct 2006 00:26:54 -0400 Subject: [Wxruby-development] fixplatform patch Message-ID: <4536FE8E.3010405@mindspring.com> This patch implements a fix that gets rid of a spurious warning on MSVC. This should only affect mswin builds but I figured someone could at least try compiling and making sure it doesn't affect anything else. Roy -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: fixplatform.rb.patch Url: http://rubyforge.org/pipermail/wxruby-development/attachments/20061019/6bb30d93/attachment.pl From roys at mindspring.com Thu Oct 19 01:02:36 2006 From: roys at mindspring.com (Roy Sutton) Date: Thu, 19 Oct 2006 01:02:36 -0400 Subject: [Wxruby-development] Pen.i patch Message-ID: <453706EC.1040003@mindspring.com> This patch removes a swig warning. I deleted a malformed (and unneeded) typemap. Also, my previous patch doesn't get rid of the debug warning when compiling wx.cpp under debug mode on Windows. I may run fixplatform over wx.cpp if it won't hurt it. I'll test that and submit a patch if it's OK. Roy -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: Pen.i.patch Url: http://rubyforge.org/pipermail/wxruby-development/attachments/20061019/408562b2/attachment.ksh From roys at mindspring.com Thu Oct 19 01:30:28 2006 From: roys at mindspring.com (Roy Sutton) Date: Thu, 19 Oct 2006 01:30:28 -0400 Subject: [Wxruby-development] wxPen.h Message-ID: <45370D74.8010706@mindspring.com> wxPen.h #ifdefs out the stipple constructor for GTK but Pen.i %ignores the stipple functions (GetStipple, SetStipple). Shouldn't we follow the same path so we get GetStipple and SetStipple on Mac and Windows? I didn't attach a patch. Too tired. Hopefully someone else can whip that into shape. :) Roy From alex at pressure.to Thu Oct 19 04:26:31 2006 From: alex at pressure.to (Alex Fenton) Date: Thu, 19 Oct 2006 09:26:31 +0100 Subject: [Wxruby-development] wxPen.h In-Reply-To: <45370D74.8010706@mindspring.com> References: <45370D74.8010706@mindspring.com> Message-ID: <453736B7.1020600@pressure.to> Roy Sutton wrote: > wxPen.h #ifdefs out the stipple constructor for GTK but Pen.i %ignores > the stipple functions (GetStipple, SetStipple). Shouldn't we follow the > same path so we get GetStipple and SetStipple on Mac and Windows? Try the attached. It required a small change to header where the docs we generated from are wrong. thanks alex -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: pen_stipple.patch Url: http://rubyforge.org/pipermail/wxruby-development/attachments/20061019/4dcd6976/attachment.pl From nobody at rubyforge.org Thu Oct 19 04:31:42 2006 From: nobody at rubyforge.org (nobody at rubyforge.org) Date: Thu, 19 Oct 2006 04:31:42 -0400 (EDT) Subject: [Wxruby-development] [687] trunk/wxruby2/swig/classes/Pen.i: Remove a malformed and unneeded typemap (Roy Sutton) Message-ID: <20061019083142.7469852410DD@rubyforge.org> An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wxruby-development/attachments/20061019/209bed88/attachment.html From alex at pressure.to Thu Oct 19 04:33:23 2006 From: alex at pressure.to (Alex Fenton) Date: Thu, 19 Oct 2006 09:33:23 +0100 Subject: [Wxruby-development] READFIRST wxPen.h In-Reply-To: <45370D74.8010706@mindspring.com> References: <45370D74.8010706@mindspring.com> Message-ID: <45373853.2010409@pressure.to> Roy Sutton wrote: > wxPen.h #ifdefs out the stipple constructor for GTK but Pen.i %ignores > the stipple functions (GetStipple, SetStipple). Shouldn't we follow the > same path so we get GetStipple and SetStipple on Mac and Windows? Sorry, this is the correct patch with your previous change applied. alex -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: pen_stipple.patch Url: http://rubyforge.org/pipermail/wxruby-development/attachments/20061019/d0a299da/attachment.ksh From nobody at rubyforge.org Thu Oct 19 04:34:57 2006 From: nobody at rubyforge.org (nobody at rubyforge.org) Date: Thu, 19 Oct 2006 04:34:57 -0400 (EDT) Subject: [Wxruby-development] [688] trunk/wxruby2/swig/fixplatform.rb: Remove a spurious warning on Windows (Roy Sutton) Message-ID: <20061019083457.80A5D5241118@rubyforge.org> An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wxruby-development/attachments/20061019/cdb3cb9b/attachment.html From alex at pressure.to Thu Oct 19 04:35:56 2006 From: alex at pressure.to (Alex Fenton) Date: Thu, 19 Oct 2006 09:35:56 +0100 Subject: [Wxruby-development] fixplatform patch In-Reply-To: <4536FE8E.3010405@mindspring.com> References: <4536FE8E.3010405@mindspring.com> Message-ID: <453738EC.9050403@pressure.to> Roy Sutton wrote: > This patch implements a fix that gets rid of a spurious warning on > MSVC. This should only affect mswin builds but I figured someone > could at least try compiling and making sure it doesn't affect > anything else. Thanks, applied. I tweaked it slightly to avoid creating a local variable that's only used once, and updated the copyright alex From nobody at rubyforge.org Thu Oct 19 05:07:56 2006 From: nobody at rubyforge.org (nobody at rubyforge.org) Date: Thu, 19 Oct 2006 05:07:56 -0400 (EDT) Subject: [Wxruby-development] [689] trunk/wxruby2/Changelog: Pen fix and remove some compile warnings Message-ID: <20061019090756.8781C52411D3@rubyforge.org> An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wxruby-development/attachments/20061019/a51a0cdf/attachment.html From alex at pressure.to Thu Oct 19 06:14:21 2006 From: alex at pressure.to (Alex Fenton) Date: Thu, 19 Oct 2006 11:14:21 +0100 Subject: [Wxruby-development] Wx::Scintilla - working Message-ID: <45374FFD.8030401@pressure.to> At last, managed to get Scintilla up and running on OS X. Sorry it's taken so long. Patch attached to enable Scintilla to be included in a Mac build. More difficult was how figuring out how to get wxscintilla built in the first place - have added instructions on our 'Building for release' page on the wiki: http://wxruby.rubyforge.org/wiki/wiki.pl?Release_HowTo cheers alex -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: rakemacosx_scintilla.patch Url: http://rubyforge.org/pipermail/wxruby-development/attachments/20061019/5522f2b1/attachment.ksh From alex at pressure.to Thu Oct 19 06:17:04 2006 From: alex at pressure.to (Alex Fenton) Date: Thu, 19 Oct 2006 11:17:04 +0100 Subject: [Wxruby-development] remove global debugging from App.i Message-ID: <453750A0.70800@pressure.to> A small patch is attached which removes the always-on debugging output which appears at start up. If this output is still useful to someone I can resubmit using ifdef DEBUG. If it's not needed maybe this custom method could be removed completely? alex -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: App_i.patch Url: http://rubyforge.org/pipermail/wxruby-development/attachments/20061019/7a57401a/attachment.ksh From wxruby at qualitycode.com Thu Oct 19 08:17:33 2006 From: wxruby at qualitycode.com (Kevin Smith) Date: Thu, 19 Oct 2006 08:17:33 -0400 Subject: [Wxruby-development] wxRuby-0.6.0, wxRuby2, SWIG and.... In-Reply-To: <4535EBF9.9060908@pressure.to> References: <200610161428.42377.cabal@myrealbox.com> <200610171116.54751.cabal@myrealbox.com> <45352F99.502@mindspring.com> <200610180827.20647.cabal@myrealbox.com> <4535EBF9.9060908@pressure.to> Message-ID: <45376CDD.9070607@qualitycode.com> Alex Fenton wrote: > WxRuby2 is one. We often want to inherit from the core classes but have > them call Ruby methods. Yes. Generically there are two cases where C++ code needs to call into Ruby code: 1. Overriding, especially of pure virtual methods. In wx, these are mostly the on_xxx methods. If you can't override App#on_init, you can't really write a wx app. 2. Events. When something like a button is pressed, an event handler is called, and the user is going to want to write some Ruby code to respond to that event. Last time I checked, JRuby (Ruby running in a Java JVM) does not have this ability, which (as far as I can tell) makes it impossible to write GUI apps. They are working on it. In SWIG, directors do in fact give this to you "for free". You can look at the generated code for something like Wx::Button to see how directors are implemented. It's mostly straightforward, except that any call coming in to a director might be coming from the C++ side (in which case it needs to be sent to the Ruby code), or from the Ruby subclass code (in which case it needs to be forwarded up to the C++ code). They keep a boolean state to manage this, and we have had some problems where it does not work correctly, usually due to discrepancies between our declarations of the inheritance hierarchy vs. what wx actually has *on that platform* (the inheritance chain varies from platform to platform). Kevin From wxruby at qualitycode.com Thu Oct 19 08:40:52 2006 From: wxruby at qualitycode.com (Kevin Smith) Date: Thu, 19 Oct 2006 08:40:52 -0400 Subject: [Wxruby-development] wxRuby-0.6.0, wxRuby2, SWIG and.... In-Reply-To: <200610161428.42377.cabal@myrealbox.com> References: <200610161428.42377.cabal@myrealbox.com> Message-ID: <45377254.2000309@qualitycode.com> Cabal wrote: > Hi, my first post here so a little background first... > > wxRuby2 seems to have a work rate > issue (compared to progress on the original) that I wouldn't expect to exist > when using something like SWIG - I may be wrong and you think SWIG is the > best thing since sliced bread - but glancing (and I do mean glancing - this > isn't something I've investigated even cursorily - thats what this email is > for) SWIG seems to be a mixed bag of really good and really really bad > (impression gained from the doc on how to add a class to wxruby2). Hi, and thanks for sharing your thoughts and ideas. A little background on my experience: The first Ruby/C++ wrapper was Ruby/FLTK. I co-designed and wrote it, and we mostly used C macros. Not as elegant as C++ templates, but similar in concept, I think. By the time I left that project to switch to wx, it was clear to me that any practical solution would require code generation. Hand-generating code for 10,000 methods was not only time-consuming, but (more critically) error-prone. (Side note: I still like many things about FLTK, and think it is a great toolkit for certain applications. I switched to wx because of its native widgets, because I want my apps to be accessible to blind users.) My next project was wxruby, and as you have seen from the 0.6.0 code base, I created a simple wrapper-generator script. When I started, the script was very small and simple, and it was easy to get the first few classes wrapped. However, over time, the script grew and grew. Each new class, and each new category of method signature required changes to the script. It was hard for anyone other than me to add support for new classes. People were not motivated to learn about my script, because that knowledge would not help them on any other project. Method signature tweaks (such as int, int* -> Array) had to be hand-coded. Callbacks and virtual method overrides had to be hand-coded. Progress was slow. Around that time SWIG added Director support for Ruby, so when I re-evaluated SWIG it was clear to me that it could do what we needed. Thus, wxruby2 was born. It took far fewer person-hours to get wxruby2 to its current state than it took to get wxruby 0.6.0 to its state. Adding new classes is usually *much* easier with SWIG, and is rarely if ever more difficult than it would have been with 0.6.0. Contributors to wxruby2 can bring any existing SWIG knowledge with them, and can take SWIG knowledge with them to their next project. From a personal standpoint, when a defacto standard (like SWIG) is "good enough", there have to be compelling reasons not to use it. So that's my story. Code generation was mandatory, and SWIG was the easiest way to get there. > > As wxRuby is of immediate concern to me I'm using it as a testbed for this > C++/Ruby wrapper replacement and I'd like to know if you think there is any > future where you might find it more useful than SWIG for what you are trying > to do. I'm thinking that my template wrappers will have a more linear > application curve (ie not as good as SWIG at its best but nowhere near as bad > as SWIG in its worse case scenario). Honestly, I think your approach might have value for smaller libraries, but I would be very surprised if you were able to match wxruby2's current functionality any time soon. I remain open, however, and want to use the best technology for wxruby, and would be willing to switch if you could make a compelling case. (Side note: A co-worker is writing an RPC-like library that allows code from different languages to easily talk to each other. He has posed the possibility of creating a "wxruby" that is implemented by calling wxpython code. Instead of wrapping C++, we would wrap python in ruby. I have considered it, and if wxruby2 had not been started, I would probably prototype it to see if it would be a viable option.) > My apologies if I have misread what has been said regarding the ease with > which SWIG does its job and if thats so just put me straight right away... It's probably not as bad as you think. We have hit a few SWIG bugs, and most of those have been fixed. Some SWIG features are really hard to understand how to use, but once we learn them, they are easy to apply. Many of our remaining problems are due more to the cross-platform variations of wx than to SWIG itself. > > I've attached button.cpp and button.h which are my current drop-in > replacements for the original wxRuby-0.6.0 files of the same name. I may post > the code inline if there is an issue with attachments on this mailing list. Your code looks fine. If you can address the issues Roy mentioned, and at some point auto-generate everything, it could be a cool tool. Kevin From wxruby at qualitycode.com Thu Oct 19 08:57:49 2006 From: wxruby at qualitycode.com (Kevin Smith) Date: Thu, 19 Oct 2006 08:57:49 -0400 Subject: [Wxruby-development] wxRuby-0.6.0, wxRuby2, SWIG and.... In-Reply-To: <200610162025.47133.cabal@myrealbox.com> References: <200610161428.42377.cabal@myrealbox.com> <4533A712.5000706@mindspring.com> <200610162025.47133.cabal@myrealbox.com> Message-ID: <4537764D.6000309@qualitycode.com> >> Having said that, if you have a solution to wrapping libraries that's >> specific to Ruby and can deal with: >> >> - overriding C++ methods from Ruby > Not sure I understand this one. Do you mean just being able to call the C++ > methods from Ruby? Once ruby knows how to call a method then 'overriding' > would be an ability handled by ruby in some derived class... We covered this one in other emails. >> - pointer arguments that could be input, output or both > I don't see any issues with handling pointers (not at this point anyway). I've > got a few specialisations on wx pointer types already. "Output pointers" generally need to be converted to ruby return values. SWIG allows use to describe the pattern and it generates the code automatically. >> - complex argument and return types > I presume you're talking about non-pod datatypes and references and pointers > to them. No issues upto now for wx types passed as arguments and return > values. >> - conversion of arguments from ruby types to C/C++ types > One of the easier bits. Here again, SWIG allows us to declare once that String<->wxString, etc. You'll definitely want to avoid having to hand-code each case. >> - collapsing/expanding of arguments (e.g. ruby array to int n, char ** >> lines) > At the minute I'm concentrating on passing args using 'int argc, VALUE* argv' > method signatures and upto 10 VALUE arguments. From the existing code that > I've looked at I haven't seen much cause for expanding and collapsing ruby > arrays as a separate operation per se. I'm not sure what you mean by this. From ruby, if you have an array, you certainly don't want to pass both the array length and the array itself. In 0.6.0 we hand-coded each case to only take the array and not also the length. That's probably what you are doing as well. SWIG allows us to declare the pattern once, and it will fold them for us. >> - memory management > I've specialised the templates for wx objects to link memory management into > the wxObjectRefData class. The wrapper will require some sort of help along > these lines whichever C++ library it is used for - but I can't see that being > any different for any other method of wrapping a library. There are some tricky issues with ownership. As you know, a new object might be created in response to a ruby "new" call, or might have been created by the C++ library and wrapped so it can be used in ruby. Later, the ruby code might want to dispose of the object, in which case C++ needs to be notified. Or C++ might dispose of the objects on its own, in which case the Ruby object needs to get disconnected. We have started addressing this in wxruby2, thanks to some SWIG features that are hard to understand, but which do all the hard work for us. It's an issue we did not really solve in wxruby 0.6.0, and was one of the reasons we switched to SWIG. > Yes - I'd got that impression :) Unfortunately wxRuby2 didn't look like it was > going to be released in a usable form anytime soon (now rectified, > possibly :) ) The pace of development of wxruby2 has been frustrating. It has been "pretty close" for a very long time, but I (and others) just haven't had enough time to work on it. Fortunately, Alex and Roy have stepped in and have done most of the work for the last few months, bringing us to our first alpha release. > and now I've got my teeth into this I'm keen to see where it > leads. I hope it will prove useful somewhere along the lines to wxRuby2 (as > you've kindly provided me with a testbed and copious examples in 0.6.0) but I > won't go bugging you about it :) Understood. I hope we have helped you, and that your project will end up being useful, whether to us or to someone else. Paraphrasing a famous quote: "SWIG is the worst wrapping tool...except for all the others." None of us love SWIG, but it is far better than anything else I have seen so far. If you can provide an easier way for ruby folk to wrap C++ libraries, I would be very happy. > Good luck and happy coding... And to you. Kevin From noreply at rubyforge.org Thu Oct 19 08:39:39 2006 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Thu, 19 Oct 2006 08:39:39 -0400 (EDT) Subject: [Wxruby-development] [ wxruby-Bugs-6234 ] ScrolledWindow very messed up on Windows Message-ID: <20061019123939.DBC605241292@rubyforge.org> Bugs item #6234, was opened at 2006-10-19 12:39 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=218&aid=6234&group_id=35 Category: Incorrect behavior Group: None Status: Open Resolution: None Priority: 5 Submitted By: Alex Fenton (brokentoy) Assigned to: Roy Sutton (roys) Summary: ScrolledWindow very messed up on Windows Initial Comment: The ScrolledWindow example within bigdemo starts creating artifacts all over the screen outside the window area. It actually rendered my whole desktop unusable with the CPU whistling, and had to restart using the power button. Erk! ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=218&aid=6234&group_id=35 From noreply at rubyforge.org Thu Oct 19 08:43:45 2006 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Thu, 19 Oct 2006 08:43:45 -0400 (EDT) Subject: [Wxruby-development] [ wxruby-Bugs-6235 ] KeyEvent#get_key_code not working properly on OS X Message-ID: <20061019124345.70DF652412AA@rubyforge.org> Bugs item #6235, was opened at 2006-10-19 12:43 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=218&aid=6235&group_id=35 Category: Incorrect behavior Group: current Status: Open Resolution: None Priority: 4 Submitted By: Alex Fenton (brokentoy) Assigned to: Kevin Smith (qualitycode) Summary: KeyEvent#get_key_code not working properly on OS X Initial Comment: The wrong values are getting returned from KeyEvent#get_key_code on OS X, unicode builds. This is visible in the caret sample; if the arrow keys are used to try and move the cursor, rubbish characters are instead inserted into the sample - because the values don't match the ARROW_UP etc constants. Windows unicode build (0.0.36) works correctly in the caret sample. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=218&aid=6235&group_id=35 From roys at mindspring.com Thu Oct 19 10:42:28 2006 From: roys at mindspring.com (Roy Sutton) Date: Thu, 19 Oct 2006 10:42:28 -0400 Subject: [Wxruby-development] READFIRST wxPen.h In-Reply-To: <45373853.2010409@pressure.to> References: <45370D74.8010706@mindspring.com> <45373853.2010409@pressure.to> Message-ID: <45378ED4.6050004@mindspring.com> Alex Fenton wrote: > Roy Sutton wrote: >> wxPen.h #ifdefs out the stipple constructor for GTK but Pen.i >> %ignores the stipple functions (GetStipple, SetStipple). Shouldn't >> we follow the same path so we get GetStipple and SetStipple on Mac >> and Windows? > Sorry, this is the correct patch with your previous change applied. > Alex, this patch looks the same as the previous one to me. How's this look? Roy -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: wxPen.h.patch Url: http://rubyforge.org/pipermail/wxruby-development/attachments/20061019/095dbc17/attachment.pl From sean.m.long at gmail.com Thu Oct 19 11:07:17 2006 From: sean.m.long at gmail.com (Sean Long) Date: Thu, 19 Oct 2006 08:07:17 -0700 Subject: [Wxruby-development] RubyConf In-Reply-To: <4536E8BB.9050200@mindspring.com> References: <4536E8BB.9050200@mindspring.com> Message-ID: Lucky guy! Sean On 10/18/06, Roy Sutton wrote: > I might be a bit scarce this weekend -- I managed to score a late ticket > to RubyConf! I'll be in Denver hobnobbing with Matz. :) > > Roy > _______________________________________________ > Wxruby-development mailing list > Wxruby-development at rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-development > From alex at pressure.to Thu Oct 19 11:47:26 2006 From: alex at pressure.to (Alex Fenton) Date: Thu, 19 Oct 2006 16:47:26 +0100 Subject: [Wxruby-development] READFIRST wxPen.h In-Reply-To: <45378ED4.6050004@mindspring.com> References: <45370D74.8010706@mindspring.com> <45373853.2010409@pressure.to> <45378ED4.6050004@mindspring.com> Message-ID: <45379E0E.7060205@pressure.to> Roy Sutton wrote: > Alex, this patch looks the same as the previous one to me. How's this > look? > The change was the same, the context in Pen.i was wrong in the old one b/c I didn't apply your previous change first. Though I expect you'd have figured it out ;). I don't have Linux so I don't know if GetStipple and SetStipple actually need to be undef'd. If you think yes or probably, please apply. Have a great time at RubyConf btw. We should have got ya a WxRuby T-shirt and baseball cap to wear! Thanks alex From roys at mindspring.com Thu Oct 19 12:04:11 2006 From: roys at mindspring.com (Roy Sutton) Date: Thu, 19 Oct 2006 12:04:11 -0400 Subject: [Wxruby-development] Wx::Scintilla - working In-Reply-To: <45374FFD.8030401@pressure.to> References: <45374FFD.8030401@pressure.to> Message-ID: <4537A1FB.5040505@mindspring.com> Alex Fenton wrote: > At last, managed to get Scintilla up and running on OS X. Sorry it's > taken so long. No problem! I've still not gotten it to build on Linux yet. I'll peek over what you've done to see if it applies there, too. Glad we've got it working on two platforms at least. Roy From nobody at rubyforge.org Thu Oct 19 12:48:20 2006 From: nobody at rubyforge.org (nobody at rubyforge.org) Date: Thu, 19 Oct 2006 12:48:20 -0400 (EDT) Subject: [Wxruby-development] [690] trunk/wxruby2/samples/text/unicode.rb: Placed controls within a panel so they appear on the correct themed background Message-ID: <20061019164820.2ECDF52417E0@rubyforge.org> An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wxruby-development/attachments/20061019/2607e123/attachment-0001.html From nobody at rubyforge.org Thu Oct 19 13:04:30 2006 From: nobody at rubyforge.org (nobody at rubyforge.org) Date: Thu, 19 Oct 2006 13:04:30 -0400 (EDT) Subject: [Wxruby-development] [691] trunk/wxruby2/samples/calendar/calendar.rb: Placed controls within a panel so they appear on the correct themed background Message-ID: <20061019170430.32E4F52417E6@rubyforge.org> An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wxruby-development/attachments/20061019/d03e40fe/attachment.html From alex at pressure.to Thu Oct 19 13:26:02 2006 From: alex at pressure.to (Alex Fenton) Date: Thu, 19 Oct 2006 18:26:02 +0100 Subject: [Wxruby-development] Nightly automatic documentation generation In-Reply-To: References: Message-ID: <4537B52A.5080209@pressure.to> Sean Long wrote: > Is there a way to have RubyForge run our 'rake html_docs' on SVN Head > each night and if successful copy to http://wxruby.rubyforge.org/doc/? > As a stop gap, here's a patch adding a rake task to automate publishing the documentation to the website. You need to tell it your Rubyforge id. rake publish_docs RUBYFORGE_USER=johnsmith alex -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: rakedoc_rb.patch Url: http://rubyforge.org/pipermail/wxruby-development/attachments/20061019/123f04fe/attachment.pl From nobody at rubyforge.org Thu Oct 19 13:34:24 2006 From: nobody at rubyforge.org (nobody at rubyforge.org) Date: Thu, 19 Oct 2006 13:34:24 -0400 (EDT) Subject: [Wxruby-development] [692] trunk/wxsugar/Rakefile: Correct a typo in the Rakefile Message-ID: <20061019173427.3A65352417E3@rubyforge.org> An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wxruby-development/attachments/20061019/f82862d3/attachment.html From nobody at rubyforge.org Thu Oct 19 13:38:46 2006 From: nobody at rubyforge.org (nobody at rubyforge.org) Date: Thu, 19 Oct 2006 13:38:46 -0400 (EDT) Subject: [Wxruby-development] [693] tags/wxsugar/0.1.2/: Tagged 0.1.2 Message-ID: <20061019173848.1BA4B52417F0@rubyforge.org> An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wxruby-development/attachments/20061019/14fae644/attachment.html From nobody at rubyforge.org Thu Oct 19 14:20:51 2006 From: nobody at rubyforge.org (nobody at rubyforge.org) Date: Thu, 19 Oct 2006 14:20:51 -0400 (EDT) Subject: [Wxruby-development] [694] trunk/wxruby2/doc/textile: Added back the logging classes which were over-zealously removed when Message-ID: <20061019182051.E5CCC524180B@rubyforge.org> An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wxruby-development/attachments/20061019/8be7d888/attachment.html From alex at pressure.to Thu Oct 19 17:30:05 2006 From: alex at pressure.to (Alex Fenton) Date: Thu, 19 Oct 2006 22:30:05 +0100 Subject: [Wxruby-development] Wx::Scintilla - working In-Reply-To: <4537A1FB.5040505@mindspring.com> References: <45374FFD.8030401@pressure.to> <4537A1FB.5040505@mindspring.com> Message-ID: <4537EE5D.9030702@pressure.to> Roy Sutton wrote: > Alex Fenton wrote: > >> At last, managed to get Scintilla up and running on OS X. Sorry it's >> taken so long. >> > No problem! I've still not gotten it to build on Linux yet. Cool - hopefully should be pretty similar. The key was figuring out that 'make release' built wxscintilla the way we wanted - then I just pointed your rake code at the right directory and file (lib/libwxscintilla) and it worked. I tried out building off wxscintilla CVS head and it worked, so Otto says he plans to do a 1.71 release soon. a From sean.m.long at gmail.com Thu Oct 19 17:43:57 2006 From: sean.m.long at gmail.com (Sean Long) Date: Thu, 19 Oct 2006 14:43:57 -0700 Subject: [Wxruby-development] Nightly automatic documentation generation In-Reply-To: <4537B52A.5080209@pressure.to> References: <4537B52A.5080209@pressure.to> Message-ID: That is a good idea, when I get some time I will have to try it out. thanks Sean On 10/19/06, Alex Fenton wrote: > Sean Long wrote: > > Is there a way to have RubyForge run our 'rake html_docs' on SVN Head > > each night and if successful copy to http://wxruby.rubyforge.org/doc/? > > > As a stop gap, here's a patch adding a rake task to automate publishing > the documentation to the website. You need to tell it your Rubyforge id. > > rake publish_docs RUBYFORGE_USER=johnsmith > > alex > > > Index: wxruby2/rake/rakedocs.rb > =================================================================== > --- wxruby2/rake/rakedocs.rb (revision 689) > +++ wxruby2/rake/rakedocs.rb (working copy) > @@ -108,3 +108,18 @@ > end > desc "Tarball the HTML documentation" > task :doc_tar_gz => [ doc_tar_gz_package ] > + > +# set the rubyforge username for publishing to the website > +RUBYFORGE_USER = ENV['RUBYFORGE_USER'] > + > +desc 'Publish rendered docs and sources to the wxRuby website, using scp' > +task :publish_docs => [ :html_docs ] do | t | > + if not RUBYFORGE_USER > + raise 'Must specify RUBYFORGE_USER to publish documents' > + end > + # the location we are publishing to > + dest = "#{RUBYFORGE_USER}@rubyforge.org:/var/www/gforge-projects/wxruby/doc/" > + sh "scp doc/html/*.html #{dest}" > + sh "scp doc/html/*.css #{dest}" > + sh "scp doc/textile/*.txtl #{dest}" > +end > > > _______________________________________________ > Wxruby-development mailing list > Wxruby-development at rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-development > > > From wxruby at qualitycode.com Thu Oct 19 21:50:57 2006 From: wxruby at qualitycode.com (Kevin Smith) Date: Thu, 19 Oct 2006 21:50:57 -0400 Subject: [Wxruby-development] remove global debugging from App.i In-Reply-To: <453750A0.70800@pressure.to> References: <453750A0.70800@pressure.to> Message-ID: <45382B81.4070303@qualitycode.com> Alex Fenton wrote: > A small patch is attached which removes the always-on debugging output > which appears at start up. +1. It was needed during early development, but is pointless now. > If it's not needed maybe this custom method could be removed completely? As long as removing it doesn't cause things to obviously stop working, it should be fine to delete it completely. Kevin From wxruby at qualitycode.com Thu Oct 19 21:59:10 2006 From: wxruby at qualitycode.com (Kevin Smith) Date: Thu, 19 Oct 2006 21:59:10 -0400 Subject: [Wxruby-development] include Wx in samples? In-Reply-To: <4534CA76.5050609@pressure.to> References: <45342896.20005@mindspring.com> <4534CA76.5050609@pressure.to> Message-ID: <45382D6E.2080405@qualitycode.com> Alex Fenton wrote: > Just for reference, it should be Wx::PLATFORM now (from > swig/RubyConstants). If scripts are referring to RUBY_PLATFORM, they are > referring to Ruby's constant in the main namespace (eg i686-mswin) not > our WXMSW. I find the const confusion one reason not to 'include Wx' in > samples, but appreciate it's a matter of taste. Yes. I prefer not to include Wx because of various possible namespace collisions. However, we should probably have at least one sample (maybe minimal.rb) written two ways--one with include Wx and the other without. That way people could see the difference and decide for themselves. Also, we could point to the one with the include if we are trying to stress how easy and friendly wxruby app code can look. Just a thought. Kevin From wxruby at qualitycode.com Thu Oct 19 22:05:49 2006 From: wxruby at qualitycode.com (Kevin Smith) Date: Thu, 19 Oct 2006 22:05:49 -0400 Subject: [Wxruby-development] Nightly Linux build? Message-ID: <45382EFD.5070400@qualitycode.com> Hey guys, I'm really sorry to be so out of touch these days. We just hired two new programmers at work so I'm busy bringing them up to speed...in time for them to help us get a major release out at the end of the year. So my personal goals for wxruby participation at the moment are: 1. Respond to any support requests as quickly as possible 2. Respond to any questions from you developers asap 3. Glance at patches when possible, and reply only if I see a problem Beyond that, it occurred to me that I could set up a nightly cron job on my Linux box to pull from SVN, build, and somehow put some results up somewhere. If that would help you detect accidental Linux wx API incompatibilities sooner, I can try to do it. We could even host a "nightly build" Linux binary gem somewhere for folks wanting to live on the bleeding edge. Thoughts? Kevin From wxruby at qualitycode.com Thu Oct 19 22:07:09 2006 From: wxruby at qualitycode.com (Kevin Smith) Date: Thu, 19 Oct 2006 22:07:09 -0400 Subject: [Wxruby-development] Activity stats In-Reply-To: <4531DC4E.8010605@mindspring.com> References: <45313D28.9010004@mindspring.com> <45315D8A.6040503@qualitycode.com> <4531DC4E.8010605@mindspring.com> Message-ID: <45382F4D.7070709@qualitycode.com> Roy Sutton wrote: > Kevin Smith wrote: >> I'm more frustrated that it is impossible (?) to find out how many >> people downloaded wxruby2 last week, whether from the Files section or >> via gem. The "all time" number is available, but not week-by-week. >> >> > http://rubyforge.org/project/stats/index.php?group_id=35&area=downloads&SPAN=1&start=1159660800&end=1162339200&submit=Refresh > > That's Daily. Change the date ranges and period to Weekly if you want > that. Not enough weeks in October to really help that. Does that include installs directly from gem, too? Kevin From wxruby at qualitycode.com Thu Oct 19 22:12:23 2006 From: wxruby at qualitycode.com (Kevin Smith) Date: Thu, 19 Oct 2006 22:12:23 -0400 Subject: [Wxruby-development] [Wxruby-users] Window.i In-Reply-To: <451D7729.2060400@pressure.to> References: <4519C56B.3030506@mindspring.com> <451D7729.2060400@pressure.to> Message-ID: <45383087.80705@qualitycode.com> Sorry for the late reply. Trying to clear out my wxruby inbox. Alex Fenton wrote: > Roy Sutton wrote: >> Also, >> given that wxWindow.h is included all over the place, I think we need to >> move some of that stuff out into a common .i that's included for all >> wxWindow descendants. >> > > Not certain which stuff you're thinking of. Generally, I think I prefer > to keep the header files reasonably closely aligned with the > organisation of methods in WxWidgets, but I'm open to discussion. I would also like to know more specifically what parts you are thinking of. I'm a big fan of eliminating duplicate code, when possible. Kevin From wxruby at qualitycode.com Thu Oct 19 22:15:02 2006 From: wxruby at qualitycode.com (Kevin Smith) Date: Thu, 19 Oct 2006 22:15:02 -0400 Subject: [Wxruby-development] [Wxruby-users] ObjectPreviouslyDeleted when trying to paint In-Reply-To: <45208F61.1040709@qualitycode.com> References: <489be1d0609282007l84cf3ffiacf802c879f31091@mail.gmail.com> <45208F61.1040709@qualitycode.com> Message-ID: <45383126.3050101@qualitycode.com> This one seems like really high priority, since it is a feature specific to wxruby. If we want people to do things "the right way", we should indoctrinate them from the start. Probably a release blocker for 0.0.38 (not for 0.0.37 because I still think we should push that one out asap to avoid confusion with the 2 different .36 gems floating around). This paint thing used to work, so I'm hoping it will be an easy fix. I just haven't had a chance to look at it. Maybe this weekend. Kevin Kevin Smith wrote: > Toby Butzon wrote: >> mainframe on_paint >> ./View/mainframe.rb:79:in `clear': in method 'Clear', argument 1 of >> type 'wxWindowDC *' (ObjectPreviouslyDeleted) >> from ./View/mainframe.rb:79:in `on_paint' >> from ./View/mainframe.rb:78:in `paint' >> from ./View/mainframe.rb:78:in `on_paint' >> from ./View/mainframe.rb:29:in `initialize' >> ... >> >> Anyone have an idea of what might be going on? Is there a "better" way >> to trigger the redraw? > > As far as I know, you are doing everything exactly right. > > I have seen the same problem, but haven't yet had time to debug it. It > seems to be a bug in paint (which we added as a bit of sugar on top of > raw wx), so you should be able to work around it for now by creating > your own PaintDC inside your on_paint method. This might cause a memory > leak (not certain) so when paint is working again your should switch > back to it. > > In your case, something like: > > def on_paint > puts "mainframe on_paint" > dc = Wx::PaintDC.new(self) > dc.clear > @cl.draw dc > end > > > Kevin > > _______________________________________________ > wxruby-users mailing list > wxruby-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-users From sean.m.long at gmail.com Fri Oct 20 00:20:44 2006 From: sean.m.long at gmail.com (Sean Long) Date: Thu, 19 Oct 2006 21:20:44 -0700 Subject: [Wxruby-development] Nightly Linux build? In-Reply-To: <45382EFD.5070400@qualitycode.com> References: <45382EFD.5070400@qualitycode.com> Message-ID: I thought about doing this for OS X Intel since my machine is on 24x7 anyway, it just has not been real high on the priority list. If you come up with some good scripts to do it let me know they will probably work fine on OS X also. If I come up with something I will let you know. I thought about setting up DamageControl CI (Continuous Integration) http://damagecontrol.codehaus.org/, but when I went to their website today it looks like the project is not active currently. Sean From roys at mindspring.com Fri Oct 20 02:29:03 2006 From: roys at mindspring.com (Roy Sutton) Date: Fri, 20 Oct 2006 02:29:03 -0400 Subject: [Wxruby-development] Nightly Linux build? In-Reply-To: References: <45382EFD.5070400@qualitycode.com> Message-ID: <45386CAF.1070608@mindspring.com> I can set up a machine to do a nightly build on Windows also. Sean Long wrote: > I thought about doing this for OS X Intel since my machine is on 24x7 > anyway, it just has not been real high on the priority list. If you > come up with some good scripts to do it let me know they will probably > work fine on OS X also. > > If I come up with something I will let you know. > > I thought about setting up DamageControl CI (Continuous Integration) > http://damagecontrol.codehaus.org/, but when I went to their website > today it looks like the project is not active currently. > > Sean > _______________________________________________ > Wxruby-development mailing list > Wxruby-development at rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-development > > > > From roys at mindspring.com Fri Oct 20 02:29:47 2006 From: roys at mindspring.com (Roy Sutton) Date: Fri, 20 Oct 2006 02:29:47 -0400 Subject: [Wxruby-development] [Wxruby-users] ObjectPreviouslyDeleted when trying to paint In-Reply-To: <45383126.3050101@qualitycode.com> References: <489be1d0609282007l84cf3ffiacf802c879f31091@mail.gmail.com> <45208F61.1040709@qualitycode.com> <45383126.3050101@qualitycode.com> Message-ID: <45386CDB.8040703@mindspring.com> Kevin Smith wrote: > This one seems like really high priority, since it is a feature specific > to wxruby. If we want people to do things "the right way", we should > indoctrinate them from the start. Probably a release blocker for 0.0.38 > (not for 0.0.37 because I still think we should push that one out asap > to avoid confusion with the 2 different .36 gems floating around). > > This paint thing used to work, so I'm hoping it will be an easy fix. I > just haven't had a chance to look at it. Maybe this weekend. > I think it's just more of our memory management issues. From roys at mindspring.com Fri Oct 20 02:36:38 2006 From: roys at mindspring.com (Roy Sutton) Date: Fri, 20 Oct 2006 02:36:38 -0400 Subject: [Wxruby-development] [Wxruby-users] Window.i In-Reply-To: <45383087.80705@qualitycode.com> References: <4519C56B.3030506@mindspring.com> <451D7729.2060400@pressure.to> <45383087.80705@qualitycode.com> Message-ID: <45386E76.7050801@mindspring.com> Kevin Smith wrote: > Sorry for the late reply. Trying to clear out my wxruby inbox. > > Alex Fenton wrote: > >> Roy Sutton wrote: >> >>> Also, >>> given that wxWindow.h is included all over the place, I think we need to >>> move some of that stuff out into a common .i that's included for all >>> wxWindow descendants. >>> >>> >> Not certain which stuff you're thinking of. Generally, I think I prefer >> to keep the header files reasonably closely aligned with the >> organisation of methods in WxWidgets, but I'm open to discussion. >> > > I would also like to know more specifically what parts you are thinking > of. I'm a big fan of eliminating duplicate code, when possible. wxWindows.h is included by many, many files. Any typemaps or SWIG directives in Window.i have to be duplicated in every .i file. Or, we make a common one. Roy From sean.m.long at gmail.com Fri Oct 20 03:45:18 2006 From: sean.m.long at gmail.com (Sean Long) Date: Fri, 20 Oct 2006 00:45:18 -0700 Subject: [Wxruby-development] Nightly Linux build? In-Reply-To: <45386CAF.1070608@mindspring.com> References: <45382EFD.5070400@qualitycode.com> <45386CAF.1070608@mindspring.com> Message-ID: I just whipped up this script to do a nightly build and upload to a web server. It does: - download a fresh copy of SVN HEAD - creates a gem - appends the current date to the gem name - uploads the gem to a web server via sftp It requires the net_sftp gem Sean On 10/19/06, Roy Sutton wrote: > I can set up a machine to do a nightly build on Windows also. > > Sean Long wrote: > > I thought about doing this for OS X Intel since my machine is on 24x7 > > anyway, it just has not been real high on the priority list. If you > > come up with some good scripts to do it let me know they will probably > > work fine on OS X also. > > > > If I come up with something I will let you know. > > > > I thought about setting up DamageControl CI (Continuous Integration) > > http://damagecontrol.codehaus.org/, but when I went to their website > > today it looks like the project is not active currently. > > > > Sean > > _______________________________________________ > > Wxruby-development mailing list > > Wxruby-development at rubyforge.org > > http://rubyforge.org/mailman/listinfo/wxruby-development > > > > > > > > > _______________________________________________ > Wxruby-development mailing list > Wxruby-development at rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-development > -------------- next part -------------- A non-text attachment was scrubbed... Name: nightly_build.rb Type: text/x-ruby-script Size: 1297 bytes Desc: not available Url : http://rubyforge.org/pipermail/wxruby-development/attachments/20061020/3b2735a8/attachment-0001.bin From alex at pressure.to Fri Oct 20 04:16:42 2006 From: alex at pressure.to (Alex Fenton) Date: Fri, 20 Oct 2006 09:16:42 +0100 Subject: [Wxruby-development] [Wxruby-users] ObjectPreviouslyDeleted when trying to paint In-Reply-To: <45383126.3050101@qualitycode.com> References: <489be1d0609282007l84cf3ffiacf802c879f31091@mail.gmail.com> <45208F61.1040709@qualitycode.com> <45383126.3050101@qualitycode.com> Message-ID: <453885EA.6030901@pressure.to> Kevin Smith wrote: > This one seems like really high priority, since it is a feature specific > to wxruby. I agree this should be a high priority fix. Rather than waiting around trying to fix the SWIG wrapper, how about redoing this method in Ruby, something like (untested): def paint yield Wx::PaintDC(self) end It would leave us with a possible memory leak, but that's something we need to address more generally down the line. Perhaps better than carrying along a crasher? alex From wxruby at qualitycode.com Fri Oct 20 09:02:33 2006 From: wxruby at qualitycode.com (Kevin Smith) Date: Fri, 20 Oct 2006 09:02:33 -0400 Subject: [Wxruby-development] [Wxruby-users] ObjectPreviouslyDeleted when trying to paint In-Reply-To: <453885EA.6030901@pressure.to> References: <489be1d0609282007l84cf3ffiacf802c879f31091@mail.gmail.com> <45208F61.1040709@qualitycode.com> <45383126.3050101@qualitycode.com> <453885EA.6030901@pressure.to> Message-ID: <4538C8E9.5070302@qualitycode.com> Alex Fenton wrote: > I agree this should be a high priority fix. Rather than waiting around > trying to fix the SWIG wrapper, how about redoing this method in Ruby, > something like (untested): > > def paint > yield Wx::PaintDC(self) > end Brilliant. As long as we remember to do the right thing eventually, I would be very happy with this approach as a short-term solution. Thanks! Kevin From wxruby at qualitycode.com Fri Oct 20 09:07:24 2006 From: wxruby at qualitycode.com (Kevin Smith) Date: Fri, 20 Oct 2006 09:07:24 -0400 Subject: [Wxruby-development] Nightly Linux build? In-Reply-To: References: <45382EFD.5070400@qualitycode.com> <45386CAF.1070608@mindspring.com> Message-ID: <4538CA0C.8030706@qualitycode.com> Sean Long wrote: > I just whipped up this script to do a nightly build and upload to a web > server. Very cool. Thanks. I think having nightly gems on all 3 (4) platforms would be great. > > It does: > - download a fresh copy of SVN HEAD > - creates a gem > - appends the current date to the gem name Can/does it also stick today's date in the version strings? I don't want someone to have it installed and then think they are using a production release if they ask for the version. > - uploads the gem to a web server via sftp Depending on where we host the results, I might need to do scp pushes instead. Is there somewhere on the rubyforge server that we could use? I have a server I could push my stuff to, but would rather not grant anyone else write access because I haven't locked it down sufficiently yet. Kevin From alex at pressure.to Fri Oct 20 10:27:36 2006 From: alex at pressure.to (Alex Fenton) Date: Fri, 20 Oct 2006 15:27:36 +0100 Subject: [Wxruby-development] Good news on WxWidgets 2.8.0 Message-ID: <4538DCD8.8070807@pressure.to> Hi Just tried out the most recent dev release (2.7.1) of WxWidgets. The first bit of good news is that 2.7.1 has lots of attractive new widgets, such as RichTextCtrl, pickers, and the AUI. This is an add-on that's now been merged into the core, and provides sophisticated things like dockable toolbars, perspective layouts, semi-transparent dragging etc. They seem to have brushed up the Mac version of AUI, and the sample had me drooling. The second is that it looks like it will be straightforward for wxRuby to target 2.8 (famous last words...). The changes are simple API changes, mainly to base classes like Window, Dialog and ControlWithItems. Just by fixing two lines in Window, I got about 80% of our current classes compiled. The remaining errors look easy enough that I could fix them, which is a good sign ;) 2.8.0 is meant to be out in a few weeks - I'm not planning to do anything real until then. My sense is that we will be able to support both 2.6 and 2.8 with some judicious ifdefs, without it getting too messy. I'm fairly keen to continue 2.6.3 support, since it'll be a while before 2.8 builds start showing up in binary, eg in Linux distros. alex From nobody at rubyforge.org Fri Oct 20 15:32:51 2006 From: nobody at rubyforge.org (nobody at rubyforge.org) Date: Fri, 20 Oct 2006 15:32:51 -0400 (EDT) Subject: [Wxruby-development] [695] trunk/wxruby2/swig/classes/include/wxPen.h: Get/SetStipple not available on GTK Message-ID: <20061020193251.5558A5241B07@rubyforge.org> An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wxruby-development/attachments/20061020/7dc94f7b/attachment.html From roys at mindspring.com Fri Oct 20 15:40:18 2006 From: roys at mindspring.com (Roy Sutton) Date: Fri, 20 Oct 2006 15:40:18 -0400 Subject: [Wxruby-development] Nightly Linux build? In-Reply-To: <45382EFD.5070400@qualitycode.com> References: <45382EFD.5070400@qualitycode.com> Message-ID: <45392622.8020304@mindspring.com> Kevin Smith wrote: > Hey guys, > > I'm really sorry to be so out of touch these days. We just hired two new > programmers at work so I'm busy bringing them up to speed...in time for > them to help us get a major release out at the end of the year. > Not a problem. Happens to us all. > So my personal goals for wxruby participation at the moment are: > 1. Respond to any support requests as quickly as possible > 2. Respond to any questions from you developers asap > 3. Glance at patches when possible, and reply only if I see a problem > > Beyond that, it occurred to me that I could set up a nightly cron job on > my Linux box to pull from SVN, build, and somehow put some results up > somewhere. If that would help you detect accidental Linux wx API > incompatibilities sooner, I can try to do it. We could even host a > "nightly build" Linux binary gem somewhere for folks wanting to live on > the bleeding edge. > Sounds good. I have been compiling on my Linux box anything that I think might affect the build process. It just takes a couple hours to compile everything (wx, wxRuby) if I have to rebuild. Fortunately testing a simple change doesn't take that long. :) > Thoughts? > > From roys at mindspring.com Fri Oct 20 15:40:55 2006 From: roys at mindspring.com (Roy Sutton) Date: Fri, 20 Oct 2006 15:40:55 -0400 Subject: [Wxruby-development] Activity stats In-Reply-To: <45382F4D.7070709@qualitycode.com> References: <45313D28.9010004@mindspring.com> <45315D8A.6040503@qualitycode.com> <4531DC4E.8010605@mindspring.com> <45382F4D.7070709@qualitycode.com> Message-ID: <45392647.1090803@mindspring.com> Kevin Smith wrote: > Roy Sutton wrote: > >> Kevin Smith wrote: >> >>> I'm more frustrated that it is impossible (?) to find out how many >>> people downloaded wxruby2 last week, whether from the Files section or >>> via gem. The "all time" number is available, but not week-by-week. >>> >>> >>> >> http://rubyforge.org/project/stats/index.php?group_id=35&area=downloads&SPAN=1&start=1159660800&end=1162339200&submit=Refresh >> >> That's Daily. Change the date ranges and period to Weekly if you want >> that. Not enough weeks in October to really help that. >> > > Does that include installs directly from gem, too? I believe so. Not sure. From roys at mindspring.com Fri Oct 20 16:01:48 2006 From: roys at mindspring.com (Roy Sutton) Date: Fri, 20 Oct 2006 16:01:48 -0400 Subject: [Wxruby-development] Nightly Linux build? In-Reply-To: <4538CA0C.8030706@qualitycode.com> References: <45382EFD.5070400@qualitycode.com> <45386CAF.1070608@mindspring.com> <4538CA0C.8030706@qualitycode.com> Message-ID: <45392B2C.1000203@mindspring.com> Kevin Smith wrote: > Can/does it also stick today's date in the version strings? I don't want > someone to have it installed and then think they are using a production > release if they ask for the version. > Maybe we need to build the version number into the binary so we can get that out? Wx::VERSION? Roy From roys at mindspring.com Fri Oct 20 16:10:48 2006 From: roys at mindspring.com (Roy Sutton) Date: Fri, 20 Oct 2006 16:10:48 -0400 Subject: [Wxruby-development] Good news on WxWidgets 2.8.0 In-Reply-To: <4538DCD8.8070807@pressure.to> References: <4538DCD8.8070807@pressure.to> Message-ID: <45392D48.6000701@mindspring.com> Alex Fenton wrote: > Hi > > Just tried out the most recent dev release (2.7.1) of WxWidgets. > Excellent news! Maybe we can figure a way to target either? Unfortunately Windows doesn't have a wx-config so we'd have to figure out the version number some other way. Perhaps a sample compile or SWIG xml parse of a wx header file? Roy > The first bit of good news is that 2.7.1 has lots of attractive new > widgets, such as RichTextCtrl, pickers, and the AUI. This is an add-on > that's now been merged into the core, and provides sophisticated things > like dockable toolbars, perspective layouts, semi-transparent dragging > etc. They seem to have brushed up the Mac version of AUI, and the sample > had me drooling. > > The second is that it looks like it will be straightforward for wxRuby > to target 2.8 (famous last words...). The changes are simple API > changes, mainly to base classes like Window, Dialog and > ControlWithItems. Just by fixing two lines in Window, I got about 80% of > our current classes compiled. The remaining errors look easy enough that > I could fix them, which is a good sign ;) > > 2.8.0 is meant to be out in a few weeks - I'm not planning to do > anything real until then. My sense is that we will be able to support > both 2.6 and 2.8 with some judicious ifdefs, without it getting too > messy. I'm fairly keen to continue 2.6.3 support, since it'll be a while > before 2.8 builds start showing up in binary, eg in Linux distros. > > alex > > > > _______________________________________________ > Wxruby-development mailing list > Wxruby-development at rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-development > > > > From nobody at rubyforge.org Sat Oct 21 07:16:24 2006 From: nobody at rubyforge.org (nobody at rubyforge.org) Date: Sat, 21 Oct 2006 07:16:24 -0400 (EDT) Subject: [Wxruby-development] [696] trunk/wxruby2/swig/classes/Pen.i: Un-ignored Get/SetStipple b/c these are now ifdef'd in the header for GTK Message-ID: <20061021111625.25DCC5241C10@rubyforge.org> An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wxruby-development/attachments/20061021/378073d4/attachment.html From alex at pressure.to Sat Oct 21 07:25:08 2006 From: alex at pressure.to (Alex Fenton) Date: Sat, 21 Oct 2006 12:25:08 +0100 Subject: [Wxruby-development] App.i patch Message-ID: <453A0394.5050908@pressure.to> This removes unwanted debugging output. also removes a deprecated method that gives a compile warning now and an error with wxWidgets 2.7.1 alex -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: App_i.patch Url: http://rubyforge.org/pipermail/wxruby-development/attachments/20061021/bbb9428c/attachment.ksh From alex at pressure.to Sat Oct 21 07:57:12 2006 From: alex at pressure.to (Alex Fenton) Date: Sat, 21 Oct 2006 12:57:12 +0100 Subject: [Wxruby-development] include Wx in samples? In-Reply-To: <45382D6E.2080405@qualitycode.com> References: <45342896.20005@mindspring.com> <4534CA76.5050609@pressure.to> <45382D6E.2080405@qualitycode.com> Message-ID: <453A0B18.3050709@pressure.to> Kevin Smith wrote: > Yes. I prefer not to include Wx because of various possible namespace > collisions. On reflection, it's probably also a matter of the size of application being written. In a sample, we're usually calling the core classes directly, so 'include Wx' is a useful repetition-saver. In a big 'real' app (like Weft) it's more usual to use subclasses. This means it's more important to see where constants are coming from, and reduces the repetition b/c the references to constants (eg style constants) are encapsulated within the subclass methods (eg constructors). So 'include Wx' makes less sense. > However, we should probably have at least one sample (maybe > minimal.rb) written two ways--one with include Wx and the other without. > Agreed. > Also, we could point to the one with the include if we are trying to > stress how easy and friendly wxruby app code can look. > Yep, sounds good. alex From nobody at rubyforge.org Sat Oct 21 10:05:24 2006 From: nobody at rubyforge.org (nobody at rubyforge.org) Date: Sat, 21 Oct 2006 10:05:24 -0400 (EDT) Subject: [Wxruby-development] [697] trunk/wxruby2/samples/bigdemo: Fixed loading of other files so the sample can be run from another directory Message-ID: <20061021140524.4FBFF5241B0E@rubyforge.org> An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wxruby-development/attachments/20061021/53088c8f/attachment.html From nobody at rubyforge.org Sat Oct 21 10:23:40 2006 From: nobody at rubyforge.org (nobody at rubyforge.org) Date: Sat, 21 Oct 2006 10:23:40 -0400 (EDT) Subject: [Wxruby-development] [698] trunk/wxruby2/samples/bigdemo/MDIDemo.rbw: Removed broken background stuff to stop crash on OS X (tho still crashes Message-ID: <20061021142340.D175C5241C79@rubyforge.org> An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wxruby-development/attachments/20061021/d09580ae/attachment.html From nobody at rubyforge.org Sat Oct 21 10:45:11 2006 From: nobody at rubyforge.org (nobody at rubyforge.org) Date: Sat, 21 Oct 2006 10:45:11 -0400 (EDT) Subject: [Wxruby-development] [699] trunk/wxruby2/doc/textile/window.txtl: Added paint method; corrected ret values for get_text_extent; removed Message-ID: <20061021144511.CBEA85241C94@rubyforge.org> An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wxruby-development/attachments/20061021/76701e3f/attachment-0001.html From roys at mindspring.com Sat Oct 21 10:49:26 2006 From: roys at mindspring.com (Roy Sutton) Date: Sat, 21 Oct 2006 10:49:26 -0400 Subject: [Wxruby-development] DataObject Message-ID: <453A3376.9000007@mindspring.com> I took a look at wxDataObject. My first attempts at wrapping it yielded link errors. I'm not really sure why. If anyone tries a naive wrapping you can probably see what I'm talking about. I got some pointers from the wxPython implementation on how to deal with some of the functions that return void pointers. I may wrap up an RbDataObjectSimple that takes and returns strings. Roy From nobody at rubyforge.org Sat Oct 21 10:54:58 2006 From: nobody at rubyforge.org (nobody at rubyforge.org) Date: Sat, 21 Oct 2006 10:54:58 -0400 (EDT) Subject: [Wxruby-development] [700] trunk/wxruby2/doc/textile/window.txtl: Added paint to the method index; corrected info about the type of DC Message-ID: <20061021145459.127FB5241C9B@rubyforge.org> An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wxruby-development/attachments/20061021/8db0fcef/attachment.html From nobody at rubyforge.org Sat Oct 21 11:23:14 2006 From: nobody at rubyforge.org (nobody at rubyforge.org) Date: Sat, 21 Oct 2006 11:23:14 -0400 (EDT) Subject: [Wxruby-development] [701] trunk/wxruby2/lib/wx/classes/: Directory to hold extension classes in Ruby Message-ID: <20061021152314.DA95D5241CA8@rubyforge.org> An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wxruby-development/attachments/20061021/b28fd228/attachment.html From alex at pressure.to Sat Oct 21 11:31:42 2006 From: alex at pressure.to (Alex Fenton) Date: Sat, 21 Oct 2006 16:31:42 +0100 Subject: [Wxruby-development] Window#paint patch Message-ID: <453A3D5E.7050508@pressure.to> Attached is a patch and some extra files to fix our ObjectPreviouslyDeleted crasher with the paint method. As discussed, it just re-implements the method in Ruby. I created a directory lib/wx/classes as a place to hold Ruby extensions to the API. The attached app.rb and window.rb files should be added to it. When this patch is applied, files in that directory are automatically required on startup. Hopefully this provides a framework for fixes and API improvements in Ruby. As an example, I'm thinking of writing something like ConfigBase to go in here, as I think persistent app settings it's useful to have in a GUI library, but the WxWidgets library requires some typemaps and is clunky too. The patch also fixes dialog.rb to use paint again, and removes an unnecessary global in that sample. alex -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: window_paint.patch Url: http://rubyforge.org/pipermail/wxruby-development/attachments/20061021/e662636f/attachment.pl -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: window.rb Url: http://rubyforge.org/pipermail/wxruby-development/attachments/20061021/e662636f/attachment-0001.pl -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: app.rb Url: http://rubyforge.org/pipermail/wxruby-development/attachments/20061021/e662636f/attachment-0002.pl From sean.m.long at gmail.com Sat Oct 21 13:18:34 2006 From: sean.m.long at gmail.com (Sean Long) Date: Sat, 21 Oct 2006 10:18:34 -0700 Subject: [Wxruby-development] Make task for rake Message-ID: I have a dual processor machine and got mad that both processors were not working away at compiling wxRuby. At first I tried using Ruby threads but they are 'fake' software threads that run in one process on one cpu. So until Ruby gets 'real' threads I added a task to rake that generates a makfile which is run with the command: 'make -j 2' which causes both CPU's to crunch away at compiling. On my iMac Core Duo 2.0ghz I got the following results: - To do a clean build including swigging with just 'rake' took 9min 45sec - To do the same with the new 'rake make' command took 6min 12sec As we add more and more wxWidgets classes the compile time is slowing down this should help us counter act it. Now if only I had one of those new MacPro Quads :) It should work fine on Linux and BSD but will need tweaks for cygwin and major changes for visual C++ on Windows. The changes do not alter any previous swig work but I thought I would show everyone the patch before I commit it, since it is different. Sean -------------- next part -------------- A non-text attachment was scrubbed... Name: rake_make.patch Type: application/octet-stream Size: 1529 bytes Desc: not available Url : http://rubyforge.org/pipermail/wxruby-development/attachments/20061021/e0ed85b0/attachment.obj From sean.m.long at gmail.com Sat Oct 21 13:26:33 2006 From: sean.m.long at gmail.com (Sean Long) Date: Sat, 21 Oct 2006 10:26:33 -0700 Subject: [Wxruby-development] Window#paint patch In-Reply-To: <453A3D5E.7050508@pressure.to> References: <453A3D5E.7050508@pressure.to> Message-ID: > I created a directory lib/wx/classes as a place to hold Ruby extensions > to the API. The attached app.rb and window.rb files should be added to > it. When this patch is applied, files in that directory are > automatically required on startup. Sounds like a good plan to me. > As an example, I'm thinking of writing something like ConfigBase > to go in here, as I think persistent app settings it's useful to have in > a GUI library, but the WxWidgets library requires some typemaps and is > clunky too. I think this is a very good idea as every app needs to store some kind of app settings, last window position, recent files, preferences etc. Sean From nobody at rubyforge.org Sat Oct 21 15:17:57 2006 From: nobody at rubyforge.org (nobody at rubyforge.org) Date: Sat, 21 Oct 2006 15:17:57 -0400 (EDT) Subject: [Wxruby-development] [702] trunk/wxruby2: Additions to allow faster compiling via a Makefile on dual-processor Message-ID: <20061021191757.4BF765241AB2@rubyforge.org> An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wxruby-development/attachments/20061021/c8a2d4f8/attachment-0001.html From alex at pressure.to Sat Oct 21 15:21:05 2006 From: alex at pressure.to (Alex Fenton) Date: Sat, 21 Oct 2006 20:21:05 +0100 Subject: [Wxruby-development] Make task for rake In-Reply-To: References: Message-ID: <453A7321.2080702@pressure.to> Sean Long wrote: > On my iMac Core Duo 2.0ghz I got the following results: > > - To do a clean build including swigging with just 'rake' took 9min 45sec > - To do the same with the new 'rake make' command took 6min 12sec Nice one. I use a G4 Powerbook for wxRuby development. It's a nice machine, but not a powerful processor: a complete build takes about 30-40 minutes now! Scintilla in particular takes ages. All good, cos it means more features, but still... Anyway, I checked in your changes because they looked good and didn't cause problems for me. Thanks for the patches. Alex From nobody at rubyforge.org Sat Oct 21 15:55:03 2006 From: nobody at rubyforge.org (nobody at rubyforge.org) Date: Sat, 21 Oct 2006 15:55:03 -0400 (EDT) Subject: [Wxruby-development] [703] trunk/wxruby2/Changelog: Get/SetStipple for Wx::Pen; faster building on dual core; MDI sample bugs on OS X Message-ID: <20061021195503.81DA45241BB9@rubyforge.org> An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wxruby-development/attachments/20061021/4df463a8/attachment.html From alex at pressure.to Sat Oct 21 16:09:35 2006 From: alex at pressure.to (Alex Fenton) Date: Sat, 21 Oct 2006 21:09:35 +0100 Subject: [Wxruby-development] 0.0.37 release? Message-ID: <453A7E7F.70705@pressure.to> I would like to tag and release 0.0.37 soon. I'm thinking of the next few days. We have good new stuff (Printing, Scintilla on OS X, other new classes) and have fixed some bugs. Also, would be good to put the early build probs with the last release behind us. Here's the patches I think are outstanding: - Wx::App cleanup - rake HTML docs publishing - Scintilla OS X - IconBundle, ListView (?) - TaskBarIconEvent event thunker patches (?) I'll check in the ones that I think are uncontroversial, but I'd like some feedback on the App patch, IconBundle, and TaskBarEvent. Anything else we want in for the release? a From sean.m.long at gmail.com Sat Oct 21 16:11:07 2006 From: sean.m.long at gmail.com (Sean Long) Date: Sat, 21 Oct 2006 13:11:07 -0700 Subject: [Wxruby-development] Make task for rake In-Reply-To: <453A7321.2080702@pressure.to> References: <453A7321.2080702@pressure.to> Message-ID: > I use a G4 Powerbook for wxRuby development. It's a nice > machine, but not a powerful processor: a complete build takes about > 30-40 minutes now! ouch! I thought the 20-30 min my PowerMac G4 1.25ghz at work was slow. The use of make will mostly help when we change something deep in wxRuby and have to do a complete rebuild and of course building releases. > Anyway, I checked in your changes because they looked good and didn't > cause problems for me. Thanks for the patches. I'm glad they worked for you also. Sean From roys at mindspring.com Sat Oct 21 16:23:41 2006 From: roys at mindspring.com (Roy Sutton) Date: Sat, 21 Oct 2006 16:23:41 -0400 Subject: [Wxruby-development] Make task for rake In-Reply-To: <453A7321.2080702@pressure.to> References: <453A7321.2080702@pressure.to> Message-ID: <453A81CD.7030905@mindspring.com> Alex Fenton wrote: > Sean Long wrote: > >> On my iMac Core Duo 2.0ghz I got the following results: >> >> - To do a clean build including swigging with just 'rake' took 9min 45sec >> - To do the same with the new 'rake make' command took 6min 12sec >> > Nice one. I use a G4 Powerbook for wxRuby development. It's a nice > machine, but not a powerful processor: a complete build takes about > 30-40 minutes now! Scintilla in particular takes ages. All good, cos it > means more features, but still... > > Anyway, I checked in your changes because they looked good and didn't > cause problems for me. Thanks for the patches. > > Doesn't work on Windows, sadly. Of course, you don't have to run it. I got an error like this: > make: *** No rule to make target `src/ActivateEvent.cppbj', needed by > `obj/ActivateEvent.obj'. Stop. Roy From sean.m.long at gmail.com Sat Oct 21 16:55:20 2006 From: sean.m.long at gmail.com (Sean Long) Date: Sat, 21 Oct 2006 13:55:20 -0700 Subject: [Wxruby-development] 0.0.37 release? In-Reply-To: <453A7E7F.70705@pressure.to> References: <453A7E7F.70705@pressure.to> Message-ID: On 10/21/06, Alex Fenton wrote: > I would like to tag and release 0.0.37 soon. I think we have enough new stuff for a release, so I am for it. > Here's the patches I think are outstanding: > - Wx::App cleanup Will try soon. > - rake HTML docs publishing Just tried it and got the following type of error for all files to upload: scp: /var/www/gforge-projects/wxruby/doc//.html: Permission denied Maybe I don't have access to this directory? > - Scintilla OS X Tried it a few days back and got Scintilla to compile but could not get it to compile into wxRuby. I did not spend too much time on it, will have to go back and test again. > - IconBundle, ListView (?) > - TaskBarIconEvent event thunker patches (?) I must have missed these, I will look for the patches to try. > Anything else we want in for the release? I think we should stick with what you mentioned for this release. Things seem to be working pretty good right now. Sean From sean.m.long at gmail.com Sat Oct 21 17:34:19 2006 From: sean.m.long at gmail.com (Sean Long) Date: Sat, 21 Oct 2006 14:34:19 -0700 Subject: [Wxruby-development] Window#paint patch In-Reply-To: <453A3D5E.7050508@pressure.to> References: <453A3D5E.7050508@pressure.to> Message-ID: I applied the patch and added the app.rb and window.rb files. On the dialogs sample I had to change on_paint to the following to get it to work. def on_paint(event) dc = PaintDC.new(self) dc.set_text_foreground( get_app.canvas_text_colour ) dc.set_font( get_app.canvas_font ) dc.draw_text("Windows common dialogs test application", 10, 10) end Besides that change things seem to be working fine. Sean From roys at mindspring.com Sat Oct 21 17:37:35 2006 From: roys at mindspring.com (Roy Sutton) Date: Sat, 21 Oct 2006 17:37:35 -0400 Subject: [Wxruby-development] common.i patch Message-ID: <453A931F.6060806@mindspring.com> The latest cvs version of SWIG breaks a few things. I have patched common.i to fix most of it. There will be some other things later that should be compatible with all versions. Can someone test to see if this compiles with the old version? Roy -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: common.i.patch Url: http://rubyforge.org/pipermail/wxruby-development/attachments/20061021/dd766eda/attachment.pl From roys at mindspring.com Sat Oct 21 17:42:17 2006 From: roys at mindspring.com (Roy Sutton) Date: Sat, 21 Oct 2006 17:42:17 -0400 Subject: [Wxruby-development] DC.i patch Message-ID: <453A9439.6010207@mindspring.com> This patch unignores GetMultiLineTextExtent. Not only did we come up with a typemap that wraps it correctly the head version of SWIG chokes trying to make a director for it if it's %ingored. Roy -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: dc.i.patch Url: http://rubyforge.org/pipermail/wxruby-development/attachments/20061021/1ee3dd5a/attachment.pl From sean.m.long at gmail.com Sat Oct 21 18:40:15 2006 From: sean.m.long at gmail.com (Sean Long) Date: Sat, 21 Oct 2006 15:40:15 -0700 Subject: [Wxruby-development] common.i patch In-Reply-To: <453A931F.6060806@mindspring.com> References: <453A931F.6060806@mindspring.com> Message-ID: I applied the changes and did a clean build, tried a few samples and they all worked as before. Sean On 10/21/06, Roy Sutton wrote: > The latest cvs version of SWIG breaks a few things. I have patched > common.i to fix most of it. There will be some other things later that > should be compatible with all versions. Can someone test to see if this > compiles with the old version? > > Roy > > > Index: wxruby2/swig/common.i > =================================================================== > --- wxruby2/swig/common.i (revision 702) > +++ wxruby2/swig/common.i (working copy) > @@ -4,7 +4,7 @@ > %feature("director"); > %feature("compactdefaultargs"); > > -%{ > +%runtime %{ > // # SWIG 1.3.29 added this new feature which we can't use (yet) > #define SWIG_DIRECTOR_NOUEH TRUE > > @@ -27,11 +27,11 @@ > #include > #include > > -void GcMarkDeleted(void *); > -bool GcIsDeleted(void *); > -void GcMapPtrToValue(void *ptr, VALUE val); > -VALUE GcGetValueFromPtr(void *ptr); > -void GcFreefunc(void *); > +extern void GcMarkDeleted(void *); > +extern bool GcIsDeleted(void *); > +extern void GcMapPtrToValue(void *ptr, VALUE val); > +extern VALUE GcGetValueFromPtr(void *ptr); > +extern void GcFreefunc(void *); > > extern VALUE mWxruby2; > %} > > > _______________________________________________ > Wxruby-development mailing list > Wxruby-development at rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-development > > > From nobody at rubyforge.org Sat Oct 21 20:45:23 2006 From: nobody at rubyforge.org (nobody at rubyforge.org) Date: Sat, 21 Oct 2006 20:45:23 -0400 (EDT) Subject: [Wxruby-development] [704] trunk/wxruby2/lib: Auto-load classes from lib/wx/classes; implement Window#paint in Ruby Message-ID: <20061022004523.52BB75241D60@rubyforge.org> An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wxruby-development/attachments/20061021/f61704c7/attachment-0001.html From nobody at rubyforge.org Sat Oct 21 20:46:28 2006 From: nobody at rubyforge.org (nobody at rubyforge.org) Date: Sat, 21 Oct 2006 20:46:28 -0400 (EDT) Subject: [Wxruby-development] [705] trunk/wxruby2/rake/rakedocs.rb: Add rake task to publish docs to wxruby website (Alex Fenton) Message-ID: <20061022004628.24D6C5241D5B@rubyforge.org> An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wxruby-development/attachments/20061021/daba82d1/attachment.html From nobody at rubyforge.org Sat Oct 21 20:47:16 2006 From: nobody at rubyforge.org (nobody at rubyforge.org) Date: Sat, 21 Oct 2006 20:47:16 -0400 (EDT) Subject: [Wxruby-development] [706] trunk/wxruby2/rake/rakemacosx.rb: WxScintilla optional class added (Alex Fenton) Message-ID: <20061022004716.3FD8A5241D5E@rubyforge.org> An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wxruby-development/attachments/20061021/31915726/attachment.html From nobody at rubyforge.org Sat Oct 21 20:48:37 2006 From: nobody at rubyforge.org (nobody at rubyforge.org) Date: Sat, 21 Oct 2006 20:48:37 -0400 (EDT) Subject: [Wxruby-development] [707] trunk/wxruby2/swig/classes/Window.i: Window-paint method now implemented in Ruby (Alex Fenton) Message-ID: <20061022004837.991AD5241D59@rubyforge.org> An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wxruby-development/attachments/20061021/5e0bc9df/attachment.html From nobody at rubyforge.org Sat Oct 21 21:02:55 2006 From: nobody at rubyforge.org (nobody at rubyforge.org) Date: Sat, 21 Oct 2006 21:02:55 -0400 (EDT) Subject: [Wxruby-development] [708] trunk/wxruby2/swig/classes/DC.i: Un-ignore get_multi_line_text_extent (Roy Sutton) Message-ID: <20061022010255.323A55241D63@rubyforge.org> An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wxruby-development/attachments/20061021/159d29ad/attachment.html From alex at pressure.to Sat Oct 21 21:08:44 2006 From: alex at pressure.to (Alex Fenton) Date: Sun, 22 Oct 2006 02:08:44 +0100 Subject: [Wxruby-development] Window#paint patch In-Reply-To: References: <453A3D5E.7050508@pressure.to> Message-ID: <453AC49C.10407@pressure.to> Sean Long wrote: > I applied the patch and added the app.rb and window.rb files. > > On the dialogs sample I had to change on_paint to the following to get > it to work. > what's the error you get with paint { ... } ? a From wxruby at qualitycode.com Sat Oct 21 22:00:56 2006 From: wxruby at qualitycode.com (Kevin Smith) Date: Sat, 21 Oct 2006 22:00:56 -0400 Subject: [Wxruby-development] Window#paint patch In-Reply-To: <453A3D5E.7050508@pressure.to> References: <453A3D5E.7050508@pressure.to> Message-ID: <453AD0D8.70106@qualitycode.com> Alex Fenton wrote: > Attached is a patch and some extra files to fix our > ObjectPreviouslyDeleted crasher with the paint method. As discussed, it > just re-implements the method in Ruby. Cool. > > I created a directory lib/wx/classes as a place to hold Ruby extensions > to the API. The attached app.rb and window.rb files should be added to > it. When this patch is applied, files in that directory are > automatically required on startup. I like it. > Hopefully this provides a framework for fixes and API improvements in > Ruby. As an example, I'm thinking of writing something like ConfigBase > to go in here, as I think persistent app settings it's useful to have in > a GUI library, but the WxWidgets library requires some typemaps and is > clunky too. Not sure about that. I haven't looked, but one would hope that there is a non-GUI-specific persistent-app-setting library we could point people to, instead of inventing our own. If we do invent our own, I would encourage it to be distinct from wxruby, as it could be equally useful to curses or ruby-gtk apps. Kevin From wxruby at qualitycode.com Sat Oct 21 22:04:41 2006 From: wxruby at qualitycode.com (Kevin Smith) Date: Sat, 21 Oct 2006 22:04:41 -0400 Subject: [Wxruby-development] Make task for rake In-Reply-To: References: Message-ID: <453AD1B9.4050107@qualitycode.com> Sean Long wrote: > So until Ruby gets 'real' threads I added a task to rake > that generates a makfile which is run with the command: 'make -j 2' > which causes both CPU's to crunch away at compiling. Cool. I don't like the target name of "make" though. Can we call it something like "rake multithreaded"? Or make it an option like "rake USEMAKE=true" if it could be used for different targets, such as "rake gem USEMAKE=true"? > It should work fine on Linux and BSD but will need tweaks for cygwin > and major changes for visual C++ on Windows. In a perfect world, it would either fallback on unsupported platforms (with an informational text output) or fail with a clean error. Kevin From wxruby at qualitycode.com Sat Oct 21 22:06:25 2006 From: wxruby at qualitycode.com (Kevin Smith) Date: Sat, 21 Oct 2006 22:06:25 -0400 Subject: [Wxruby-development] 0.0.37 release? In-Reply-To: References: <453A7E7F.70705@pressure.to> Message-ID: <453AD221.4030606@qualitycode.com> Sean Long wrote: > On 10/21/06, Alex Fenton wrote: >> I would like to tag and release 0.0.37 soon. Strong +1. I'll trust your judgment of exactly when to cut it off, but I would favor sooner rather than later. Kevin From wxruby at qualitycode.com Sat Oct 21 22:08:15 2006 From: wxruby at qualitycode.com (Kevin Smith) Date: Sat, 21 Oct 2006 22:08:15 -0400 Subject: [Wxruby-development] [Fwd: Wxruby-development post from noreply@rubyforge.org requires approval] Message-ID: <453AD28F.5010703@qualitycode.com> Alex: Any idea why the list is still bouncing these? "noreply at rubyforge.org" is in the list of addresses that are supposed to be allowed to post even though not subscribed. What is that about "Message has implicit destination"??? Kevin -------- Original Message -------- Subject: Wxruby-development post from noreply at rubyforge.org requires approval Date: Sat, 21 Oct 2006 14:13:27 -0400 From: wxruby-development-owner at rubyforge.org To: wxruby-development-owner at rubyforge.org As list administrator, your authorization is requested for the following mailing list posting: List: Wxruby-development at rubyforge.org From: noreply at rubyforge.org Subject: [ wxruby-Bugs-6262 ] MDIParentFrame#add_child not working on OS X Reason: Message has implicit destination At your convenience, visit: http://rubyforge.org/mailman/admindb/wxruby-development to approve or deny the request. -------------- next part -------------- An embedded message was scrubbed... From: Subject: [ wxruby-Bugs-6262 ] MDIParentFrame#add_child not working on OS X Date: Sat, 21 Oct 2006 14:13:25 -0400 (EDT) Size: 1329 Url: http://rubyforge.org/pipermail/wxruby-development/attachments/20061021/1930e7a7/attachment-0002.eml -------------- next part -------------- An embedded message was scrubbed... From: wxruby-development-request at rubyforge.org Subject: confirm eddc16c9d8683f5a6a5bcbd7063173a3b9af96a7 Date: no date Size: 653 Url: http://rubyforge.org/pipermail/wxruby-development/attachments/20061021/1930e7a7/attachment-0003.eml From noreply at rubyforge.org Sat Oct 21 14:13:25 2006 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Sat, 21 Oct 2006 14:13:25 -0400 (EDT) Subject: [Wxruby-development] [ wxruby-Bugs-6262 ] MDIParentFrame#add_child not working on OS X Message-ID: <20061021181326.73A445241D01@rubyforge.org> Bugs item #6262, was opened at 2006-10-21 18:13 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=218&aid=6262&group_id=35 Category: Incorrect behavior Group: None Status: Open Resolution: None Priority: 3 Submitted By: Alex Fenton (brokentoy) Assigned to: Kevin Smith (qualitycode) Summary: MDIParentFrame#add_child not working on OS X Initial Comment: MDIParentFrame#add_child either crashes (in bigdemo) or does nothing at all (mdi demo), on OS X. There isn't true MDI on OS X, but wxRuby should follow WxWidgets in providing an emulation of it, using ordinary Frames. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=218&aid=6262&group_id=35 From wxruby at qualitycode.com Sat Oct 21 23:36:30 2006 From: wxruby at qualitycode.com (Kevin Smith) Date: Sat, 21 Oct 2006 23:36:30 -0400 Subject: [Wxruby-development] [Fwd: Wxruby-development post from noreply@rubyforge.org requires approval] In-Reply-To: <453AD28F.5010703@qualitycode.com> References: <453AD28F.5010703@qualitycode.com> Message-ID: <453AE73E.9030702@qualitycode.com> I think I figured out the bouncing. The messages seemed to have the list as a BCC, which is typical of spam. I changed the list setting, so hopefully bug reports will start showing up on wxruby-dev automatically. Kevin Kevin Smith wrote: > Alex: Any idea why the list is still bouncing these? > "noreply at rubyforge.org" is in the list of addresses that are supposed to > be allowed to post even though not subscribed. What is that about > "Message has implicit destination"??? > > Kevin > > > -------- Original Message -------- > Subject: Wxruby-development post from noreply at rubyforge.org requires > approval > Date: Sat, 21 Oct 2006 14:13:27 -0400 > From: wxruby-development-owner at rubyforge.org > To: wxruby-development-owner at rubyforge.org > > As list administrator, your authorization is requested for the > following mailing list posting: > > List: Wxruby-development at rubyforge.org > From: noreply at rubyforge.org > Subject: [ wxruby-Bugs-6262 ] MDIParentFrame#add_child not working > on OS X > Reason: Message has implicit destination > > At your convenience, visit: > > http://rubyforge.org/mailman/admindb/wxruby-development > > to approve or deny the request. > > > ------------------------------------------------------------------------ > > Subject: > [ wxruby-Bugs-6262 ] MDIParentFrame#add_child not working on OS X > From: > > Date: > Sat, 21 Oct 2006 14:13:25 -0400 (EDT) > To: > noreply at rubyforge.org > > To: > noreply at rubyforge.org > > > Bugs item #6262, was opened at 2006-10-21 18:13 > You can respond by visiting: > http://rubyforge.org/tracker/?func=detail&atid=218&aid=6262&group_id=35 > > Category: Incorrect behavior > Group: None > Status: Open > Resolution: None > Priority: 3 > Submitted By: Alex Fenton (brokentoy) > Assigned to: Kevin Smith (qualitycode) > Summary: MDIParentFrame#add_child not working on OS X > > Initial Comment: > MDIParentFrame#add_child either crashes (in bigdemo) or does nothing at all (mdi demo), on OS X. There isn't true MDI on OS X, but wxRuby should follow WxWidgets in providing an emulation of it, using ordinary Frames. > > ---------------------------------------------------------------------- > > You can respond by visiting: > http://rubyforge.org/tracker/?func=detail&atid=218&aid=6262&group_id=35 > > > > ------------------------------------------------------------------------ > > Subject: > confirm eddc16c9d8683f5a6a5bcbd7063173a3b9af96a7 > From: > wxruby-development-request at rubyforge.org > > > If you reply to this message, keeping the Subject: header intact, > Mailman will discard the held message. Do this if the message is > spam. If you reply to this message and include an Approved: header > with the list password in it, the message will be approved for posting > to the list. The Approved: header can also appear in the first line > of the body of the reply. > > > ------------------------------------------------------------------------ > > _______________________________________________ > Wxruby-development mailing list > Wxruby-development at rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-development From nobody at rubyforge.org Sun Oct 22 20:08:02 2006 From: nobody at rubyforge.org (nobody at rubyforge.org) Date: Sun, 22 Oct 2006 20:08:02 -0400 (EDT) Subject: [Wxruby-development] [709] trunk/wxruby2/samples/dialogs/dialogs.rb: Use paint method again, remove unnecessary global (Alex Fenton) Message-ID: <20061023000802.4E1E15241E50@rubyforge.org> An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wxruby-development/attachments/20061022/641da50c/attachment.html From alex at pressure.to Sun Oct 22 20:13:38 2006 From: alex at pressure.to (Alex Fenton) Date: Mon, 23 Oct 2006 01:13:38 +0100 Subject: [Wxruby-development] Make task for rake In-Reply-To: <453AD1B9.4050107@qualitycode.com> References: <453AD1B9.4050107@qualitycode.com> Message-ID: <453C0932.4010506@pressure.to> Kevin Smith wrote: > I don't like the target name of "make" though. Can we call it something > like "rake multithreaded"? +1 though it's not urgent. alex From alex at pressure.to Sun Oct 22 20:19:39 2006 From: alex at pressure.to (Alex Fenton) Date: Mon, 23 Oct 2006 01:19:39 +0100 Subject: [Wxruby-development] 0.0.37 release? In-Reply-To: References: <453A7E7F.70705@pressure.to> Message-ID: <453C0A9B.7050003@pressure.to> Sean Long wrote: >> - rake HTML docs publishing >> > > Just tried it and got the following type of error for all files to upload: > scp: /var/www/gforge-projects/wxruby/doc//.html: > Permission denied > > Maybe I don't have access to this directory? > I modified the directory to be group write. Let me know if it's still not working. >> - Scintilla OS X >> > > Tried it a few days back and got Scintilla to compile but could not > get it to compile into wxRuby. I did not spend too much time on it, > will have to go back and test again. > Should be in SVN in now. Are you still getting compile errors? It needs a full rebuild. alex From sean.m.long at gmail.com Sun Oct 22 23:19:35 2006 From: sean.m.long at gmail.com (Sean Long) Date: Sun, 22 Oct 2006 20:19:35 -0700 Subject: [Wxruby-development] Make task for rake In-Reply-To: <453C0932.4010506@pressure.to> References: <453AD1B9.4050107@qualitycode.com> <453C0932.4010506@pressure.to> Message-ID: I'm ok with a name change, I just care about the functionality. How about rake multi or something else with a short name? A shorter name is easier to remember and less likely to be spelled wrong (I have a hard enough time with spelling). Sean On 10/22/06, Alex Fenton wrote: > Kevin Smith wrote: > > I don't like the target name of "make" though. Can we call it something > > like "rake multithreaded"? > +1 though it's not urgent. > > alex > _______________________________________________ > Wxruby-development mailing list > Wxruby-development at rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-development > From sean.m.long at gmail.com Sun Oct 22 23:22:10 2006 From: sean.m.long at gmail.com (Sean Long) Date: Sun, 22 Oct 2006 20:22:10 -0700 Subject: [Wxruby-development] 0.0.37 release? In-Reply-To: <453C0A9B.7050003@pressure.to> References: <453A7E7F.70705@pressure.to> <453C0A9B.7050003@pressure.to> Message-ID: > I modified the directory to be group write. Let me know if it's still > not working. When I have a few minutes I will test it again. > Should be in SVN in now. Are you still getting compile errors? It needs > a full rebuild. I got Scintilla to integrate into wxRuby after you posted the changes, bigdemo crashes on startup after adding Scintilla, something with a Scintilla event. Sean From alex at pressure.to Mon Oct 23 03:46:08 2006 From: alex at pressure.to (Alex Fenton) Date: Mon, 23 Oct 2006 08:46:08 +0100 Subject: [Wxruby-development] common.i patch In-Reply-To: <453A931F.6060806@mindspring.com> References: <453A931F.6060806@mindspring.com> Message-ID: <453C7340.3030107@pressure.to> Roy Sutton wrote: > The latest cvs version of SWIG breaks a few things. I have patched > common.i to fix most of it. There will be some other things later > that should be compatible with all versions. Can someone test to see > if this compiles with the old version? Yep, fine for me too. Feel free to apply, thanks. alex From alex at pressure.to Mon Oct 23 03:50:35 2006 From: alex at pressure.to (Alex Fenton) Date: Mon, 23 Oct 2006 08:50:35 +0100 Subject: [Wxruby-development] 0.0.37 release? In-Reply-To: References: <453A7E7F.70705@pressure.to> <453C0A9B.7050003@pressure.to> Message-ID: <453C744B.7030306@pressure.to> Sean Long wrote: >> Should be in SVN in now. Are you still getting compile errors? It needs >> a full rebuild. >> > > I got Scintilla to integrate into wxRuby after you posted the changes, > bigdemo crashes on startup after adding Scintilla, something with a > Scintilla event. Hmm. I was seeing errors of this sort when I first compiled it in, but they fixed once I did a rake reswig with WXSCINTILLA pointed to the right place. It's needed so the right event hooks get added into EvtHandler and all the classes that inherit from it. cheers alex From alex at pressure.to Mon Oct 23 04:23:35 2006 From: alex at pressure.to (Alex Fenton) Date: Mon, 23 Oct 2006 09:23:35 +0100 Subject: [Wxruby-development] Make task for rake In-Reply-To: References: <453AD1B9.4050107@qualitycode.com> <453C0932.4010506@pressure.to> Message-ID: <453C7C07.6000709@pressure.to> Sean Long wrote: > I'm ok with a name change, I just care about the functionality. > How about rake multi Sounds good to me, thanks. alex From nobody at rubyforge.org Mon Oct 23 09:46:15 2006 From: nobody at rubyforge.org (nobody at rubyforge.org) Date: Mon, 23 Oct 2006 09:46:15 -0400 (EDT) Subject: [Wxruby-development] [710] trunk/wxruby2/swig/common.i: Added extern keyword to Gc functions and moved common header includes to %runtime Message-ID: <20061023134615.A5F025240DDB@rubyforge.org> An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wxruby-development/attachments/20061023/93c7afd1/attachment.html From alex at pressure.to Mon Oct 23 12:56:22 2006 From: alex at pressure.to (Alex Fenton) Date: Mon, 23 Oct 2006 17:56:22 +0100 Subject: [Wxruby-development] patch for rake install Message-ID: <453CF436.4050808@pressure.to> The attached patch fixes the task for non-gem installation. It adds installation of the version and class ruby files, and puts things in the right place (wx.rb was previously going into sitearchdir). It also adds an uninstall task. I plan to overhaul the rake system at some point soon as I think it could be declared more simply, and to avoid launching a new process for each of the cpp post-processors. Once this is in, and the App patch has been applied, I think we should tag and release. I'll check in App.i if I don't hear any objections. I'll resubmit IconBundle etc later with a proper sample, cos it does need testing on Windows where icons work differently to OS X. alex -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: rake_install.patch Url: http://rubyforge.org/pipermail/wxruby-development/attachments/20061023/66526e95/attachment.ksh From nobody at rubyforge.org Mon Oct 23 13:55:22 2006 From: nobody at rubyforge.org (nobody at rubyforge.org) Date: Mon, 23 Oct 2006 13:55:22 -0400 (EDT) Subject: [Wxruby-development] [711] trunk/wxruby2/Changelog: Ruby extension directory, paint fix, multi_line_text_extent, doc publishing Message-ID: <20061023175523.0216C5241335@rubyforge.org> An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wxruby-development/attachments/20061023/5bf0fafd/attachment.html From roys at mindspring.com Mon Oct 23 13:28:54 2006 From: roys at mindspring.com (Roy Sutton) Date: Mon, 23 Oct 2006 13:28:54 -0400 Subject: [Wxruby-development] patch for rake install In-Reply-To: <453CF436.4050808@pressure.to> References: <453CF436.4050808@pressure.to> Message-ID: <453CFBD6.3090703@mindspring.com> Alex Fenton wrote: > The attached patch fixes the task for non-gem installation. It adds > installation of the version and class ruby files, and puts things in > the right place (wx.rb was previously going into sitearchdir). It also > adds an uninstall task. > > I plan to overhaul the rake system at some point soon as I think it > could be declared more simply, and to avoid launching a new process > for each of the cpp post-processors. Should we take a look at mkrf[1]? I'm not entirely certain it's something we want but it was discussed at RubyConf. > > Once this is in, and the App patch has been applied, I think we should > tag and release. I'll check in App.i if I don't hear any objections. > > I'll resubmit IconBundle etc later with a proper sample, cos it does > need testing on Windows where icons work differently to OS X. > I'll test out the attached patch and look over IconBundle when you [re-]submit it. [1] http://rubyforge.org/projects/mkrf/ From nobody at rubyforge.org Mon Oct 23 16:55:33 2006 From: nobody at rubyforge.org (nobody at rubyforge.org) Date: Mon, 23 Oct 2006 16:55:33 -0400 (EDT) Subject: [Wxruby-development] [712] trunk/wxruby2/swig/classes/App.i: Removed unneeded debugging output & deprecated method (Alex Fenton) Message-ID: <20061023205533.421F152413A0@rubyforge.org> An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wxruby-development/attachments/20061023/8b168bef/attachment.html From alex at pressure.to Mon Oct 23 18:36:36 2006 From: alex at pressure.to (Alex Fenton) Date: Mon, 23 Oct 2006 23:36:36 +0100 Subject: [Wxruby-development] patch for rake install In-Reply-To: <453CFBD6.3090703@mindspring.com> References: <453CF436.4050808@pressure.to> <453CFBD6.3090703@mindspring.com> Message-ID: <453D43F4.1070305@pressure.to> Roy Sutton wrote: > Alex Fenton wrote: >> >> >> I plan to overhaul the rake system at some point soon as I think it >> could be declared more simply, and to avoid launching a new process >> for each of the cpp post-processors. >> > Should we take a look at mkrf[1]? I'm not entirely certain it's > something we want but it was discussed at RubyConf. > Funny, I was looking at it earlier browsing the RubyConf blogs. I'd be willing to give it a go once it's a bit more mature and documented. Actually, I think our build system is OK, and it's got a lot of learning and platform/compiler knowledge embedded in it. I'd really just like to tidy it up and make it a bit easier to follow. I think we could make better use of rake features (eg synthetic rules), use constants rather than globals where possible, so uninitialised or overwriting settings is warned aobut, and declare the tasks straightforwardly. I'd like to fix dependency checking so that changes to superclasses trigger a recompile of subclasses, add stripping of OS X binaries, and tidy the postprocessors. But none of those is very high priority. >> Once this is in, and the App patch has been applied, I think we should >> tag and release. I'll check in App.i if I don't hear any objections. >> > I'll test out the attached patch Thanks. After that's in, unless we hear there's major problems on a platform, let's go for a release. alex From nobody at rubyforge.org Mon Oct 23 22:40:32 2006 From: nobody at rubyforge.org (nobody at rubyforge.org) Date: Mon, 23 Oct 2006 22:40:32 -0400 (EDT) Subject: [Wxruby-development] [713] trunk/wxruby2: Patch for rake install, added rake uninstall Message-ID: <20061024024032.CBACE5241E9C@rubyforge.org> An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wxruby-development/attachments/20061023/03c1212a/attachment-0001.html From nobody at rubyforge.org Mon Oct 23 22:49:35 2006 From: nobody at rubyforge.org (nobody at rubyforge.org) Date: Mon, 23 Oct 2006 22:49:35 -0400 (EDT) Subject: [Wxruby-development] [714] trunk/wxruby2/doc/textile/app.txtl: Removed create_log_target Message-ID: <20061024024935.250085241EA6@rubyforge.org> An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wxruby-development/attachments/20061023/b504bce5/attachment.html From roys at mindspring.com Mon Oct 23 22:50:28 2006 From: roys at mindspring.com (Roy Sutton) Date: Mon, 23 Oct 2006 22:50:28 -0400 Subject: [Wxruby-development] rakefile Message-ID: <453D7F74.4050507@mindspring.com> I tested all the new rakefile stuff, including installing, uninstalling and publishing the docs. I have a question though: Why are the textile files uploaded to the server? Roy From nobody at rubyforge.org Tue Oct 24 03:52:27 2006 From: nobody at rubyforge.org (nobody at rubyforge.org) Date: Tue, 24 Oct 2006 03:52:27 -0400 (EDT) Subject: [Wxruby-development] [715] trunk/wxruby2/TODO: Remove some completed items Message-ID: <20061024075227.423915240FCA@rubyforge.org> An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wxruby-development/attachments/20061024/3d55ab46/attachment.html From nobody at rubyforge.org Tue Oct 24 03:52:45 2006 From: nobody at rubyforge.org (nobody at rubyforge.org) Date: Tue, 24 Oct 2006 03:52:45 -0400 (EDT) Subject: [Wxruby-development] [716] trunk/wxruby2/Changelog: Last changes in preparation for tagging 0.0.37 Message-ID: <20061024075245.7CE4E5240E31@rubyforge.org> An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wxruby-development/attachments/20061024/d520e3e5/attachment.html From nobody at rubyforge.org Tue Oct 24 03:56:29 2006 From: nobody at rubyforge.org (nobody at rubyforge.org) Date: Tue, 24 Oct 2006 03:56:29 -0400 (EDT) Subject: [Wxruby-development] [717] tags/wxruby2/0.0.37/: Tagged 0.0.37 Message-ID: <20061024075631.A1E4C5240E31@rubyforge.org> An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wxruby-development/attachments/20061024/877e4cf3/attachment.html From alex at pressure.to Tue Oct 24 04:08:02 2006 From: alex at pressure.to (Alex Fenton) Date: Tue, 24 Oct 2006 09:08:02 +0100 Subject: [Wxruby-development] tagged 0.0.37; release plans Message-ID: <453DC9E2.9020203@pressure.to> Hi I just tagged 0.0.37 in Subversion. I also added a note on the Wiki on how to do this, and how to checkout a clean version: http://wxruby.rubyforge.org/wiki/wiki.pl?Release_HowTo For the build, I'm just about to upload a tarball, and will add a powerpc gem once the compiler's chugged away. Please upload for your platform as you're ready. I suggest we announce to wxruby-users now, as a 'friendly' list to pick up any problems. Then once we have a full set of binaries, let's do a public (rubyforge/clr) announcement. Sound good? alex From wxruby at qualitycode.com Tue Oct 24 08:20:36 2006 From: wxruby at qualitycode.com (Kevin Smith) Date: Tue, 24 Oct 2006 08:20:36 -0400 Subject: [Wxruby-development] tagged 0.0.37; release plans In-Reply-To: <453DC9E2.9020203@pressure.to> References: <453DC9E2.9020203@pressure.to> Message-ID: <453E0514.9060705@qualitycode.com> Alex Fenton wrote: > Hi > > I just tagged 0.0.37 in Subversion. I also added a note on the Wiki on > how to do this, and how to checkout a clean version: > > http://wxruby.rubyforge.org/wiki/wiki.pl?Release_HowTo Ok. I can do an Ubuntu build today. > For the build, I'm just about to upload a tarball, and will add a > powerpc gem once the compiler's chugged away. Please upload for your > platform as you're ready. > > I suggest we announce to wxruby-users now, as a 'friendly' list to pick > up any problems. Then once we have a full set of binaries, let's do a > public (rubyforge/clr) announcement. Sound good? I think an announcement that "we have tagged the code as 0.0.37 in preparation for a release" and that "binary gems will start to appear shortly" would make sense. Hopefully most folks on the users list are installing from binary gems, so I don't want to confuse them or encourage them to switch how they have it installed. Then, as each binary gets uploaded, maybe we should post a note to users about that, so folks could know to try it (or avoid pulling a gem for a bit if they don't want to be a 0.0.37 pioneer? Kevin From wxruby at qualitycode.com Tue Oct 24 10:20:28 2006 From: wxruby at qualitycode.com (Kevin Smith) Date: Tue, 24 Oct 2006 10:20:28 -0400 Subject: [Wxruby-development] tagged 0.0.37; release plans In-Reply-To: <453E0514.9060705@qualitycode.com> References: <453DC9E2.9020203@pressure.to> <453E0514.9060705@qualitycode.com> Message-ID: <453E212C.7000207@qualitycode.com> Kevin Smith wrote: > Alex Fenton wrote: >> Hi >> >> I just tagged 0.0.37 in Subversion. I also added a note on the Wiki on >> how to do this, and how to checkout a clean version: >> >> http://wxruby.rubyforge.org/wiki/wiki.pl?Release_HowTo > > Ok. I can do an Ubuntu build today. Actually, I probably can't. I haven't installed scintilla yet. Roy, can you build the Linux gem? If not, it will take me a couple/few days. Kevin From sean.m.long at gmail.com Tue Oct 24 11:57:51 2006 From: sean.m.long at gmail.com (Sean Long) Date: Tue, 24 Oct 2006 08:57:51 -0700 Subject: [Wxruby-development] tagged 0.0.37; release plans In-Reply-To: <453E212C.7000207@qualitycode.com> References: <453DC9E2.9020203@pressure.to> <453E0514.9060705@qualitycode.com> <453E212C.7000207@qualitycode.com> Message-ID: I am having a runtime problem with the gem I generate from the 0.0.37 tag. I checked out the source using: svn checkout svn://rubyforge.org/var/svn/wxruby/tags/wxruby2/0.0.37 I built using: rake gem WXSCINTILLA=/Developer/wxscintilla_1.68.1 WXRUBY_RELEASE=true WXRUBY_VERSION=0.0.37 And after I installed the gem and run a sample I got: dyld: NSLinkModule() error dyld: Symbol not found: __Z8wxAssertiPKwiS0_S0_ Referenced from: /usr/local/lib/ruby/gems/1.8/gems/wxruby2-preview-0.0.37-i686-darwin8.4.1/lib/wxruby2.bundle Expected in: flat namespace Trace/BPT trap I did 2 clean builds and got the same error, looks like something with wxAssert. Unfortunately I ran out of time to play with it and had to go to work. Alex did you get anything similar with the PPC build? I will not be able to try compiling again until late tonight. Sean From alex at pressure.to Tue Oct 24 11:58:47 2006 From: alex at pressure.to (Alex Fenton) Date: Tue, 24 Oct 2006 16:58:47 +0100 Subject: [Wxruby-development] tagged 0.0.37; release plans In-Reply-To: <453E212C.7000207@qualitycode.com> References: <453DC9E2.9020203@pressure.to> <453E0514.9060705@qualitycode.com> <453E212C.7000207@qualitycode.com> Message-ID: <453E3837.5060207@pressure.to> Kevin Smith wrote: > Actually, I probably can't. I haven't installed scintilla yet. Roy, can > you build the Linux gem? If not, it will take me a couple/few days > The Scintilla support isn't in there yet for Linux rakefile, so it won't build that anyway with 0.0.37 as tagged. So no problem if the binary doesn't have it - just be good to get one out there. The release notes and changelog only specify it as new on OS X. Of course, it would be great to add Scintilla very soon for Linux, certainly for 0.0.38. thanks alex From alex at pressure.to Tue Oct 24 12:57:48 2006 From: alex at pressure.to (Alex Fenton) Date: Tue, 24 Oct 2006 17:57:48 +0100 Subject: [Wxruby-development] tagged 0.0.37; release plans In-Reply-To: References: <453DC9E2.9020203@pressure.to> <453E0514.9060705@qualitycode.com> <453E212C.7000207@qualitycode.com> Message-ID: <453E460C.2080305@pressure.to> Sean Long wrote: > I am having a runtime problem with the gem I generate from the 0.0.37 tag. > > I checked out the source using: > svn checkout svn://rubyforge.org/var/svn/wxruby/tags/wxruby2/0.0.37 > > I built using: > rake gem WXSCINTILLA=/Developer/wxscintilla_1.68.1 WXRUBY_RELEASE=true > WXRUBY_VERSION=0.0.37 > looks good. > And after I installed the gem and run a sample I got: > > dyld: NSLinkModule() error > dyld: Symbol not found: __Z8wxAssertiPKwiS0_S0_ > Referenced from: > /usr/local/lib/ruby/gems/1.8/gems/wxruby2-preview-0.0.37-i686-darwin8.4.1/lib/wxruby2.bundle > Expected in: flat namespace > > Alex did you get anything similar with the PPC build? No, afraid I haven't seen this. I actually ended up building against wxscintilla CVS, at Otto Wyss's request, although 1.68.1 worked. Sorry for not posting this before. Maybe worth a shot? The CVSROOT and directory is (from browsing, can't try this out on this PC). :pserver:anonymous at wxcode.cvs.sourceforge.net:/cvsroot/wxcode/wxCode/components/wxscintilla/ Alternately, I suppose it could be related to the recently applied change to App.i (although it didn't touch assert, only initialize). This was changed in revision 712, so maybe: svn checkout -r 711 svn://rubyforge.org/var/svn/wxruby/trunk/wxruby2/ alex From roys at mindspring.com Tue Oct 24 15:31:43 2006 From: roys at mindspring.com (Roy Sutton) Date: Tue, 24 Oct 2006 15:31:43 -0400 Subject: [Wxruby-development] tagged 0.0.37; release plans In-Reply-To: <453E212C.7000207@qualitycode.com> References: <453DC9E2.9020203@pressure.to> <453E0514.9060705@qualitycode.com> <453E212C.7000207@qualitycode.com> Message-ID: <453E6A1F.9040107@mindspring.com> Kevin Smith wrote: > Kevin Smith wrote: > >> Alex Fenton wrote: >> >>> Hi >>> >>> I just tagged 0.0.37 in Subversion. I also added a note on the Wiki on >>> how to do this, and how to checkout a clean version: >>> >>> http://wxruby.rubyforge.org/wiki/wiki.pl?Release_HowTo >>> >> Ok. I can do an Ubuntu build today. >> > > Actually, I probably can't. I haven't installed scintilla yet. Roy, can > you build the Linux gem? If not, it will take me a couple/few days. This is on my list. My Ubuntu box went offline over the weekend and I haven't gotten it back yet. I did manage to get a 'make release' done on Scintilla but didn't get to the linking part with wxRuby. If I can make it to the office today I'll restart the machine. Roy From roys at mindspring.com Tue Oct 24 19:23:18 2006 From: roys at mindspring.com (Roy Sutton) Date: Tue, 24 Oct 2006 19:23:18 -0400 Subject: [Wxruby-development] tagged 0.0.37; release plans In-Reply-To: <453E6A1F.9040107@mindspring.com> References: <453DC9E2.9020203@pressure.to> <453E0514.9060705@qualitycode.com> <453E212C.7000207@qualitycode.com> <453E6A1F.9040107@mindspring.com> Message-ID: <453EA066.8050904@mindspring.com> Roy Sutton wrote: > Kevin Smith wrote: > >> Kevin Smith wrote: >> >> >>> Alex Fenton wrote: >>> >>> >>>> Hi >>>> >>>> I just tagged 0.0.37 in Subversion. I also added a note on the Wiki on >>>> how to do this, and how to checkout a clean version: >>>> >>>> http://wxruby.rubyforge.org/wiki/wiki.pl?Release_HowTo >>>> >>>> >>> Ok. I can do an Ubuntu build today. >>> >>> >> Actually, I probably can't. I haven't installed scintilla yet. Roy, can >> you build the Linux gem? If not, it will take me a couple/few days. >> > This is on my list. My Ubuntu box went offline over the weekend and I > haven't gotten it back yet. I did manage to get a 'make release' done > on Scintilla but didn't get to the linking part with wxRuby. If I can > make it to the office today I'll restart the machine. It was the hub that crashed. It takes me over 30 minutes just to link on the Ubuntu box! Anyhow, I -think- Scintilla is compiled in correctly. However, I have to actually test it. Then I'll do a full build on Linux. Roy From roys at mindspring.com Tue Oct 24 22:37:09 2006 From: roys at mindspring.com (Roy Sutton) Date: Tue, 24 Oct 2006 22:37:09 -0400 Subject: [Wxruby-development] wxPrinterDC Message-ID: <453ECDD5.7060801@mindspring.com> wxPrinterDC doesn't seem to be supported on GTK. Not sure why that is. There's nothing in the docs about it not existing. I'm debating what to do. Roy From roys at mindspring.com Tue Oct 24 23:08:56 2006 From: roys at mindspring.com (Roy Sutton) Date: Tue, 24 Oct 2006 23:08:56 -0400 Subject: [Wxruby-development] PrinterDC.i Patch Message-ID: <453ED548.1060501@mindspring.com> This patch allows PrinterDC to go merrily by on Linux. I'm not sure it's the best solution to the problem so I submit it for your approval. Roy -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: PrinterDC.i.patch Url: http://rubyforge.org/pipermail/wxruby-development/attachments/20061024/585c15f2/attachment.pl From roys at mindspring.com Wed Oct 25 00:38:58 2006 From: roys at mindspring.com (Roy Sutton) Date: Wed, 25 Oct 2006 00:38:58 -0400 Subject: [Wxruby-development] Windows gem Message-ID: <453EEA62.604@mindspring.com> I have built the Windows gem and installed it. Unfortunately it crashes every time I try to run a sample in bigdemo. I will try to diagnose the issue. Gem on hold for now. Roy From nobody at rubyforge.org Wed Oct 25 00:57:13 2006 From: nobody at rubyforge.org (nobody at rubyforge.org) Date: Wed, 25 Oct 2006 00:57:13 -0400 (EDT) Subject: [Wxruby-development] [718] trunk/wxruby2/swig/classes/App.i: Put back Initialize function Message-ID: <20061025045713.B315352409CE@rubyforge.org> An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wxruby-development/attachments/20061025/5f33ce03/attachment.html From roys at mindspring.com Wed Oct 25 01:48:55 2006 From: roys at mindspring.com (Roy Sutton) Date: Wed, 25 Oct 2006 01:48:55 -0400 Subject: [Wxruby-development] Linux Scintilla support Message-ID: <453EFAC7.8060903@mindspring.com> I have a Linux gem that appears to work with Scintilla. I'm not able to really see what's going on because my VNC connection is hosed to my Linux box. The scintilla sample appears to work but I can't see the code window on bigdemo. I also get a lot of GLib and Gdk warnings and errors while running. Doesn't sound good to me. I'm happy to post the gem somewhere so someone else can test it. It's entirely possible I've hosed up something on my machine. I'll post the rakelinux.rb patch for someone else to look over. Roy From roys at mindspring.com Wed Oct 25 01:51:05 2006 From: roys at mindspring.com (Roy Sutton) Date: Wed, 25 Oct 2006 01:51:05 -0400 Subject: [Wxruby-development] rakelinux.rb Message-ID: <453EFB49.50408@mindspring.com> This patch should allow Scintilla to work on Linux (if build correctly). -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: rakelinux.rb.patch Url: http://rubyforge.org/pipermail/wxruby-development/attachments/20061025/6bce071e/attachment.ksh From sean.m.long at gmail.com Wed Oct 25 04:24:09 2006 From: sean.m.long at gmail.com (Sean Long) Date: Wed, 25 Oct 2006 01:24:09 -0700 Subject: [Wxruby-development] tagged 0.0.37; release plans In-Reply-To: <453E460C.2080305@pressure.to> References: <453DC9E2.9020203@pressure.to> <453E0514.9060705@qualitycode.com> <453E212C.7000207@qualitycode.com> <453E460C.2080305@pressure.to> Message-ID: > No, afraid I haven't seen this. I actually ended up building against > wxscintilla CVS, at Otto Wyss's request, although 1.68.1 worked. Sorry > for not posting this before. Maybe worth a shot? Sorry but that did not fix it. > Alternately, I suppose it could be related to the recently applied > change to App.i (although it didn't touch assert, only initialize). This > was changed in revision 712, so maybe: > > svn checkout -r 711 svn://rubyforge.org/var/svn/wxruby/trunk/wxruby2/ And that did not work either, the only way I can get a working build is not including wxscintilla. Should I upload the 0.0.37 without scintilla for OS X x86? Sean From alex at pressure.to Wed Oct 25 04:29:03 2006 From: alex at pressure.to (Alex Fenton) Date: Wed, 25 Oct 2006 09:29:03 +0100 Subject: [Wxruby-development] PrinterDC.i Patch In-Reply-To: <453ED548.1060501@mindspring.com> References: <453ED548.1060501@mindspring.com> Message-ID: <453F204F.6040900@pressure.to> Roy Sutton wrote: > This patch allows PrinterDC to go merrily by on Linux. Thanks for debugging this and the patch. > I'm not sure it's the best solution to the problem so I submit it for > your approval. Nor am I. We're going to have more of this type of problem when we start supporting wx-2.8 only classes. So I wonder what the best option is. Off the top off my head: 1) hack rakefile so it removes the unwanted classes from the dependency chain (requires some work, perhaps object-orienting the code that returns lists of classes so it can be subclassed on different platforms, and perhaps has a mix-in for different wx versions. Once it's done it's done; but also means the configuration is somewhat removed from the class) 2) find some flag that can be added to the .i file way for SWIG to halt, or signal to the postprocessors that the class should be removed: #ifdef __WXGTK__ %dontprocessme #endif ... (also needs some work, may confuse rake and make it repeatedly try to SWIG classes it shouldn't. but maybe puts the configuration closer to the class; easier to add piecemeal) Thoughts? I think I marginally lean towards 1). alex From alex at pressure.to Wed Oct 25 04:32:38 2006 From: alex at pressure.to (Alex Fenton) Date: Wed, 25 Oct 2006 09:32:38 +0100 Subject: [Wxruby-development] Windows gem In-Reply-To: <453EEA62.604@mindspring.com> References: <453EEA62.604@mindspring.com> Message-ID: <453F2126.7030009@pressure.to> Roy Sutton wrote: > I have built the Windows gem and installed it. Unfortunately it crashes > every time I try to run a sample in bigdemo. I will try to diagnose the > issue. Gem on hold for now. OK thanks. I'm not making any announcements for the moment :/ For some weird reason everything's sweet as pie on PowerPC OS X, but even with 0.0.36 I was seeing segfaults running my own code on Windows that I didn't see on OS X. I couldn't diagnose it, but your insight about GC and allocation explains why I was seeing crashes at seemingly random times. alex From alex at pressure.to Wed Oct 25 04:35:53 2006 From: alex at pressure.to (Alex Fenton) Date: Wed, 25 Oct 2006 09:35:53 +0100 Subject: [Wxruby-development] Linux Scintilla support In-Reply-To: <453EFAC7.8060903@mindspring.com> References: <453EFAC7.8060903@mindspring.com> Message-ID: <453F21E9.9090901@pressure.to> Roy Sutton wrote: > I have a Linux gem that appears to work with Scintilla. Cool, thanks for the patch also. I'm not going to apply this as I don't have a Linux box, but perhaps Kevin might pick this up at some point. Alternately, we know there are a couple of people with Linux and the build toolchain set up on wxruby-users, perhaps you could post the patch and/or gem there and ask for help? alex From alex at pressure.to Wed Oct 25 07:07:43 2006 From: alex at pressure.to (Alex Fenton) Date: Wed, 25 Oct 2006 12:07:43 +0100 Subject: [Wxruby-development] OS X intel Message-ID: <453F457F.2070504@pressure.to> Hi Sean Thanks for the info on OS intel. Glad that at least it's only broken on Scintilla, not generally. If you could upload a gem w/o Scintilla that would be great. Perhaps some library or framework that's needed on 10.4 that 10.3 doesn't need. I don't know. cheers alex From sean.m.long at gmail.com Wed Oct 25 11:02:51 2006 From: sean.m.long at gmail.com (Sean Long) Date: Wed, 25 Oct 2006 08:02:51 -0700 Subject: [Wxruby-development] OS X intel In-Reply-To: <453F457F.2070504@pressure.to> References: <453F457F.2070504@pressure.to> Message-ID: > Perhaps some library or framework that's needed on 10.4 that 10.3 > doesn't need. I don't know. I forgot you are running 10.3, maybe you are right and the problem is with the OS version not the cpu architecture. I uploaded the OS X intel gem Sean From alex at pressure.to Wed Oct 25 13:43:35 2006 From: alex at pressure.to (Alex Fenton) Date: Wed, 25 Oct 2006 18:43:35 +0100 Subject: [Wxruby-development] OS X intel In-Reply-To: References: <453F457F.2070504@pressure.to> Message-ID: <453FA247.7050309@pressure.to> Sean Long wrote: >> Perhaps some library or framework that's needed on 10.4 that 10.3 >> doesn't need. I don't know. >> > I forgot you are running 10.3, maybe you are right and the problem is > with the OS version not the cpu architecture. > Thanks very much for the gem. Just one more thought - are you able to build and run the sample included with wxscintilla? It doesn't run properly on OS X b/c it's not stuffed into an .app so it doesn't detach from the Finder or the console correctly, but we should be able to rule out the undefined symbol coming from wxscintilla itself. alex From alex at pressure.to Wed Oct 25 13:51:03 2006 From: alex at pressure.to (Alex Fenton) Date: Wed, 25 Oct 2006 18:51:03 +0100 Subject: [Wxruby-development] textile docs In-Reply-To: <453D7F74.4050507@mindspring.com> References: <453D7F74.4050507@mindspring.com> Message-ID: <453FA407.6010409@pressure.to> Roy Sutton wrote: > Why are the textile > files uploaded to the server? > Hmm.. I'm not quite sure. Because they're linked to from the HTML output, at the moment - but that's not really an answer. I suppose a vague hope that someone would see the input format, spot something needing correction, and think 'Wow, this agile lightweight format is so easy to edit, I'll just download it, make the change and send it to the mailing list'. For a volunteer open-source project, that's probably a pretty focussed documentation strategy ;) alex From alex at pressure.to Wed Oct 25 13:57:54 2006 From: alex at pressure.to (Alex Fenton) Date: Wed, 25 Oct 2006 18:57:54 +0100 Subject: [Wxruby-development] persistent preferences In-Reply-To: <453AD0D8.70106@qualitycode.com> References: <453A3D5E.7050508@pressure.to> <453AD0D8.70106@qualitycode.com> Message-ID: <453FA5A2.60602@pressure.to> > Not sure about that. I haven't looked, but one would hope that there is > a non-GUI-specific persistent-app-setting library we could point people > to, instead of inventing our own. If we do invent our own, I would > encourage it to be distinct from wxruby, as it could be equally useful > to curses or ruby-gtk apps. Funnily enough, this came up on c.l.r, and seems Joel Vanderwerf wrote something for FxRuby http://redshift.sourceforge.net/preferences/ The licence isn't clear, and it seems intended to work with objects that have symmetric (rubyish) setters and getters, which we don't. But maybe a starting point. alex From sean.m.long at gmail.com Wed Oct 25 14:21:06 2006 From: sean.m.long at gmail.com (Sean Long) Date: Wed, 25 Oct 2006 11:21:06 -0700 Subject: [Wxruby-development] OS X intel In-Reply-To: References: <453F457F.2070504@pressure.to> Message-ID: I just did a build on 0.0.37 on OS X 10.4 PPC with scintilla and got the same error I am getting on Intel. Looks more and more like a 10.3 vs 10.4 problem. Sean From sean.m.long at gmail.com Wed Oct 25 17:20:08 2006 From: sean.m.long at gmail.com (Sean Long) Date: Wed, 25 Oct 2006 14:20:08 -0700 Subject: [Wxruby-development] OS X intel In-Reply-To: <453FA247.7050309@pressure.to> References: <453F457F.2070504@pressure.to> <453FA247.7050309@pressure.to> Message-ID: > Thanks very much for the gem. Just one more thought - are you able to > build and run the sample included with wxscintilla? > It doesn't run properly on OS X b/c it's not stuffed into an .app so it > doesn't detach from the Finder or the console correctly, but we should > be able to rule out the undefined symbol coming from wxscintilla itself. Yes I can build the included sample. I wonder if it is an incompatibility with options passed to the compiler during the wxscintilla build with those used to build wxRuby. Maybe there is a problem caused by the compiler on OS X 10.4 the default compiler is gcc version 4.0.1 not sure what it is on 10.3. Maybe tonight I can look at it some more. Sean From alex at pressure.to Thu Oct 26 03:31:04 2006 From: alex at pressure.to (Alex Fenton) Date: Thu, 26 Oct 2006 08:31:04 +0100 Subject: [Wxruby-development] OS X intel In-Reply-To: References: <453F457F.2070504@pressure.to> <453FA247.7050309@pressure.to> Message-ID: <45406438.8080802@pressure.to> Sean Long wrote: > I wonder if it is an incompatibility with options passed to the > compiler during the wxscintilla build with those used to build wxRuby. > That sounds plausible. > Maybe there is a problem caused by the compiler on OS X 10.4 the > default compiler is gcc version 4.0.1 not sure what it is on 10.3. > SCIPIUS:~ alex$ g++ --version g++ (GCC) 3.3 20030304 (Apple Computer, Inc. build 1666) alex From wxruby at qualitycode.com Thu Oct 26 08:36:03 2006 From: wxruby at qualitycode.com (Kevin Smith) Date: Thu, 26 Oct 2006 08:36:03 -0400 Subject: [Wxruby-development] Handling platform-only classes (was: PrinterDC.i Patch) In-Reply-To: <453F204F.6040900@pressure.to> References: <453ED548.1060501@mindspring.com> <453F204F.6040900@pressure.to> Message-ID: <4540ABB3.4000809@qualitycode.com> Alex Fenton wrote: > 1) hack rakefile so it removes the unwanted classes from the dependency > chain (snip) > > 2) find some flag that can be added to the .i file way for SWIG to halt, > or signal to the postprocessors that the class should be removed: (snip) > > Thoughts? I think I marginally lean towards 1). I think I agree. The simplest would be to just have a list of excluded classes in the platform-specific rakefiles. When constructing the list of classes, take the list of .i files minus the list of files not available on this platform. Kevin From wxruby at qualitycode.com Thu Oct 26 08:37:33 2006 From: wxruby at qualitycode.com (Kevin Smith) Date: Thu, 26 Oct 2006 08:37:33 -0400 Subject: [Wxruby-development] Windows gem In-Reply-To: <453F2126.7030009@pressure.to> References: <453EEA62.604@mindspring.com> <453F2126.7030009@pressure.to> Message-ID: <4540AC0D.4000608@qualitycode.com> Alex Fenton wrote: > For some weird reason everything's sweet as pie on PowerPC OS X, but > even with 0.0.36 I was seeing segfaults running my own code on Windows > that I didn't see on OS X. I couldn't diagnose it, but your insight > about GC and allocation explains why I was seeing crashes at seemingly > random times. It sounds like you guys are finally seeing what I have been seeing on Linux all along. Stuff like minimal works fine, but bigdemo never goes more than a few seconds before crashing. Kevin From wxruby at qualitycode.com Thu Oct 26 08:45:38 2006 From: wxruby at qualitycode.com (Kevin Smith) Date: Thu, 26 Oct 2006 08:45:38 -0400 Subject: [Wxruby-development] persistent preferences In-Reply-To: <453FA5A2.60602@pressure.to> References: <453A3D5E.7050508@pressure.to> <453AD0D8.70106@qualitycode.com> <453FA5A2.60602@pressure.to> Message-ID: <4540ADF2.8050204@qualitycode.com> Alex Fenton wrote: > Funnily enough, this came up on c.l.r, and seems Joel Vanderwerf wrote > something for FxRuby > > http://redshift.sourceforge.net/preferences/ > > The licence isn't clear, The intro.txt file says it's under the "Ruby License". > and it seems intended to work with objects that > have symmetric (rubyish) setters and getters, which we don't. But maybe > a starting point. It might not be able to directly persist some/all standard wx classes, but it certainly seems like it would meet the needs of most apps that want to save some settings in a standard place. And it looks like it does a good job with cross-platform directories. Looks like a winner if it actually does what it says it does. Kevin From alex at pressure.to Mon Oct 30 11:08:55 2006 From: alex at pressure.to (Alex Fenton) Date: Mon, 30 Oct 2006 16:08:55 +0000 Subject: [Wxruby-development] PrinterDC.i Patch In-Reply-To: <453ED548.1060501@mindspring.com> References: <453ED548.1060501@mindspring.com> Message-ID: <45462397.3000504@pressure.to> This patch excludes PrinterDC on Linux, and also creates a general way to hide classes that aren't supported (eg between versions). I haven't tested it on Linux, but the principle seems to work. alex Roy Sutton wrote: > This patch allows PrinterDC to go merrily by on Linux. I'm not sure > it's the best solution to the problem so I submit it for your approval. > > Roy > ------------------------------------------------------------------------ > > Index: wxruby2/swig/classes/PrinterDC.i > =================================================================== > --- wxruby2/swig/classes/PrinterDC.i (revision 710) > +++ wxruby2/swig/classes/PrinterDC.i (working copy) > @@ -5,7 +5,23 @@ > > %module(directors="1") wxPrinterDC > > +#ifdef __WXGTK__ > + > +%{ > +class wxPrinterDC > +{ > +}; > +%} > + > +class wxPrinterDC > +{ > +}; > + > +#else > + > %import "include/wxObject.h" > %import "include/wxDC.h" > > %include "include/wxPrinterDC.h" > + > +#endif // __WXGTK__ > > ------------------------------------------------------------------------ > > _______________________________________________ > Wxruby-development mailing list > Wxruby-development at rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-development > -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: rake_excl_classes.patch Url: http://rubyforge.org/pipermail/wxruby-development/attachments/20061030/27f1625a/attachment.pl From alex at pressure.to Mon Oct 30 11:13:54 2006 From: alex at pressure.to (Alex Fenton) Date: Mon, 30 Oct 2006 16:13:54 +0000 Subject: [Wxruby-development] memory mgmt etc Message-ID: <454624C2.8080302@pressure.to> Hi Seems we ran into what football commentators call a 'run of bad form', when you can't get the ball in the net for love nor money, and your defence is leaking goals like an extension library leaks memory. But no bad run lasts forever, so wanted to get your thoughts on what we should focus on next. Apologies for a longish email. Roy's experiences with 0.0.37 on Windows, and Kevin's comments on Linux suggest to me that we shouldn't continue avoiding addressing memory management. I've been doing a bit of testing on OS X, and I think the reason Sean and I are not getting crashes is that Ruby GC is not collecting destroyed objects until shutdown - ie being overly conservative. So I re-read some docs to see what might be giving us problems: http://www.swig.org/Doc1.3/Ruby.html#Ruby_nn57 http://wxruby.rubyforge.org/wiki/wiki.pl?Memory_Management While the wiki page is useful, it's important to bear in mind that it predates the release of SWIG 1.3.26, which includes the additional features for marking and tracking. So my first question is: 1) What's the status of the handcoded memory management (especially in wx.i and fixdeleting.rb)? Will current SWIG do everything we need in terms of linking ruby to c++ objs, and preventing c++ objects being destroyed twice, if %trackobjects is enabled? Is this the route we should go? What's especially useful on the wiki page is the clear explanation of the kind of situations that might create problems. It'd be useful to understand better which of these might be causing the segfaults we're seeing. So: 2) Crashes in bigdemo: - do they happen if you launch the app and do nothing? - do they happen if you launch the app and just wiggle and click the mouse? - or they only happen if widgets are being created and destroyed in the demo pane? A task I want to work on is to develop simpler test cases for the memory management crashers - ones that contain fewer routes and fewer types of widgets than bigdemo. Ideally they can run without user interaction. Roy - perhaps you could hook me up with a 0.0.37 windows gem. Other things that need fixing, but are probably lower priority: 1) WxScintilla - let's not sweat it. It's great that we have it up and running on Windows and OS X 10.3. It will come. 2) Missing classes: HTMLWindow, HTMLEasyPrinting, Drag'n'Drop, Clipboard. With that little list tackled, I think we're looking good for a beta release. What do others think? cheers alex From sean.m.long at gmail.com Mon Oct 30 12:23:19 2006 From: sean.m.long at gmail.com (Sean Long) Date: Mon, 30 Oct 2006 09:23:19 -0800 Subject: [Wxruby-development] PrinterDC.i Patch In-Reply-To: <45462397.3000504@pressure.to> References: <453ED548.1060501@mindspring.com> <45462397.3000504@pressure.to> Message-ID: > I haven't tested it on Linux, but the principle seems to work. Looks like it should work. Isn't the #ifdef __WXGTK__ #endif redundant with the the $excluded_classes being used? Or am I missing something? On another note over the weekend I setup FreeBSD 6.1 under Parallels and got the SVN HEAD of wxRuby2 to work just fine, the only change I had to make was the #ifdef __WXGTK__ in PrinterDC.i. I did not test scintilla on FreeBSD yet. Sean From alex at pressure.to Mon Oct 30 14:10:27 2006 From: alex at pressure.to (Alex Fenton) Date: Mon, 30 Oct 2006 19:10:27 +0000 Subject: [Wxruby-development] PrinterDC.i Patch In-Reply-To: References: <453ED548.1060501@mindspring.com> <45462397.3000504@pressure.to> Message-ID: <45464E23.6050006@pressure.to> Sean Long wrote: > Looks like it should work. > > Isn't the #ifdef __WXGTK__ #endif redundant with the the > $excluded_classes being used? Or am I missing something? > Yes, this replaces the patch to PrinterDC.i. I think it's a neater way to solve the same problem. > On another note over the weekend I setup FreeBSD 6.1 under Parallels > and got the SVN HEAD of wxRuby2 to work just fine, the only change I > had to make was the #ifdef __WXGTK__ in PrinterDC.i. Cool, good to try on another platform. I am starting to develop an irrational desire to get a new intel mac... Please feel free to commit the rake changes if you get a chance to try them on BSD Thanks alex From sean.m.long at gmail.com Tue Oct 31 19:13:54 2006 From: sean.m.long at gmail.com (Sean Long) Date: Tue, 31 Oct 2006 16:13:54 -0800 Subject: [Wxruby-development] PrinterDC.i Patch In-Reply-To: <45464E23.6050006@pressure.to> References: <453ED548.1060501@mindspring.com> <45462397.3000504@pressure.to> <45464E23.6050006@pressure.to> Message-ID: > Please feel free to commit the rake changes if you get a chance to try > them on BSD The changes work on FreeBSD I do not have the time to commit them right now. Sean From nobody at rubyforge.org Tue Oct 31 20:37:16 2006 From: nobody at rubyforge.org (nobody at rubyforge.org) Date: Tue, 31 Oct 2006 20:37:16 -0500 (EST) Subject: [Wxruby-development] [719] trunk/wxruby2: Hide unsupported PrinterDC class on GTK (Alex Fenton) Message-ID: <20061101013716.A1A215242338@rubyforge.org> An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wxruby-development/attachments/20061031/621edece/attachment.html