From mjbjr at beaudesign.com Tue Jul 12 21:59:31 2005 From: mjbjr at beaudesign.com (mjbjr@beaudesign.com) Date: Tue Jul 12 21:54:19 2005 Subject: [Wxruby-users] comm between gui and app? Message-ID: <20050713015931.GA28020@beaudesign.com> To me, the main app (an object) is separate from the app gui (object)... MVC'ish. How can I have the gui part communicate to the app that an event has taken place? Example code somewhere? Thank you. -- - Martin J. Brown, Jr. - - mjbjr@beaudesign.com - Public PGP Key ID: 0xB09AFEFE keyserver: http://pgpkeys.mit.edu:11371/ Key fingerprint = F3C4 503E 6239 E395 1D33 2FA6 CF11 6F34 B09A FEFE -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://rubyforge.org/pipermail/wxruby-users/attachments/20050712/c8625fb8/attachment-0001.bin From wxruby at qualitycode.com Tue Jul 12 22:33:55 2005 From: wxruby at qualitycode.com (Kevin Smith) Date: Tue Jul 12 22:29:17 2005 Subject: [Wxruby-users] comm between gui and app? In-Reply-To: <20050713015931.GA28020@beaudesign.com> References: <20050713015931.GA28020@beaudesign.com> Message-ID: <42D47D93.6090108@qualitycode.com> mjbjr@beaudesign.com wrote: > To me, the main app (an object) is separate from the app gui (object)... > MVC'ish. > > How can I have the gui part communicate to the app that an event has > taken place? Example code somewhere? The short answer to your question as asked would be that you would simply invoke normal ruby methods in your app class. Something like this (written in email and never run through ruby): ##################################### class MyApp < Wx::App ... def something_happened puts("something happened!") end ... end class MyMainFrame < Wx::Frame ... def on_click Wx::get_app.something_happened end ... end ##################################### Hm. That call to get_app.something_happened probably won't work in wxruby 0.6 because it doesn't have great support for extending subclassed classes. Maybe, though. It might not even work in wxruby-swig, but I think it would. If not, the alternative to simply keep a global $app variable, and invoke $app.something_happened. In a perfect world, wxruby would support the Wx::Document class, which might be a better place for your non-GUI logic. Unfortunately, neither wxruby 0.6 nor wxruby-swig supports that yet. However, you could create your own document (aka model) class, and create it in your frame initializer. In that case, the sample above would end up more like: def on_click @model.something_happened end If you wanted to get fancier, you could use the wx event system to pass messages to a document or to your app. Your document would be a subclass of Wx::EventHandler, which would allow it to receive events. However, that's very much uncharted territory, so if you experiment with it, you might be the first person on the planet ever to have done so. Hope that helps. Kevin From alex at pressure.to Thu Jul 14 04:02:42 2005 From: alex at pressure.to (alex fenton) Date: Thu Jul 14 03:58:02 2005 Subject: [Wxruby-users] comm between gui and app? In-Reply-To: <20050713015931.GA28020@beaudesign.com> References: <20050713015931.GA28020@beaudesign.com> Message-ID: <42D61C22.8090301@pressure.to> Hi What sort of GUI events are they, and, importantly, are they things that the GUI needs to update in response to the results? As Kevin suggested, it might be easiest for the GUI to call the app object's methods - the app should expose a set of methods that correspond to the actions that can be performed through the GUI Weft QDA (http://www.pressure.to/qda/) follows this model for gui->app communication. app->gui communication - including presenting the results of user actions - is handled by a module similar to Observable (in the standard library). When an updateable UI element is created, it subscribes to global app events that it is interested in. class Widget include Subscriber def initialize(foo, bar) ... subscribe(:category_added, :category_changed) end def receive_category_added(category) update_myself_to_show_new_category end end hth alex mjbjr@beaudesign.com wrote: > To me, the main app (an object) is separate from the app gui (object)... > MVC'ish. > > How can I have the gui part communicate to the app that an event has > taken place? Example code somewhere? > > Thank you. > > > > ------------------------------------------------------------------------ > > _______________________________________________ > wxruby-users mailing list > wxruby-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-users From mjbjr at beaudesign.com Thu Jul 14 04:23:44 2005 From: mjbjr at beaudesign.com (mjbjr@beaudesign.com) Date: Thu Jul 14 04:18:29 2005 Subject: [Wxruby-users] comm between gui and app? In-Reply-To: <42D47D93.6090108@qualitycode.com> References: <20050713015931.GA28020@beaudesign.com> <42D47D93.6090108@qualitycode.com> Message-ID: <20050714082344.GA30107@beaudesign.com> Well, I was hoping to not have to sub-class Frame, but that's what I've done. Now, the mainApp object passes 'self' to the myFrame object on instantiation. -- - Martin J. Brown, Jr. - - mjbjr@beaudesign.com - Public PGP Key ID: 0xB09AFEFE keyserver: http://pgpkeys.mit.edu:11371/ Key fingerprint = F3C4 503E 6239 E395 1D33 2FA6 CF11 6F34 B09A FEFE -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://rubyforge.org/pipermail/wxruby-users/attachments/20050714/c3dca730/attachment.bin From wxruby at qualitycode.com Sat Jul 16 09:32:00 2005 From: wxruby at qualitycode.com (Kevin Smith) Date: Sat Jul 16 09:26:48 2005 Subject: [Wxruby-users] wxruby (was: [FR-devel] Some questions) In-Reply-To: <42D83767.6010208@mindspring.com> References: <42D79938.8090402@xs4all.nl> <42D7BD75.8030708@mindspring.com> <42D8245F.6070801@hibbs.com> <42D83767.6010208@mindspring.com> Message-ID: <42D90C50.4060008@qualitycode.com> Roy Sutton wrote (on the FreeRIDE list): > Really? That's interesting. I haven't checked out WxRuby but I would > be much happier using something that interfaces to the underlying > operating system's widgets. As a member (and former leader) of the wxruby team, I thought I would share the state of the wxruby world. The current release is 0.6, and it has pretty good widget support, but has a few stability problems, and some pretty bad memory leaks. We are rewriting wxruby from scratch using swig, which has some significant benefits: - Fixes the leaks and other memory problems - Provides much better support for subclassing wx classes - Makes it easier for non-coders to add support for more classes Unfortunately, none of us on the team have had time to bring wxruby-swig up to the level where it supports all the classes that are in wxruby 0.6. So wxruby-swig has not yet been released. And although we still believe in wxruby, none of us are actively developing it right now. A motivated person could rapidly make a lot of progress, even if they don't know C++. I can offer quick and deep technical support to anyone interested in working on wxruby-swig. Oh...one other issue. We are a bit caught between supporting the upstream wx 2.4 library and the recently-released 2.6 version. So far, we have focused on 2.4, but as time goes by, more and more people would rather have a version that works with 2.6. Kevin From sean.m.long at gmail.com Sun Jul 17 03:02:15 2005 From: sean.m.long at gmail.com (Sean Long) Date: Sun Jul 17 02:56:56 2005 Subject: [Wxruby-users] wxruby (was: [FR-devel] Some questions) In-Reply-To: <42D90C50.4060008@qualitycode.com> References: <42D79938.8090402@xs4all.nl> <42D7BD75.8030708@mindspring.com> <42D8245F.6070801@hibbs.com> <42D83767.6010208@mindspring.com> <42D90C50.4060008@qualitycode.com> Message-ID: Kevin, You are in luck! Over the last week or so I have been hacking on wxruby swig version from CVS. I have made it compile and run on wxWidgets 2.6.1 on Mac OS X and Windows XP using VS .Net. I have added support for: XMLResource ProgressDialog Validator Icon FindReplaceDialog I have tested the following sample projects successfully: caret dialogs etc images minimal xrc I am working on getting the controls sample working After working on this for awhile I think the project should only focus on wxWidgets 2.6.1 and beyond. If anyone wants to use wxWidgets 2.4.x they can use the old wxRuby 0.6 path. I also think we should look into getting rid of the wxclasses-2.4.2.xml for class and method definitions and do it all with *.i. With the *.i files we have more control over conditional compilation for the different platforms and libraries that people may want to leave out when compiling wxruby. Not to mention it really slows down the development process having to parse the XML files every-time something is added to extractxml.rb. Since I can not write back to the CVS repository I am posting my changes zipped up to: http://www.hailstonesoftware.com/wxruby/wxruby-swig_07_16_2005.zip it is 2.71 MB NOTES: - I renamed rake.bat in the root directory to rake2.bat because it messed up rake usage on Windows for me. - In extconf.rb ENV['WXWIN'] did not work for me so I have $WXDIR hard coded for the windows version. - Also note I have not used SWIG before so excuse any stupid looking mistakes :) Used: SWIG 1.3.24 Rake 0.5.3 Ruby 1.8.2 wxWidgets 2.6.1 Windows XP Pro Service pack 2 Mac OS X 10.4.2 Sean Long On 7/16/05, Kevin Smith wrote: > Roy Sutton wrote (on the FreeRIDE list): > > Really? That's interesting. I haven't checked out WxRuby but I would > > be much happier using something that interfaces to the underlying > > operating system's widgets. > > As a member (and former leader) of the wxruby team, I thought I would > share the state of the wxruby world. > > The current release is 0.6, and it has pretty good widget support, but > has a few stability problems, and some pretty bad memory leaks. We are > rewriting wxruby from scratch using swig, which has some significant > benefits: > - Fixes the leaks and other memory problems > - Provides much better support for subclassing wx classes > - Makes it easier for non-coders to add support for more classes > > Unfortunately, none of us on the team have had time to bring wxruby-swig > up to the level where it supports all the classes that are in wxruby > 0.6. So wxruby-swig has not yet been released. And although we still > believe in wxruby, none of us are actively developing it right now. A > motivated person could rapidly make a lot of progress, even if they > don't know C++. I can offer quick and deep technical support to anyone > interested in working on wxruby-swig. > > Oh...one other issue. We are a bit caught between supporting the > upstream wx 2.4 library and the recently-released 2.6 version. So far, > we have focused on 2.4, but as time goes by, more and more people would > rather have a version that works with 2.6. > > Kevin > _______________________________________________ > wxruby-users mailing list > wxruby-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-users > From alex at pressure.to Sun Jul 17 06:47:06 2005 From: alex at pressure.to (alex fenton) Date: Sun Jul 17 06:42:29 2005 Subject: [Wxruby-users] wxruby gems In-Reply-To: <42BFF389.50504@qualitycode.com> References: <42BEB543.8040901@pressure.to> <42BFF389.50504@qualitycode.com> Message-ID: <42DA372A.6050808@pressure.to> I've just dusted off the gemspec for wxruby (not-swig) attached. The compiled gems are at http://www.pressure.to/ruby/wxruby-gems.tar.gz if someone wants to test them before uploading them. It would be great if wxruby could be autoinstalled as dependency by rubygems. > Assuming Nick is ok with it, I would propose something like: "wxruby > development team". Folks can check the web site for current and detailed > information. As you suggest, email is wxruby-users@rubyforge.org > Perhaps there should be separate gems for wxruby-docs and wxruby-samples? Will look into it, but prefer to work on this on wxruby-swig source tree ... > Especially the wxruby-swig version, since that's the > one that will receive any of my available time. ... will try and make some for wxruby-swig asap, when i get my pc with compile chain on back from repair. a -------------- next part -------------- require 'rubygems' WXRUBY_GEMSPEC = Gem::Specification.new do | s | s.name = 'wxruby' s.platform = Gem::Platform::WIN32 s.version = '0.6.0' s.summary = "Ruby interface to the WxWidgets GUI library" s.description = <<-EOF WxRuby provides an interface to the WxWidgets library. It enables the creation of GUI applications with native widgets on platforms including Windows, OS X and Linux. EOF s.files = [ 'wxruby.so' ] s.autorequire = 'wxruby' s.require_path = '.' s.has_rdoc = false s.author = "WxRuby development team" s.email = "wxruby-users@rubyforge.org" s.homepage = "http://wxruby.rubyforge.org/" s.rubyforge_project = "wxruby" end -------------- next part -------------- require 'rubygems' WXRUBY_GEMSPEC = Gem::Specification.new do | s | s.name = 'wxruby' s.version = '0.6.0' s.summary = "Ruby interface to the WxWidgets GUI library" s.description = <<-EOF WxRuby provides an interface to the WxWidgets library. It enables the creation of GUI applications with native widgets on platforms including Windows, OS X and Linux. EOF s.files = Dir[ 'src/*' ] s.autorequire = 'wxruby' s.require_path = 'lib' s.extensions << 'src/extconf.rb' s.has_rdoc = false s.author = "WxRuby development team" s.email = "wxruby-users@rubyforge.org" s.homepage = "http://wxruby.rubyforge.org/" s.rubyforge_project = "wxruby" end From snowzone5 at hotmail.com Sun Jul 17 13:10:13 2005 From: snowzone5 at hotmail.com (tony summerfelt) Date: Sun Jul 17 13:03:35 2005 Subject: [Wxruby-users] Re: wxruby In-Reply-To: <42D90C50.4060008@qualitycode.com> References: <42D79938.8090402@xs4all.nl> <42D7BD75.8030708@mindspring.com> <42D8245F.6070801@hibbs.com> <42D83767.6010208@mindspring.com> <42D90C50.4060008@qualitycode.com> Message-ID: <42DA90F5.6070009@hotmail.com> Roy Sutton wrote (on the FreeRIDE list): > And although we still believe in wxruby, none of us are actively developing > it right now. hmm, well i guess that pretty much makes up my mind :/ -- http://home.cogeco.ca/~tsummerfelt1 telnet://ventedspleen.dyndns.org From sean.m.long at gmail.com Sun Jul 17 13:19:54 2005 From: sean.m.long at gmail.com (Sean Long) Date: Sun Jul 17 13:14:32 2005 Subject: [Wxruby-users] Re: wxruby In-Reply-To: <42DA90F5.6070009@hotmail.com> References: <42D79938.8090402@xs4all.nl> <42D7BD75.8030708@mindspring.com> <42D8245F.6070801@hibbs.com> <42D83767.6010208@mindspring.com> <42D90C50.4060008@qualitycode.com> <42DA90F5.6070009@hotmail.com> Message-ID: Tony, See my post under 'wxruby (was: [FR-devel] Some questions)', the core group may not be actively developing it right now but others may be, myself included. Sean Long On 7/17/05, tony summerfelt wrote: > Roy Sutton wrote (on the FreeRIDE list): > > > And although we still believe in wxruby, none of us are actively developing > > it right now. > > hmm, well i guess that pretty much makes up my mind :/ > > > -- > http://home.cogeco.ca/~tsummerfelt1 > telnet://ventedspleen.dyndns.org > > _______________________________________________ > wxruby-users mailing list > wxruby-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-users > From wxruby at qualitycode.com Sun Jul 17 20:29:15 2005 From: wxruby at qualitycode.com (Kevin Smith) Date: Sun Jul 17 20:24:21 2005 Subject: [Wxruby-users] wxruby In-Reply-To: References: <42D79938.8090402@xs4all.nl> <42D7BD75.8030708@mindspring.com> <42D8245F.6070801@hibbs.com> <42D83767.6010208@mindspring.com> <42D90C50.4060008@qualitycode.com> Message-ID: <42DAF7DB.7010601@qualitycode.com> This is great. I really want to leverage your momentum, so I'm setting aside some other important work to try to incorporate your changes into the main wxruby-swig codebase. My approach is to pick one change at a time from your zipped source tree, apply it to a copy of the "official" tree, and check it into CVS. It's a bit tedious, but is safe, and helps me understand what you've done. I'm not sure I'm willing to target only 2.6 yet, since my own system (Ubuntu) only has 2.5 on it. Perhaps targeting 2.5+ for now would be a reasonable compromise. I agree that it is time to drop the .xml file. It has served its purpose as a quick way to build a set of clean wx .h files. However, since it is not very accurate, and especially since it is not being updated upstream, we should stop using it. However, I do want to retain the split between our own .i files and the generic .h files. I'll let you know as I make progress integrating your changes. Thanks! Kevin Sean Long wrote: > Kevin, > > You are in luck! > > Over the last week or so I have been hacking on wxruby swig version > from CVS. I have made it compile and run on wxWidgets 2.6.1 on Mac OS > X and Windows XP using VS .Net. > > I have added support for: > XMLResource > ProgressDialog > Validator > Icon > FindReplaceDialog > > I have tested the following sample projects successfully: > caret > dialogs > etc > images > minimal > xrc > > I am working on getting the controls sample working > > After working on this for awhile I think the project should only focus > on wxWidgets 2.6.1 and beyond. If anyone wants to use wxWidgets 2.4.x > they can use the old wxRuby 0.6 path. > > I also think we should look into getting rid of the > wxclasses-2.4.2.xml for class and method definitions and do it all > with *.i. With the *.i files we have more control over conditional > compilation for the different platforms and libraries that people may > want to leave out when compiling wxruby. Not to mention it really > slows down the development process having to parse the XML files > every-time something is added to extractxml.rb. > > Since I can not write back to the CVS repository I am posting my > changes zipped up to: > http://www.hailstonesoftware.com/wxruby/wxruby-swig_07_16_2005.zip > it is 2.71 MB > > NOTES: > - I renamed rake.bat in the root directory to rake2.bat because it > messed up rake usage on Windows for me. > - In extconf.rb ENV['WXWIN'] did not work for me so I have $WXDIR hard > coded for the windows version. > - Also note I have not used SWIG before so excuse any stupid looking mistakes :) > > Used: > SWIG 1.3.24 > Rake 0.5.3 > Ruby 1.8.2 > wxWidgets 2.6.1 > Windows XP Pro Service pack 2 > Mac OS X 10.4.2 > > Sean Long > > > On 7/16/05, Kevin Smith wrote: > >>Roy Sutton wrote (on the FreeRIDE list): >> >>>Really? That's interesting. I haven't checked out WxRuby but I would >>>be much happier using something that interfaces to the underlying >>>operating system's widgets. >> >>As a member (and former leader) of the wxruby team, I thought I would >>share the state of the wxruby world. >> >>The current release is 0.6, and it has pretty good widget support, but >>has a few stability problems, and some pretty bad memory leaks. We are >>rewriting wxruby from scratch using swig, which has some significant >>benefits: >>- Fixes the leaks and other memory problems >>- Provides much better support for subclassing wx classes >>- Makes it easier for non-coders to add support for more classes >> >>Unfortunately, none of us on the team have had time to bring wxruby-swig >>up to the level where it supports all the classes that are in wxruby >>0.6. So wxruby-swig has not yet been released. And although we still >>believe in wxruby, none of us are actively developing it right now. A >>motivated person could rapidly make a lot of progress, even if they >>don't know C++. I can offer quick and deep technical support to anyone >>interested in working on wxruby-swig. >> >>Oh...one other issue. We are a bit caught between supporting the >>upstream wx 2.4 library and the recently-released 2.6 version. So far, >>we have focused on 2.4, but as time goes by, more and more people would >>rather have a version that works with 2.6. >> >>Kevin >>_______________________________________________ >>wxruby-users mailing list >>wxruby-users@rubyforge.org >>http://rubyforge.org/mailman/listinfo/wxruby-users >> > > > _______________________________________________ > wxruby-users mailing list > wxruby-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-users From wxruby at qualitycode.com Mon Jul 18 00:49:17 2005 From: wxruby at qualitycode.com (Kevin Smith) Date: Mon Jul 18 00:44:05 2005 Subject: [Wxruby-users] Progress on wxruby-swig (was: wxruby) In-Reply-To: <42DAF7DB.7010601@qualitycode.com> References: <42D79938.8090402@xs4all.nl> <42D7BD75.8030708@mindspring.com> <42D8245F.6070801@hibbs.com> <42D83767.6010208@mindspring.com> <42D90C50.4060008@qualitycode.com> <42DAF7DB.7010601@qualitycode.com> Message-ID: <42DB34CD.1090903@qualitycode.com> Quick update: I have checked in most of Sean's wxruby-swig changes, except for those in the swig/ and sample/ directories (which, I realize, are the most interesting ones). It still compiles and the minimal sample still runs, at least on my Ubuntu Linux box. It would be great if someone could do a quick test on Mac and on MS Windows to make sure I didn't break anything big. Xrc is not part of wx 2.4 (which is what I'm still using right now). So I made the Xrc stuff optional. If you do a full build with WXRUBY_XRC in your environment, you should get Xrc support. Since I don't have Xrc, I wasn't able to test this. My next step (tomorrow, hopefully) will be to officially remove wxclasses-2.4.2.xml and extractxml from the project. After that, I will probably bring in the newly added classes, and then try to pull in the updates to existing classes. Finally, I'll bring in the new samples, and whatever else I have forgotten. Somewhere in there, I might take the big plunge to wxWidgets 2.5.3.2, and if that works, I would probably want to officially move wxruby-swig to wx 2.5+, which seemed to be the consensus direction as of a few months ago. Cheers, Kevin Kevin Smith wrote: > This is great. I really want to leverage your momentum, so I'm setting > aside some other important work to try to incorporate your changes into > the main wxruby-swig codebase. > > My approach is to pick one change at a time from your zipped source > tree, apply it to a copy of the "official" tree, and check it into CVS. > It's a bit tedious, but is safe, and helps me understand what you've done. > > I'm not sure I'm willing to target only 2.6 yet, since my own system > (Ubuntu) only has 2.5 on it. Perhaps targeting 2.5+ for now would be a > reasonable compromise. > > I agree that it is time to drop the .xml file. It has served its purpose > as a quick way to build a set of clean wx .h files. However, since it is > not very accurate, and especially since it is not being updated > upstream, we should stop using it. > > However, I do want to retain the split between our own .i files and the > generic .h files. > > I'll let you know as I make progress integrating your changes. > > Thanks! > > Kevin > > > Sean Long wrote: > >> Kevin, >> >> You are in luck! >> >> Over the last week or so I have been hacking on wxruby swig version >> from CVS. I have made it compile and run on wxWidgets 2.6.1 on Mac OS >> X and Windows XP using VS .Net. >> >> I have added support for: >> XMLResource >> ProgressDialog >> Validator >> Icon >> FindReplaceDialog >> >> I have tested the following sample projects successfully: >> caret >> dialogs >> etc >> images >> minimal >> xrc >> >> I am working on getting the controls sample working >> >> After working on this for awhile I think the project should only focus >> on wxWidgets 2.6.1 and beyond. If anyone wants to use wxWidgets 2.4.x >> they can use the old wxRuby 0.6 path. >> >> I also think we should look into getting rid of the >> wxclasses-2.4.2.xml for class and method definitions and do it all >> with *.i. With the *.i files we have more control over conditional >> compilation for the different platforms and libraries that people may >> want to leave out when compiling wxruby. Not to mention it really >> slows down the development process having to parse the XML files >> every-time something is added to extractxml.rb. >> >> Since I can not write back to the CVS repository I am posting my >> changes zipped up to: >> http://www.hailstonesoftware.com/wxruby/wxruby-swig_07_16_2005.zip >> it is 2.71 MB >> >> NOTES: >> - I renamed rake.bat in the root directory to rake2.bat because it >> messed up rake usage on Windows for me. >> - In extconf.rb ENV['WXWIN'] did not work for me so I have $WXDIR hard >> coded for the windows version. >> - Also note I have not used SWIG before so excuse any stupid looking >> mistakes :) >> >> Used: >> SWIG 1.3.24 >> Rake 0.5.3 >> Ruby 1.8.2 >> wxWidgets 2.6.1 >> Windows XP Pro Service pack 2 >> Mac OS X 10.4.2 >> >> Sean Long >> >> >> On 7/16/05, Kevin Smith wrote: >> >>> Roy Sutton wrote (on the FreeRIDE list): >>> >>>> Really? That's interesting. I haven't checked out WxRuby but I would >>>> be much happier using something that interfaces to the underlying >>>> operating system's widgets. >>> >>> >>> As a member (and former leader) of the wxruby team, I thought I would >>> share the state of the wxruby world. >>> >>> The current release is 0.6, and it has pretty good widget support, but >>> has a few stability problems, and some pretty bad memory leaks. We are >>> rewriting wxruby from scratch using swig, which has some significant >>> benefits: >>> - Fixes the leaks and other memory problems >>> - Provides much better support for subclassing wx classes >>> - Makes it easier for non-coders to add support for more classes >>> >>> Unfortunately, none of us on the team have had time to bring wxruby-swig >>> up to the level where it supports all the classes that are in wxruby >>> 0.6. So wxruby-swig has not yet been released. And although we still >>> believe in wxruby, none of us are actively developing it right now. A >>> motivated person could rapidly make a lot of progress, even if they >>> don't know C++. I can offer quick and deep technical support to anyone >>> interested in working on wxruby-swig. >>> >>> Oh...one other issue. We are a bit caught between supporting the >>> upstream wx 2.4 library and the recently-released 2.6 version. So far, >>> we have focused on 2.4, but as time goes by, more and more people would >>> rather have a version that works with 2.6. >>> >>> Kevin >>> _______________________________________________ >>> wxruby-users mailing list >>> wxruby-users@rubyforge.org >>> http://rubyforge.org/mailman/listinfo/wxruby-users >>> >> >> >> _______________________________________________ >> wxruby-users mailing list >> wxruby-users@rubyforge.org >> http://rubyforge.org/mailman/listinfo/wxruby-users > > > _______________________________________________ > wxruby-users mailing list > wxruby-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-users From wxruby at qualitycode.com Mon Jul 18 12:36:26 2005 From: wxruby at qualitycode.com (Kevin Smith) Date: Mon Jul 18 12:31:21 2005 Subject: [Wxruby-users] Re: Progress on wxruby-swig In-Reply-To: References: <42D79938.8090402@xs4all.nl> <42D7BD75.8030708@mindspring.com> <42D8245F.6070801@hibbs.com> <42D83767.6010208@mindspring.com> <42D90C50.4060008@qualitycode.com> <42DAF7DB.7010601@qualitycode.com> <42DB34CD.1090903@qualitycode.com> <42DBA009.1080106@qualitycode.com> Message-ID: <42DBDA8A.2060009@qualitycode.com> Sean Long wrote: > Ok I tried again and got the correct files. It does not compile out of > the box on OS X with wxWidgets 2.6.1 because of: > > void DrawRoundedRectangle(wxCoord x , wxCoord y , wxCoord width , > wxCoord height , double radius = 20) > > which needs to be > > void DrawRoundedRectangle(wxCoord x , wxCoord y , wxCoord width , > wxCoord height , double radius ) Hm. That looks backward to me, but I can't check it right now. > But once we get rid of the XML we can just put #ifdef's in wxDc.h for > wxWidgets 2.4.x, 2.5.x , 2.6.x whatever. Yup. > Before you said you want to target wxWidgets 2.5.x the only problem I > see with that it is no longer easy to find on the wxWidgets site since > it was considered TESTING and 2.6.x is STABLE production quality so > that is what they push. True, but Ubuntu stable (Hoary) only has 2.5, so that's what I personally want to target right now. We can primarily target 2.5 on Linux and 2.6 on Mac and Windows. Hopefully it will work with a broad range of 2.5 - 2.6 anyway. I think the next Ubuntu release is scheduled for August. At the moment, it doesn't have 2.5 or 2.6, but hopefully that will change. > I did get my version without XML working, but will wait on your > version to start implementing new functionality. Ok. Kevin From wxruby at qualitycode.com Mon Jul 18 18:06:00 2005 From: wxruby at qualitycode.com (Kevin Smith) Date: Mon Jul 18 18:00:52 2005 Subject: [Wxruby-users] Progress on wxruby-swig In-Reply-To: <42DB34CD.1090903@qualitycode.com> References: <42D79938.8090402@xs4all.nl> <42D7BD75.8030708@mindspring.com> <42D8245F.6070801@hibbs.com> <42D83767.6010208@mindspring.com> <42D90C50.4060008@qualitycode.com> <42DAF7DB.7010601@qualitycode.com> <42DB34CD.1090903@qualitycode.com> Message-ID: <42DC27C8.3020009@qualitycode.com> Kevin Smith wrote: > My next step (tomorrow, hopefully) will be to officially remove > wxclasses-2.4.2.xml and extractxml from the project. Done. I tagged this as 0.0.19, because my next step is to upgrade my system to wx 2.5, and (probably) break 2.4 compatibility. Perhaps someone can help me figure out a weird situation on my box. My working copy of wxruby-swig seems to be working perfectly...except that it doesn't know about the installers/ directory. cvs update doesn't create it. I tried to copy in Sean's version and check it in, but cvs got all flustered and refused it. Is there something funky about it on the cvs server? Or is my local working copy of wxruby-swig hosed? Kevin From alex at pressure.to Mon Jul 18 19:46:52 2005 From: alex at pressure.to (alex fenton) Date: Mon Jul 18 19:42:38 2005 Subject: [Wxruby-users] Progress on wxruby-swig In-Reply-To: <42DC27C8.3020009@qualitycode.com> References: <42D79938.8090402@xs4all.nl> <42D7BD75.8030708@mindspring.com> <42D8245F.6070801@hibbs.com> <42D83767.6010208@mindspring.com> <42D90C50.4060008@qualitycode.com> <42DAF7DB.7010601@qualitycode.com> <42DB34CD.1090903@qualitycode.com> <42DC27C8.3020009@qualitycode.com> Message-ID: <42DC3F6C.2000708@pressure.to> Kevin Smith wrote: > Perhaps someone can help me figure out a weird situation on my box. My > working copy of wxruby-swig seems to be working perfectly...except that > it doesn't know about the installers/ directory. cvs update doesn't > create it. I tried to copy in Sean's version and check it in, but cvs > got all flustered and refused it. There's something funny going on on the server, I think - I had an existing repository without installers, but cvs up didn't create the dir when I tried to update my sources with your recent check-ins. A new check-out seems to be working OK. Thanks for pushing things forward, Kevin, Sean alex From sean.m.long at gmail.com Mon Jul 18 19:53:35 2005 From: sean.m.long at gmail.com (Sean Long) Date: Mon Jul 18 19:48:39 2005 Subject: [Wxruby-users] Progress on wxruby-swig In-Reply-To: <42DC27C8.3020009@qualitycode.com> References: <42D79938.8090402@xs4all.nl> <42D7BD75.8030708@mindspring.com> <42D8245F.6070801@hibbs.com> <42D83767.6010208@mindspring.com> <42D90C50.4060008@qualitycode.com> <42DAF7DB.7010601@qualitycode.com> <42DB34CD.1090903@qualitycode.com> <42DC27C8.3020009@qualitycode.com> Message-ID: I just did a fresh check out and the installers directory was generated with a sub directory called windows. I probably won't have any time today to test out your changes but hopefully tomorrow I will. Sean Long On 7/18/05, Kevin Smith wrote: > Kevin Smith wrote: > > My next step (tomorrow, hopefully) will be to officially remove > > wxclasses-2.4.2.xml and extractxml from the project. > > Done. > > I tagged this as 0.0.19, because my next step is to upgrade my system to > wx 2.5, and (probably) break 2.4 compatibility. > > Perhaps someone can help me figure out a weird situation on my box. My > working copy of wxruby-swig seems to be working perfectly...except that > it doesn't know about the installers/ directory. cvs update doesn't > create it. I tried to copy in Sean's version and check it in, but cvs > got all flustered and refused it. > > Is there something funky about it on the cvs server? Or is my local > working copy of wxruby-swig hosed? > > Kevin > _______________________________________________ > wxruby-users mailing list > wxruby-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-users > From wxruby at qualitycode.com Tue Jul 19 00:09:48 2005 From: wxruby at qualitycode.com (Kevin Smith) Date: Tue Jul 19 00:04:40 2005 Subject: [Wxruby-users] Progress on wxruby-swig In-Reply-To: <42DC27C8.3020009@qualitycode.com> References: <42D79938.8090402@xs4all.nl> <42D7BD75.8030708@mindspring.com> <42D8245F.6070801@hibbs.com> <42D83767.6010208@mindspring.com> <42D90C50.4060008@qualitycode.com> <42DAF7DB.7010601@qualitycode.com> <42DB34CD.1090903@qualitycode.com> <42DC27C8.3020009@qualitycode.com> Message-ID: <42DC7D0C.5040309@qualitycode.com> Kevin Smith wrote: > I tagged this as 0.0.19, because my next step is to upgrade my system to > wx 2.5, and (probably) break 2.4 compatibility. Ugh. I just spent several hours trying to figure out why minimal.rb would crash immediately. Finally I realized that Ubuntu's wxWidgets 2.5.3 was compiled with UNICODE enabled. Now I have to decide between: a. going back to wx 2.4 (at least for now) b. making it work with wx 2.5.3 unicode c. manually installing wx 2.6 outside the Ubuntu package manager I suspect (b) would be too difficult at this point, although it would be really cool if I could get it working. As much as I dislike bypassing apt/dpkg, I suspect (c) is a better long-term option than (a). Bah. Kevin From wxruby at qualitycode.com Tue Jul 19 00:55:41 2005 From: wxruby at qualitycode.com (Kevin Smith) Date: Tue Jul 19 00:50:26 2005 Subject: [Wxruby-users] I just got wxruby-swig working with unicode! (was: Progress on wxruby-swig) In-Reply-To: <42DC7D0C.5040309@qualitycode.com> References: <42D79938.8090402@xs4all.nl> <42D7BD75.8030708@mindspring.com> <42D8245F.6070801@hibbs.com> <42D83767.6010208@mindspring.com> <42D90C50.4060008@qualitycode.com> <42DAF7DB.7010601@qualitycode.com> <42DB34CD.1090903@qualitycode.com> <42DC27C8.3020009@qualitycode.com> <42DC7D0C.5040309@qualitycode.com> Message-ID: <42DC87CD.1010704@qualitycode.com> Kevin Smith wrote: > Ugh. I just spent several hours trying to figure out why minimal.rb > would crash immediately. Finally I realized that Ubuntu's wxWidgets > 2.5.3 was compiled with UNICODE enabled. > > Now I have to decide between: > > a. going back to wx 2.4 (at least for now) > b. making it work with wx 2.5.3 unicode > c. manually installing wx 2.6 outside the Ubuntu package manager Holy Freakin Smoke! I actually got it working with option (b). I can run minimal and calendar (that's all I've tried) using a unicode build of wxWidgets 2.5.3. Woo-hoo!!! It's already past my bedtime, so I won't check anything in tonight. Within the next day or two, I should be able to check in changes that will allow wxruby-swig to work with unicode or non-unicode builds of wx 2.5 or 2.6. From now on, wxruby-swig will not support wx 2.4, unless someone else steps up to maintain 2.4 compatibility. My current brain-dead approach assumes that all strings passed in from Ruby are UTF-8, and all strings returned to Ruby are also UTF-8. For those of you who aren't familiar with UTF-8, it is a superset of 7-bit ASCII, so plain ASCII text will work fine. It shouldn't be too difficult to support other encodings at run-time. The changes were surprisingly small, thanks to SWIG. Kevin From sean.m.long at gmail.com Tue Jul 19 03:17:53 2005 From: sean.m.long at gmail.com (Sean Long) Date: Tue Jul 19 03:12:55 2005 Subject: [Wxruby-users] I just got wxruby-swig working with unicode! (was: Progress on wxruby-swig) In-Reply-To: <42DC87CD.1010704@qualitycode.com> References: <42D79938.8090402@xs4all.nl> <42D8245F.6070801@hibbs.com> <42D83767.6010208@mindspring.com> <42D90C50.4060008@qualitycode.com> <42DAF7DB.7010601@qualitycode.com> <42DB34CD.1090903@qualitycode.com> <42DC27C8.3020009@qualitycode.com> <42DC7D0C.5040309@qualitycode.com> <42DC87CD.1010704@qualitycode.com> Message-ID: I am glad 2.4 will be dropped and the UTF-8 support sounds cool. Earlier I said I would not have time to try the latest in CVS, well I did have time and hit a few snags. Mostly just little things in a few headers like having default parameters when actually the function does not have defaults, they must have changed a few of these since 2.5.x. The biggest problem I have is with the Xrc.i file, the following: %init %{ extern VALUE mWx; rb_define_module_function(mWx, "xrcid", VALUEFUNC(xrcid), 1); %} Causes this error when linking: /usr/bin/ld: multiple definitions of symbol _Init_wxFunctions Functions.o definition of _Init_wxFunctions in section (__TEXT,__text) Xrc.o definition of _Init_wxFunctions in section (__TEXT,__text) Which makes perfect sense but how can we get around this with SWIG? I could not find anything in the documents like using %extend on %init or _Init_wxFunctions. This is where my lack of experience with SWIG hurts me. Hope you have a slick work around Sean On 7/18/05, Kevin Smith wrote: > Kevin Smith wrote: > > Ugh. I just spent several hours trying to figure out why minimal.rb > > would crash immediately. Finally I realized that Ubuntu's wxWidgets > > 2.5.3 was compiled with UNICODE enabled. > > > > Now I have to decide between: > > > > a. going back to wx 2.4 (at least for now) > > b. making it work with wx 2.5.3 unicode > > c. manually installing wx 2.6 outside the Ubuntu package manager > > Holy Freakin Smoke! I actually got it working with option (b). I can run > minimal and calendar (that's all I've tried) using a unicode build of > wxWidgets 2.5.3. Woo-hoo!!! > > It's already past my bedtime, so I won't check anything in tonight. > Within the next day or two, I should be able to check in changes that > will allow wxruby-swig to work with unicode or non-unicode builds of wx > 2.5 or 2.6. From now on, wxruby-swig will not support wx 2.4, unless > someone else steps up to maintain 2.4 compatibility. > > My current brain-dead approach assumes that all strings passed in from > Ruby are UTF-8, and all strings returned to Ruby are also UTF-8. For > those of you who aren't familiar with UTF-8, it is a superset of 7-bit > ASCII, so plain ASCII text will work fine. It shouldn't be too difficult > to support other encodings at run-time. > > The changes were surprisingly small, thanks to SWIG. > > Kevin > _______________________________________________ > wxruby-users mailing list > wxruby-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-users > From jani at iv.ro Tue Jul 19 05:29:32 2005 From: jani at iv.ro (Jani Monoses) Date: Tue Jul 19 05:25:24 2005 Subject: [Wxruby-users] Re: Progress on wxruby-swig In-Reply-To: <42DBDA8A.2060009@qualitycode.com> References: <42D79938.8090402@xs4all.nl> <42D7BD75.8030708@mindspring.com> <42D8245F.6070801@hibbs.com> <42D83767.6010208@mindspring.com> <42D90C50.4060008@qualitycode.com> <42DAF7DB.7010601@qualitycode.com> <42DB34CD.1090903@qualitycode.com> <42DBA009.1080106@qualitycode.com> <42DBDA8A.2060009@qualitycode.com> Message-ID: > I think the next Ubuntu release is scheduled for August. At the moment, > it doesn't have 2.5 or 2.6, but hopefully that will change. It is scheduled for mid October. Now that it looks that wxruby-swig is going to work with the default wx2.5 in ubuntu/debian I am even more interested in packaging it :) BTW Kevin you still don't like darcs ;) ? It would be nice if there was a wxruby-swig repo of a disconnected SCM, since it seems the number of people interested in contributing is growing Jani From abo at eduard-wulff.de Tue Jul 19 05:39:26 2005 From: abo at eduard-wulff.de (Eduard Wulff) Date: Tue Jul 19 05:34:08 2005 Subject: [Wxruby-users] wx 2.6 on Debian / Ubuntu Message-ID: <42DCCA4E.6020300@eduard-wulff.de> FWIW: http://packages.debian.org/experimental/libs/libwxgtk2.6-0 experimental ... Should work for Ubuntu too. From wxruby at qualitycode.com Tue Jul 19 09:52:40 2005 From: wxruby at qualitycode.com (Kevin Smith) Date: Tue Jul 19 09:47:26 2005 Subject: [Wxruby-users] darcs? (was: Progress on wxruby-swig) In-Reply-To: References: <42D79938.8090402@xs4all.nl> <42D7BD75.8030708@mindspring.com> <42D8245F.6070801@hibbs.com> <42D83767.6010208@mindspring.com> <42D90C50.4060008@qualitycode.com> <42DAF7DB.7010601@qualitycode.com> <42DB34CD.1090903@qualitycode.com> <42DBA009.1080106@qualitycode.com> <42DBDA8A.2060009@qualitycode.com> Message-ID: <42DD05A8.6020108@qualitycode.com> Jani Monoses wrote: > >> I think the next Ubuntu release is scheduled for August. At the >> moment, it doesn't have 2.5 or 2.6, but hopefully that will change. > > It is scheduled for mid October. Now that it looks that wxruby-swig is > going to work with the default wx2.5 in ubuntu/debian I am even more > interested in packaging it :) Thanks for the schedule correction. I sure hope Breezy adds wx 2.5/2.6 before it is released. It would be GREAT if you could package wxruby for Ubuntu, although I also really want to see it as a gem. > BTW Kevin you still don't like darcs ;) ? It would be nice if there was > a wxruby-swig repo of a disconnected SCM, since it seems the number of > people interested in contributing is growing I am still completely committed to eventually using a distributed SCM. My current favorites are ArX[1] and Mercurial[2]. Darcs is a good tool in many ways, but has some attributes I don't like. Same for Monotone, codeville, svk, GNU arch, FastCST, git/cogito, bazaar, bazaar-ng... If my using ArX or Mercurial would increase contributions to wxruby, I might try to start using it, with a gateway to keep the CVS tree updated. Kevin [1] http://www.nongnu.org/arx/ [2] http://www.selenic.com/mercurial/ From wxruby at qualitycode.com Tue Jul 19 10:03:44 2005 From: wxruby at qualitycode.com (Kevin Smith) Date: Tue Jul 19 09:58:26 2005 Subject: [Wxruby-users] I just got wxruby-swig working with unicode! In-Reply-To: References: <42D79938.8090402@xs4all.nl> <42D8245F.6070801@hibbs.com> <42D83767.6010208@mindspring.com> <42D90C50.4060008@qualitycode.com> <42DAF7DB.7010601@qualitycode.com> <42DB34CD.1090903@qualitycode.com> <42DC27C8.3020009@qualitycode.com> <42DC7D0C.5040309@qualitycode.com> <42DC87CD.1010704@qualitycode.com> Message-ID: <42DD0840.7070509@qualitycode.com> Sean Long wrote: > Earlier I said I would not have time to try the latest in CVS, well I > did have time and hit a few snags. Mostly just little things in a few > headers like having default parameters when actually the function does > not have defaults, they must have changed a few of these since 2.5.x. Ok. I will rely on you to help us get to the point where it works with 2.5 and 2.6. It would be perfect for me if you could re-target the rest of your source changes against the current HEAD, and send them to me as patches (or just paste the little .i fixes into an email). > The biggest problem I have is with the Xrc.i file, the following: > %init %{ > extern VALUE mWx; > rb_define_module_function(mWx, "xrcid", VALUEFUNC(xrcid), 1); > %} > > Causes this error when linking: > /usr/bin/ld: multiple definitions of symbol _Init_wxFunctions > Functions.o definition of _Init_wxFunctions in section (__TEXT,__text) > Xrc.o definition of _Init_wxFunctions in section (__TEXT,__text) Actually, that was my mistake. At the top of Xrc.i, it should be: %module(directors="1") wxXrc instead of %module(directors="1") wxFunctions Both Functions and Xrc were creating a "wxFunctions" module, causing the conflict. I have changed this in my local source, but have not yet committed it. Let me know if this change fixes it for you. > Which makes perfect sense but how can we get around this with SWIG? I > could not find anything in the documents like using %extend on %init > or _Init_wxFunctions. > > This is where my lack of experience with SWIG hurts me. Actually, it's a lack of experience with the tricks I had to use in wxRuby to work around SWIG limitations. SWIG really doesn't support having multiple files combined into a single module. The workaround is to SWIG each C++ class as if it were going to end up in a separate module. Then the postprocessing .rb commands mangle the created .cpp files to all be in the same module. Then it's up to us (seen at the bottom of wx.cpp) to initialize all the classes. Thanks again, Kevin From wxruby at qualitycode.com Tue Jul 19 10:07:00 2005 From: wxruby at qualitycode.com (Kevin Smith) Date: Tue Jul 19 10:01:41 2005 Subject: [Wxruby-users] I just got wxruby-swig working with unicode! In-Reply-To: <42DC87CD.1010704@qualitycode.com> References: <42D79938.8090402@xs4all.nl> <42D7BD75.8030708@mindspring.com> <42D8245F.6070801@hibbs.com> <42D83767.6010208@mindspring.com> <42D90C50.4060008@qualitycode.com> <42DAF7DB.7010601@qualitycode.com> <42DB34CD.1090903@qualitycode.com> <42DC27C8.3020009@qualitycode.com> <42DC7D0C.5040309@qualitycode.com> <42DC87CD.1010704@qualitycode.com> Message-ID: <42DD0904.1020304@qualitycode.com> Kevin Smith wrote: > Holy Freakin Smoke! (snip) > I can run minimal and calendar (that's all I've tried) using a unicode > build of wxWidgets 2.5.3. Woo-hoo!!! Just a couple other notes on this: 1. My wxWidgets is also built to use GTK2, and I immediately noticed that the apps look more attractive than they did with wx 2.4 and GTK1. 2. The unicode support I built in should also work fine with non-unicode builds of wx, as long as wxruby is built with wx headers that match the wx library that it will run with. I guess that means we'll eventually need to ship two wxruby binaries--one for unicode wx, and the other not. I'm not sure about that, though. There might be a way to work with both entirely at runtime. Kevin From wxruby at qualitycode.com Tue Jul 19 10:14:19 2005 From: wxruby at qualitycode.com (Kevin Smith) Date: Tue Jul 19 10:08:59 2005 Subject: [Wxruby-users] wx 2.6 on Debian / Ubuntu In-Reply-To: <42DCCA4E.6020300@eduard-wulff.de> References: <42DCCA4E.6020300@eduard-wulff.de> Message-ID: <42DD0ABB.4060702@qualitycode.com> Eduard Wulff wrote: > FWIW: > http://packages.debian.org/experimental/libs/libwxgtk2.6-0 Cool. > > experimental ... > > Should work for Ubuntu too. Unfortunately not for Ubuntu stable (Hoary), which I'm running :-( Because it has this dependency: libc6 (>= 2.3.2.ds1-21) [not ia64] GNU C Library: Shared libraries and Timezone data and Ubuntu Hoary only has libc6 2.3.2.ds1-20ubuntu13. But it looks like it should work with the upcoming Ubuntu release (Breezy) which has libc6 2.3.5-1ubuntu7. Given that it is only in Debian experimental, is wx 2.6 likely to end up in Ubuntu Breezy in October? If not, I sure hope they put wx 2.5 back in. Thanks, Kevin From jani at iv.ro Tue Jul 19 10:35:32 2005 From: jani at iv.ro (Jani Monoses) Date: Tue Jul 19 10:35:35 2005 Subject: [Wxruby-users] Re: wx 2.6 on Debian / Ubuntu In-Reply-To: <42DD0ABB.4060702@qualitycode.com> References: <42DCCA4E.6020300@eduard-wulff.de> <42DD0ABB.4060702@qualitycode.com> Message-ID: > > Unfortunately not for Ubuntu stable (Hoary), which I'm running :-( > > Because it has this dependency: > libc6 (>= 2.3.2.ds1-21) [not ia64] > GNU C Library: Shared libraries and Timezone data > > and Ubuntu Hoary only has libc6 2.3.2.ds1-20ubuntu13. maybe using dpkg --ignore-depends or some other --force options could help if that fails a .deb is an ar archive.So you can ar x it, modify the CONTROL file in control.tar.gz so that the Depends line lists the required glibc version then rearchive using ar in the same order debian-binary control.tar.gz data.tar.gz to a new .deb file and dpkg install it while crossing fingers :) > But it looks like it should work with the upcoming Ubuntu release > (Breezy) which has libc6 2.3.5-1ubuntu7. > > Given that it is only in Debian experimental, is wx 2.6 likely to end up > in Ubuntu Breezy in October? If not, I sure hope they put wx 2.5 back in. I don't know about 2.6 since breezy has already entered upstream freeze but libwxgtk2.5.3 is in on my systme at least. Jani From jani at iv.ro Tue Jul 19 11:44:04 2005 From: jani at iv.ro (Jani Monoses) Date: Tue Jul 19 11:40:01 2005 Subject: [Wxruby-users] Re: I just got wxruby-swig working with unicode! In-Reply-To: <42DC87CD.1010704@qualitycode.com> References: <42D79938.8090402@xs4all.nl> <42D7BD75.8030708@mindspring.com> <42D8245F.6070801@hibbs.com> <42D83767.6010208@mindspring.com> <42D90C50.4060008@qualitycode.com> <42DAF7DB.7010601@qualitycode.com> <42DB34CD.1090903@qualitycode.com> <42DC27C8.3020009@qualitycode.com> <42DC7D0C.5040309@qualitycode.com> <42DC87CD.1010704@qualitycode.com> Message-ID: > Holy Freakin Smoke! I actually got it working with option (b). I can run > minimal and calendar (that's all I've tried) using a unicode build of > wxWidgets 2.5.3. Woo-hoo!!! CVS HEAD still doesn't build here with either g++ 3.4 or 4.0.1. I wonder if something particular needs to be set. src/TextCtrl.cpp: In function `VALUE _wrap_wxTextCtrl___lshift____SWIG_0(int, VALUE*, VALUE)': src/TextCtrl.cpp:2066: error: call of overloaded `operator<<(const char*)' is ambiguous /usr/include/wx-2.5/wx/textctrl.h:375: note: candidates are: wxTextCtrl& wxTextCtrlBase::operator<<(const wxString&) /usr/include/wx-2.5/wx/textctrl.h:376: note: wxTextCtrl& wxTextCtrlBase::operator<<(int) /usr/include/wx-2.5/wx/textctrl.h:377: note: wxTextCtrl& wxTextCtrlBase::operator<<(long int) /usr/include/wx-2.5/wx/textctrl.h:380: note: wxTextCtrl& wxTextCtrlBase::operator<<(wxChar) other than that almost every file has these two warnings src/StaticBoxSizer.cpp:529: warning: 'alive' defined but not used src/StaticBoxSizer.cpp:535: warning: 'void SWIG_AsVal(VALUE, int*)' defined but not used Jani From curt at hibbs.com Tue Jul 19 12:01:57 2005 From: curt at hibbs.com (Curt Hibbs) Date: Tue Jul 19 11:56:39 2005 Subject: [Wxruby-users] Hello, new developer here. (for Bryan Green) Message-ID: <42DD23F5.6070501@hibbs.com> Bryan Green has subscribed to the ML, but is getting his postings rejected. I'm forward his post to the list for you to read, and as a test to see if I also get an error. Bryan: Can you send me the actual error/rejection-notice you are getting? Anyway, here's Bryan's message: Greetings to everyone! I have been pointed to this project from the Freeride project. I have checked out the wxruby-swig (as anonymous, don't have developer access) source and have started looking over it. Just wanted to drop a line and say hello. I am a very experienced C/C++ programmer (other languages, also). I have a lot of experience developing for Linux and Windows. I have some swig experience with python. From wxruby at qualitycode.com Tue Jul 19 12:04:06 2005 From: wxruby at qualitycode.com (Kevin Smith) Date: Tue Jul 19 11:59:07 2005 Subject: [Wxruby-users] Re: I just got wxruby-swig working with unicode! In-Reply-To: References: <42D79938.8090402@xs4all.nl> <42D7BD75.8030708@mindspring.com> <42D8245F.6070801@hibbs.com> <42D83767.6010208@mindspring.com> <42D90C50.4060008@qualitycode.com> <42DAF7DB.7010601@qualitycode.com> <42DB34CD.1090903@qualitycode.com> <42DC27C8.3020009@qualitycode.com> <42DC7D0C.5040309@qualitycode.com> <42DC87CD.1010704@qualitycode.com> Message-ID: <42DD2476.1010501@qualitycode.com> Jani Monoses wrote: > > CVS HEAD still doesn't build here with either g++ 3.4 or 4.0.1. I wonder > if something > particular needs to be set. > > src/TextCtrl.cpp: In function `VALUE > _wrap_wxTextCtrl___lshift____SWIG_0(int, VALUE*, VALUE)': > src/TextCtrl.cpp:2066: error: call of overloaded `operator<<(const Thanks for the report, and sorry about that. I had tweaked TextCtrl.i but not checked it in. I have committed it now. > other than that almost every file has these two warnings > > src/StaticBoxSizer.cpp:529: warning: 'alive' defined but not used I also just checked in a fix to eliminate that. > src/StaticBoxSizer.cpp:535: warning: 'void SWIG_AsVal(VALUE, int*)' > defined but not used I couldn't see an obvious place where this was being generated, so it will still be a problem. Also, I checked in the Xrc.i fix that I mentioned earlier, so hopefully (fingers crossed) it will build if you set WXRUBY_XRC=YES in your environment. However, since xrc is part of wx 2.5+, I will be removing that environment setting shortly, and always including xrc. Cheers, Kevin From jani at iv.ro Tue Jul 19 12:14:59 2005 From: jani at iv.ro (Jani Monoses) Date: Tue Jul 19 12:10:50 2005 Subject: [Wxruby-users] Re: I just got wxruby-swig working with unicode! In-Reply-To: <42DD2476.1010501@qualitycode.com> References: <42D79938.8090402@xs4all.nl> <42D7BD75.8030708@mindspring.com> <42D8245F.6070801@hibbs.com> <42D83767.6010208@mindspring.com> <42D90C50.4060008@qualitycode.com> <42DAF7DB.7010601@qualitycode.com> <42DB34CD.1090903@qualitycode.com> <42DC27C8.3020009@qualitycode.com> <42DC7D0C.5040309@qualitycode.com> <42DC87CD.1010704@qualitycode.com> <42DD2476.1010501@qualitycode.com> Message-ID: > Thanks for the report, and sorry about that. I had tweaked TextCtrl.i > but not checked it in. I have committed it now. Still the .cpp is the same. If I understand correctly you generate the .cpp files locally from the .i files and commit them too? CVS up just gave the 3 modifications you mentioned. And I do not run SWIG myself, should I? >> other than that almost every file has these two warnings >> >> src/StaticBoxSizer.cpp:529: warning: 'alive' defined but not used Still there probably because of the same reason. thanks Jani From wxruby at qualitycode.com Tue Jul 19 13:35:34 2005 From: wxruby at qualitycode.com (Kevin Smith) Date: Tue Jul 19 13:30:19 2005 Subject: [Wxruby-users] Re: I just got wxruby-swig working with unicode! In-Reply-To: References: <42D79938.8090402@xs4all.nl> <42D7BD75.8030708@mindspring.com> <42D8245F.6070801@hibbs.com> <42D83767.6010208@mindspring.com> <42D90C50.4060008@qualitycode.com> <42DAF7DB.7010601@qualitycode.com> <42DB34CD.1090903@qualitycode.com> <42DC27C8.3020009@qualitycode.com> <42DC7D0C.5040309@qualitycode.com> <42DC87CD.1010704@qualitycode.com> <42DD2476.1010501@qualitycode.com> Message-ID: <42DD39E6.3020808@qualitycode.com> Jani Monoses wrote: > Still the .cpp is the same. If I understand correctly you generate the > .cpp files locally from the .i files and commit them too? CVS up just > gave the 3 modifications you mentioned. > And I do not run SWIG myself, should I? You should not have to run SWIG yourself, although if you want to contribute code you will need to eventually. I just checked in EVERYTHING in my tree, so the HEAD should now have the fixed TextCtrl.cpp that works with 2.5, and it should avoid the "alive" warning, and it includes my unicode work. Sorry for all the mess caused by my partial commits. I thought I was being safer not checking in my hacky unicode stuff last night, but I think I actually made things worse for you :-( Anyway, what's in the head now is what swigs, compiles, and runs for me with wx 2.5.3 unicode. I definitely want to hear any problem reports. Thanks again, Kevin From wxruby at qualitycode.com Tue Jul 19 21:04:16 2005 From: wxruby at qualitycode.com (Kevin Smith) Date: Tue Jul 19 20:59:02 2005 Subject: [Wxruby-users] More wxruby-swig changes Message-ID: <42DDA310.8070504@qualitycode.com> I just checked in several changes from Sean Long that should make wxruby-swig work with wx 2.6 as well as 2.5. I also committed his changes to extconf.rb. But could someone please explain to me why anyone would prefer to use extconf.rb instead of rake? It just seems like one more piece of code to maintain, and I don't like extra code. Sean: The other diffs in the patch you sent were all due to changes I checked in recently that weren't in your baseline. As far as I know, I have incorporated all the changes you have sent me so far. You have also added some classes and samples, right? Can you send those as patches too? Next up for me: Make xrc non-optional, and try to figure out how to get rid of the WXRUBY_SWIG environment variable by just detecting whether or not SWIG is available. Thanks much, Kevin From alex at pressure.to Tue Jul 19 21:24:27 2005 From: alex at pressure.to (alex fenton) Date: Tue Jul 19 21:20:22 2005 Subject: [Wxruby-users] More wxruby-swig changes In-Reply-To: <42DDA310.8070504@qualitycode.com> References: <42DDA310.8070504@qualitycode.com> Message-ID: <42DDA7CB.9090805@pressure.to> > I also committed his changes to extconf.rb. But could someone please > explain to me why anyone would prefer to use extconf.rb instead of rake? > It just seems like one more piece of code to maintain, and I don't like > extra code. I much prefer Rake too. It's either bundled or easy-to-install these days, so reducing the argument for extconf.rb as a standalone. It may be worth looking at the install stage (OS X only) of the Rakefile if dumping extconf.rb: http://rubyforge.org/pipermail/wxruby-users/2005-February/001166.html Also I don't know how well Rakefiles play with Rubygems - but the manual entry seems to suggest it's possible. http://docs.rubygems.org/read/chapter/20#extensions I can look at these latter two once your work's stabilised and i have my laptop back a From wxruby at qualitycode.com Wed Jul 20 00:41:56 2005 From: wxruby at qualitycode.com (Kevin Smith) Date: Wed Jul 20 00:36:45 2005 Subject: [Wxruby-users] Plans to rename wxruby-swig to wxruby2 Message-ID: <42DDD614.2040503@qualitycode.com> Greetings all, Over the last few months, while I have been busy on other projects, Nick and other folks have built wxruby-swig up to where it now supports about 120 classes, compared to the 139 in wxruby 0.6. When you include the fact that wxruby 0.6 had a few classes that really weren't needed (because non-wx ruby versions work fine), it looks like wxruby-swig is actually very close to wxruby 0.6 in terms of functionality. And remember, it is actually far better in terms of memory leakage, and in the number of methods within each class that are fully supported. Great job guys!!! I had no idea so many classes were supported, since nobody had updated the README which still claimed only about 20 classes were being included. We have had an ongoing debate about what to call wxruby-swig. I now have a concrete proposal that I plan to implement soon unless someone raises objections: 1. The new swig-based library will officially be named wxruby2. This will be used as the CVS module name, the gem name, the name for any packaging (e.g. Debian, RPM), and in most documentation. The version numbers will start with 2.0.0-preX, moving to 2.0.0-rcX, and then 2.0.0 proper. Of course, our rubyforge project will remain simply 'wxruby'. 2. The actual binary will also be named wxruby2.dll/wxruby2.so, to avoid conflicting with legacy wxruby binaries. 3. The package will include a wx.rb file which will act as a naming bridge. Ruby apps that want to use wxruby2 will require 'wx', as they currently do with wxruby-swig. wx.rb will in turn require 'wxruby2'. We really don't want to create a ruby-specific binary named wx.dll or wx.so, but it seems needlessly painful to make our users directly require 'wxruby2' in their apps. 4. This wx.rb file will also be a handy place to create pure ruby api sugar. Eventually, one of the ways wxruby can really be valuable is to provide an API that is more rubyish, and coding wrappers in ruby is far easier than doing so in C++. Eventually, some of those wrappers could be ported to C++ for speed, if necessary. My goal is to release a beta version of wxruby2 within a few weeks. Kevin From wxruby at qualitycode.com Wed Jul 20 00:50:14 2005 From: wxruby at qualitycode.com (Kevin Smith) Date: Wed Jul 20 00:44:56 2005 Subject: [Wxruby-users] Plans to rename wxruby-swig to wxruby2 In-Reply-To: <42DDD614.2040503@qualitycode.com> References: <42DDD614.2040503@qualitycode.com> Message-ID: <42DDD806.7050901@qualitycode.com> Kevin Smith wrote: > > My goal is to release a beta version of wxruby2 within a few weeks. Quick reminder: If you want to play around with wxruby-swig, but don't want to deal with CVS, you can download a daily(?) snapshot tarball from this rubyforge page: http://rubyforge.org/cgi-bin/viewcvs.cgi/wxruby-swig/?cvsroot=wxruby Click on the "download tarball" link at the lower left. Kevin From curt at hibbs.com Wed Jul 20 09:09:09 2005 From: curt at hibbs.com (Curt Hibbs) Date: Wed Jul 20 09:03:55 2005 Subject: [Wxruby-users] Plans to rename wxruby-swig to wxruby2 In-Reply-To: <42DDD614.2040503@qualitycode.com> References: <42DDD614.2040503@qualitycode.com> Message-ID: <42DE4CF5.4000206@hibbs.com> Kevin, I'm really glad to see you've got the time and energy to jump back in to wxRuby development. You accomplished much goodness in only a few days! I like the idea of moving to a wxRuby2 name. Besides being a proper reflection of the project, I think having a 2.x version number will have a positive psychological effect on potential users. Curt Kevin Smith wrote: > Greetings all, > > Over the last few months, while I have been busy on other projects, Nick > and other folks have built wxruby-swig up to where it now supports about > 120 classes, compared to the 139 in wxruby 0.6. When you include the > fact that wxruby 0.6 had a few classes that really weren't needed > (because non-wx ruby versions work fine), it looks like wxruby-swig is > actually very close to wxruby 0.6 in terms of functionality. And > remember, it is actually far better in terms of memory leakage, and in > the number of methods within each class that are fully supported. > > Great job guys!!! I had no idea so many classes were supported, since > nobody had updated the README which still claimed only about 20 classes > were being included. > > We have had an ongoing debate about what to call wxruby-swig. I now have > a concrete proposal that I plan to implement soon unless someone raises > objections: > > 1. The new swig-based library will officially be named wxruby2. This > will be used as the CVS module name, the gem name, the name for any > packaging (e.g. Debian, RPM), and in most documentation. The version > numbers will start with 2.0.0-preX, moving to 2.0.0-rcX, and then 2.0.0 > proper. Of course, our rubyforge project will remain simply 'wxruby'. > > 2. The actual binary will also be named wxruby2.dll/wxruby2.so, to avoid > conflicting with legacy wxruby binaries. > > 3. The package will include a wx.rb file which will act as a naming > bridge. Ruby apps that want to use wxruby2 will require 'wx', as they > currently do with wxruby-swig. wx.rb will in turn require 'wxruby2'. We > really don't want to create a ruby-specific binary named wx.dll or > wx.so, but it seems needlessly painful to make our users directly > require 'wxruby2' in their apps. > > 4. This wx.rb file will also be a handy place to create pure ruby api > sugar. Eventually, one of the ways wxruby can really be valuable is to > provide an API that is more rubyish, and coding wrappers in ruby is far > easier than doing so in C++. Eventually, some of those wrappers could be > ported to C++ for speed, if necessary. > > My goal is to release a beta version of wxruby2 within a few weeks. > > Kevin > _______________________________________________ > wxruby-users mailing list > wxruby-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-users > > From jani at iv.ro Wed Jul 20 09:23:52 2005 From: jani at iv.ro (Jani Monoses) Date: Wed Jul 20 09:21:18 2005 Subject: [Wxruby-users] Re: I just got wxruby-swig working with unicode! In-Reply-To: <42DD39E6.3020808@qualitycode.com> References: <42D79938.8090402@xs4all.nl> <42D7BD75.8030708@mindspring.com> <42D8245F.6070801@hibbs.com> <42D83767.6010208@mindspring.com> <42D90C50.4060008@qualitycode.com> <42DAF7DB.7010601@qualitycode.com> <42DB34CD.1090903@qualitycode.com> <42DC27C8.3020009@qualitycode.com> <42DC7D0C.5040309@qualitycode.com> <42DC87CD.1010704@qualitycode.com> <42DD2476.1010501@qualitycode.com> <42DD39E6.3020808@qualitycode.com> Message-ID: > Anyway, what's in the head now is what swigs, compiles, and runs for me > with wx 2.5.3 unicode. I definitely want to hear any problem reports. Great, it works here too. samples/etc/choice.rb and samples/dialogs/dialogs.rb (select log in the file menu) still give (wxruby:32194): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text() and no text is shown, some more areas need to be UTF8-ized? while samples/controls/controls.rb crashes in TextCtrl.new(), something to do with arguments not being valid. I started looking in the sources but it's still intimidating to try and track these down :) thanks Jani From sean.m.long at gmail.com Wed Jul 20 11:11:09 2005 From: sean.m.long at gmail.com (Sean Long) Date: Wed Jul 20 11:06:10 2005 Subject: [Wxruby-users] More wxruby-swig changes In-Reply-To: <42DDA310.8070504@qualitycode.com> References: <42DDA310.8070504@qualitycode.com> Message-ID: > Sean: The other diffs in the patch you sent were all due to changes I > checked in recently that weren't in your baseline. As far as I know, I > have incorporated all the changes you have sent me so far. You have also > added some classes and samples, right? Can you send those as patches too? I am attaching a small patch and the missing files, the xrc.zip is for the samples/ folder. Sean -------------- next part -------------- A non-text attachment was scrubbed... Name: diff.list Type: application/octet-stream Size: 8191 bytes Desc: not available Url : http://rubyforge.org/pipermail/wxruby-users/attachments/20050720/8919ca01/diff-0001.obj -------------- next part -------------- A non-text attachment was scrubbed... Name: xrc.zip Type: application/zip Size: 1867 bytes Desc: not available Url : http://rubyforge.org/pipermail/wxruby-users/attachments/20050720/8919ca01/xrc-0001.zip -------------- next part -------------- A non-text attachment was scrubbed... Name: ProgressDialog.i Type: application/octet-stream Size: 256 bytes Desc: not available Url : http://rubyforge.org/pipermail/wxruby-users/attachments/20050720/8919ca01/ProgressDialog-0001.obj From alex at pressure.to Wed Jul 20 17:18:57 2005 From: alex at pressure.to (Alex Fenton) Date: Wed Jul 20 17:13:43 2005 Subject: [Wxruby-users] wxr2 build error CVS HEAD on OS x Message-ID: <42DEBFC1.7050903@pressure.to> Hi I'm getting a build error with the current cvs HEAD of wxruby-swig. Perh something to do with the unicode changes? OS X 10.3 WxMAC 2.6.0 ruby 1.8.2 thanks alex g++ -c -I/usr/local/lib/wx/include/mac-ansi-release-static-2.6 -I/usr/local/include/wx-2.6 -D__WXMAC__ -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -DNO_GCC_PRAGMA -O2 -fno-common -pipe -fno-common -x objective-c++ -I /Applications/Emacs.app/Contents/Resources/lib/ruby/site_ruby -I /usr/local/lib/ruby/site_ruby/1.8 -I /usr/local/lib/ruby/site_ruby/1.8/powerpc-darwin7.5.0 -I /usr/local/lib/ruby/site_ruby -I /usr/local/lib/ruby/1.8 -I /usr/local/lib/ruby/1.8/powerpc-darwin7.5.0 -I . -o obj/FileDialog.o src/FileDialog.cpp src/FileDialog.cpp: In function `VALUE _wrap_wxFileDialog_GetFilenames(int, VALUE*, long unsigned int)': src/FileDialog.cpp:923: error: conversion from `const wxWCharBuffer' to non-scalar type `wxString' requested src/FileDialog.cpp: In function `VALUE _wrap_wxFileDialog_GetPaths(int, VALUE*, long unsigned int)': src/FileDialog.cpp:1007: error: conversion from `const wxWCharBuffer' to non-scalar type `wxString' requested rake aborted! From sean.m.long at gmail.com Wed Jul 20 18:30:16 2005 From: sean.m.long at gmail.com (Sean Long) Date: Wed Jul 20 18:25:15 2005 Subject: [Wxruby-users] wxr2 build error CVS HEAD on OS x In-Reply-To: <42DEBFC1.7050903@pressure.to> References: <42DEBFC1.7050903@pressure.to> Message-ID: Those look like the errors I was getting, apply the patch I sent earlier today in the message 'More wxruby-swig changes' and you should be able to compile correctly. I use OS X 10.4 and wx 2.6.1 but I bet it will work. Or you can just wait for Kevin to apply the patch to HEAD. Sean On 7/20/05, Alex Fenton wrote: > Hi > > I'm getting a build error with the current cvs HEAD of wxruby-swig. Perh > something to do with the unicode changes? > > OS X 10.3 > WxMAC 2.6.0 > ruby 1.8.2 > > thanks > alex > > g++ -c -I/usr/local/lib/wx/include/mac-ansi-release-static-2.6 > -I/usr/local/include/wx-2.6 -D__WXMAC__ -D_FILE_OFFSET_BITS=64 > -D_LARGE_FILES -DNO_GCC_PRAGMA -O2 -fno-common -pipe -fno-common -x > objective-c++ -I > /Applications/Emacs.app/Contents/Resources/lib/ruby/site_ruby -I > /usr/local/lib/ruby/site_ruby/1.8 -I > /usr/local/lib/ruby/site_ruby/1.8/powerpc-darwin7.5.0 -I > /usr/local/lib/ruby/site_ruby -I /usr/local/lib/ruby/1.8 -I > /usr/local/lib/ruby/1.8/powerpc-darwin7.5.0 -I . -o obj/FileDialog.o > src/FileDialog.cpp > src/FileDialog.cpp: In function `VALUE _wrap_wxFileDialog_GetFilenames(int, > VALUE*, long unsigned int)': > src/FileDialog.cpp:923: error: conversion from `const wxWCharBuffer' to > non-scalar type `wxString' requested > src/FileDialog.cpp: In function `VALUE _wrap_wxFileDialog_GetPaths(int, > VALUE*, > long unsigned int)': > src/FileDialog.cpp:1007: error: conversion from `const wxWCharBuffer' to > non-scalar type `wxString' requested > rake aborted! > _______________________________________________ > wxruby-users mailing list > wxruby-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-users > From alex at pressure.to Wed Jul 20 18:41:27 2005 From: alex at pressure.to (Alex Fenton) Date: Wed Jul 20 18:36:19 2005 Subject: [Wxruby-users] Wxruby2 gemspec Message-ID: <42DED317.6050508@pressure.to> Hi A gemspec for installation of wxuby-swig via rubygems. It assumes the end-users will compile the pre-swigged .cpp files & that that the main require file will be wx.rb (as per Kevin's suggestion). runrake.rb is just a helper script that runs rake correctly within the rubygems installation process. # to build the gem gem build wxruby2.gemspec # to build & install the built gem gem install wxruby2 will do a win32 gem once binaries are available for a release. cheers alex -------------- next part -------------- # For use by rubygems; a simple script that runs WxRuby2 Rakefile's compile # sequence automatically begin require 'rake' rescue LoadError require 'rubygems' require_gem 'rake' end begin rake = RakeApp.new() rake.load_rakefile() Task['compile'].invoke rescue Exception => ex puts "rake aborted!" puts ex.message puts ex.backtrace.find {|str| str =~ /#{@rakefile}/ } || "" exit(1) end -------------- next part -------------- require 'rubygems' require 'rake' WXRUBY2_GEMSPEC = Gem::Specification.new do | s | s.name = 'wxruby2' s.version = '0.20' s.summary = "Ruby interface to the WxWidgets GUI library" s.description = <<-DESC WxRuby provides an interface to the WxWidgets library. It enables the creation of GUI applications with native widgets on platforms including Windows, OS X and Linux. DESC s.author = "WxRuby development team" s.email = "wxruby-users@rubyforge.org" s.homepage = "http://wxruby.rubyforge.org/" s.rubyforge_project = "wxruby" s.files = FileList[ 'src/*' ].to_a + FileList[ 'rake/*' ].to_a + %w[Rakefile] s.autorequire = 'wx' s.require_path = 'lib' s.extensions << 'runrake.rb' s.has_rdoc = false s.add_dependency('rake' => '>= 0.5.0') end From wxruby at qualitycode.com Thu Jul 21 08:45:37 2005 From: wxruby at qualitycode.com (Kevin Smith) Date: Thu Jul 21 08:40:24 2005 Subject: [Wxruby-users] Moving to wx 2.6 (was: More wxruby-swig changes) In-Reply-To: References: <42DDA310.8070504@qualitycode.com> Message-ID: <42DF98F1.2080808@qualitycode.com> Sean Long wrote: > I am attaching a small patch and the missing files, the xrc.zip is for > the samples/ folder. I tried to apply these last night, but encountered several problems that seem to be due to changes between wx 2.5 and 2.6. I can't think of a clean way to support both, so I plan to upgrade myself to 2.6 and then change wxruby2 to only support that version. However, I definitely do not want to impose a binary dependency on wx 2.6 since it is not available for Ubuntu (and perhaps others). For this reason and others (e.g. unicode support), I plan to link wx statically into wxruby2, at least on Linux. It probably makes sense on other platforms, but I'm not in a good position to decide that. I do not plan to support dynamic linking at all for Linux, and suggest the same for other platforms, to keep everything as simple as possible. I will upgrade my system to 2.6, and then will apply Sean's latest changes. After that, I plan to begin the naming changes to wxruby2. However, this is a busy week for me, so I'll probably only have a little time each day to make a little progress. Kevin From wxruby at qualitycode.com Thu Jul 21 08:50:57 2005 From: wxruby at qualitycode.com (Kevin Smith) Date: Thu Jul 21 08:45:38 2005 Subject: [Wxruby-users] Re: I just got wxruby-swig working with unicode! In-Reply-To: References: <42D79938.8090402@xs4all.nl> <42D7BD75.8030708@mindspring.com> <42D8245F.6070801@hibbs.com> <42D83767.6010208@mindspring.com> <42D90C50.4060008@qualitycode.com> <42DAF7DB.7010601@qualitycode.com> <42DB34CD.1090903@qualitycode.com> <42DC27C8.3020009@qualitycode.com> <42DC7D0C.5040309@qualitycode.com> <42DC87CD.1010704@qualitycode.com> <42DD2476.1010501@qualitycode.com> <42DD39E6.3020808@qualitycode.com> Message-ID: <42DF9A31.70302@qualitycode.com> Jani Monoses wrote: > > samples/etc/choice.rb and samples/dialogs/dialogs.rb (select log in the > file menu) still give > > (wxruby:32194): Pango-WARNING **: Invalid UTF-8 string passed to > pango_layout_set_text() > > and no text is shown, some more areas need to be UTF8-ized? I see the same thing here, but won't touch it until after I get wx 2.6 working on my system. Probably something needs to be added to swig/typemaps.i. If you can at least track down what ruby statement is triggering these warnings, it would help. > while samples/controls/controls.rb crashes in TextCtrl.new(), something > to do with arguments not being valid. If you look in src/TextCtrl.cpp, you'll see a constructor wrapper that chooses which C++ constructor to invoke, based on the number and types of the ruby parameters passed in. If you could insert printf's in this constructor, you can probably identify why it is falling through to the end without finding any match. It could be a problem with the ruby code, or with the wxTextCtrl.h api file. Typically with other classes that have had similar problems, I have added a %ignore to the .i file to eliminate all but one constructor. That's not the right long-term solution, but it has gotten several classes to work. > I started looking in the sources but it's still intimidating to try and > track these down :) Yup. Hopefully with the information above you can make an attempt. If not, I'll get back to it in a few days. Thanks, Kevin From jani at iv.ro Thu Jul 21 09:22:56 2005 From: jani at iv.ro (Jani Monoses) Date: Thu Jul 21 10:00:16 2005 Subject: [Wxruby-users] Re: I just got wxruby-swig working with unicode! In-Reply-To: <42DF9A31.70302@qualitycode.com> References: <42D79938.8090402@xs4all.nl> <42D7BD75.8030708@mindspring.com> <42D8245F.6070801@hibbs.com> <42D83767.6010208@mindspring.com> <42D90C50.4060008@qualitycode.com> <42DAF7DB.7010601@qualitycode.com> <42DB34CD.1090903@qualitycode.com> <42DC27C8.3020009@qualitycode.com> <42DC7D0C.5040309@qualitycode.com> <42DC87CD.1010704@qualitycode.com> <42DD2476.1010501@qualitycode.com> <42DD39E6.3020808@qualitycode.com> <42DF9A31.70302@qualitycode.com> Message-ID: Kevin Smith wrote: > Jani Monoses wrote: > >> >> samples/etc/choice.rb and samples/dialogs/dialogs.rb (select log in >> the file menu) still give >> >> (wxruby:32194): Pango-WARNING **: Invalid UTF-8 string passed to >> pango_layout_set_text() >> >> and no text is shown, some more areas need to be UTF8-ized? > > > I see the same thing here, but won't touch it until after I get wx 2.6 > working on my system. Probably something needs to be added to > swig/typemaps.i. If you can at least track down what ruby statement is > triggering these warnings, it would help. I haven't looked at this back then , but I might this weekend. >> while samples/controls/controls.rb crashes in TextCtrl.new(), >> something to do with arguments not being valid. > > > If you look in src/TextCtrl.cpp, you'll see a constructor wrapper that > chooses which C++ constructor to invoke, based on the number and types > of the ruby parameters passed in. If you could insert printf's in this > constructor, you can probably identify why it is falling through to the > end without finding any match. I actually inserted printfs there and modified the TextcCtrl.new() invocation in ruby so it bailed out at different stages of that large if() statement But what I could not figure out is what types ans how many args that initializer must have t behave correctly. But it probably has to do with the fact you mention that you only allowed one type of constructor and the ruby code used another one. Jani From Bryan.Green at acxiom.com Thu Jul 21 11:57:31 2005 From: Bryan.Green at acxiom.com (Green Bryan - bgreen) Date: Thu Jul 21 11:52:18 2005 Subject: [Wxruby-users] RE: Let's see if I can post Message-ID: Checking again. ________________________________ From: Green Bryan - bgreen Sent: Wednesday, July 20, 2005 8:49 AM To: wxruby-users@rubyforge.org Subject: Let's see if I can post Hello, New user trying to see if I can post. Bryan Green ********************************************************************** The information contained in this communication is confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message or any copy of it from your computer system. Thank You. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wxruby-users/attachments/20050721/7ed37c6b/attachment.htm From robin-lists-wxruby-users at nibor.org Sun Jul 24 15:12:50 2005 From: robin-lists-wxruby-users at nibor.org (Robin Stocker) Date: Sun Jul 24 15:07:24 2005 Subject: [Wxruby-users] Wxruby2 gemspec In-Reply-To: <42DED317.6050508@pressure.to> References: <42DED317.6050508@pressure.to> Message-ID: <42E3E832.9020000@nibor.org> Alex Fenton wrote: > WXRUBY2_GEMSPEC = Gem::Specification.new do | s | > s.name = 'wxruby2' > s.version = '0.20' Hi, Is there a reason for not using the rubygems versioning policy? http://docs.rubygems.org/read/chapter/7 I'm just curious. Robin From jani.monoses at gmail.com Sun Jul 24 15:43:06 2005 From: jani.monoses at gmail.com (Jani Monoses) Date: Sun Jul 24 15:37:32 2005 Subject: [Wxruby-users] Fwd: fix Choice.cpp unicode string In-Reply-To: <29e1155305072412281ab845ff@mail.gmail.com> References: <29e1155305072412281ab845ff@mail.gmail.com> Message-ID: <29e11553050724124322e2434a@mail.gmail.com> This is needed so that samples/etc/choice.rb shows the strings in the choice box. One of the few places that missed UTF8 convertion. --- swig/classes/Choice.i 31 Jan 2005 04:18:52 -0000 1.2 +++ swig/classes/Choice.i 24 Jul 2005 19:18:55 -0000 @@ -14,7 +14,7 @@ for(int i=0; i < $1; ++i) { VALUE thisItem = rb_ary_entry($input, i); - $2[i] = (wxChar *)STR2CSTR(thisItem); + $2[i] = wxConvUTF8.cMB2WC(STR2CSTR(thisItem)); } } There's another I think UTF8 problem: The onAbout dialog in caret.rb uses the (c) character so the string is not shown. Jani From usrlocalinfo at yahoo.com Sun Jul 24 16:57:17 2005 From: usrlocalinfo at yahoo.com (DJB) Date: Sun Jul 24 16:52:36 2005 Subject: [Wxruby-users] Re: Plans to rename wxruby-swig to wxruby2 In-Reply-To: <42DDD614.2040503@qualitycode.com> References: <42DDD614.2040503@qualitycode.com> Message-ID: <42E400AD.5070006@yahoo.com> Kevin Smith wrote: > [...] > > My goal is to release a beta version of wxruby2 within a few weeks. > > Kevin Kevin, Thanks so much for updating wxruby. IMHO, wxruby is one of the most important projects in ruby. With a hardcopy book on wxWidgets coming out this month, I'm sure wxWidgets will continue to grow in popularity. I'd like to see wxruby2 continue to be able to use wxWidgets 2.6.0 rather than 2.6.1 or later versions. There were some wording changes in the wxWidgets 2.6.1 license that (unintentionally according to one wxWidgets developer) requires derived binary works to allow reverse-engineering and modifications by end users. Continued support for 2.6.0 will make wxruby more compatible with commerical EULA. Thanks again! From usrlocalinfo at yahoo.com Sun Jul 24 17:21:57 2005 From: usrlocalinfo at yahoo.com (DJB) Date: Sun Jul 24 17:17:44 2005 Subject: [Wxruby-users] Re: wxruby In-Reply-To: References: <42D79938.8090402@xs4all.nl> <42D7BD75.8030708@mindspring.com> <42D8245F.6070801@hibbs.com> <42D83767.6010208@mindspring.com> <42D90C50.4060008@qualitycode.com> Message-ID: <42E40675.8030800@yahoo.com> Sean Long wrote: > Kevin, > > After working on this for awhile I think the project should only focus > on wxWidgets 2.6.1 and beyond. If anyone wants to use wxWidgets 2.4.x > they can use the old wxRuby 0.6 path. Kevin, I hope wxruby will support wxWidgets 2.6.0 instead of requiring 2.6.1. I'm not allowed to use wxWidgets 2.6.1 because the change in license (from 2.6.0) forces derived *binary* works to require distribution terms to allow reverse-engineering and modifications by end users. We use wxWidgets 2.6.0 primarily with C++ but I'm trying to spread the use of both ruby and wxruby at work. Requiring 2.6.1 will make wxruby unusable by us because we are not allowed to link anything we develop with it. I'm hoping wxWidgets 2.6.2 will revert back to the less restrictive license found in the wxWidgets 2.6.0 Manual. From wxruby at qualitycode.com Sun Jul 24 19:02:07 2005 From: wxruby at qualitycode.com (Kevin Smith) Date: Sun Jul 24 18:57:26 2005 Subject: [Wxruby-users] wx 2.6.1 license change? ( was: Re: wxruby) In-Reply-To: <42E40675.8030800@yahoo.com> References: <42D79938.8090402@xs4all.nl> <42D7BD75.8030708@mindspring.com> <42D8245F.6070801@hibbs.com> <42D83767.6010208@mindspring.com> <42D90C50.4060008@qualitycode.com> <42E40675.8030800@yahoo.com> Message-ID: <42E41DEF.8030907@qualitycode.com> DJB wrote: > > I hope wxruby will support wxWidgets 2.6.0 instead of requiring 2.6.1. > > I'm not allowed to use wxWidgets 2.6.1 because the change in license > (from 2.6.0) forces derived *binary* works to require distribution terms > to allow reverse-engineering and modifications by end users. Very interesting. Personally, I think reverse-engineering should always be allowed, but my position as wxRuby lead has always been that our library should be useable by pretty much anyone in pretty much any way they wish. Can you point to the 2.6.1 license text that causes a problem? I'm looking at the wxWidgets CVS repository. It seems that for at least 6 years, the LGPL v2 has said: --- 6. As an exception to the Sections above, you may also compile or link a "work that uses the Library" with the Library to produce a work containing portions of the Library, and distribute that work under terms of your choice, provided that the terms permit modification of the work for the customer's own use and reverse engineering for debugging such modifications. --- But it appears that the wxWindows/wxWidgets library allows you to override this with your own exception, as it says in the wxWidgets v3 license (which hasn't changed for 14 months): -- 2. The exception is that you may use, copy, link, modify and distribute under the user's own terms, binary object code versions of works based on the Library. -- My interpretation of that (and I am not a lawyer) would be that as long as you only distributed binary code, you could do so under your "own terms", which could prevent modifications and reverse-engineering. Kevin From wxruby at qualitycode.com Sun Jul 24 19:04:41 2005 From: wxruby at qualitycode.com (Kevin Smith) Date: Sun Jul 24 18:59:54 2005 Subject: [Wxruby-users] Moving to wx 2.6 In-Reply-To: <42DF98F1.2080808@qualitycode.com> References: <42DDA310.8070504@qualitycode.com> <42DF98F1.2080808@qualitycode.com> Message-ID: <42E41E89.4030909@qualitycode.com> Kevin Smith wrote: > > I tried to apply these last night, but encountered several problems that > seem to be due to changes between wx 2.5 and 2.6. I can't think of a > clean way to support both, so I plan to upgrade myself to 2.6 and then > change wxruby2 to only support that version. I'm changing my mind again. I have been experimenting with wx 2.6 today. I got it to link statically, but I'm really not sure that's the best option after all. It seems like it introduces more complexity and more dependencies, rather than less. At this point, I am again leaning toward trying to support 2.5+. > I will upgrade my system to 2.6, and then will apply Sean's latest > changes. I have not yet attempted (again) to apply Sean's latest patches in a way that lets them work with wx 2.5. On the other hand, the code that is currently checked into the head compiles with both 2.5 and 2.6 on my system, so I am more optimistic that the problems are not due to differences between 2.5 and 2.6. Kevin From wxruby at qualitycode.com Sun Jul 24 21:27:15 2005 From: wxruby at qualitycode.com (Kevin Smith) Date: Sun Jul 24 21:22:38 2005 Subject: [Wxruby-users] Fwd: fix Choice.cpp unicode string In-Reply-To: <29e11553050724124322e2434a@mail.gmail.com> References: <29e1155305072412281ab845ff@mail.gmail.com> <29e11553050724124322e2434a@mail.gmail.com> Message-ID: <42E43FF3.5040002@qualitycode.com> Jani Monoses wrote: > This is needed so that samples/etc/choice.rb shows the strings in the > choice box. > One of the few places that missed UTF8 convertion. > > --- swig/classes/Choice.i 31 Jan 2005 04:18:52 -0000 1.2 > +++ swig/classes/Choice.i 24 Jul 2005 19:18:55 -0000 > @@ -14,7 +14,7 @@ > for(int i=0; i < $1; ++i) > { > VALUE thisItem = rb_ary_entry($input, i); > - $2[i] = (wxChar *)STR2CSTR(thisItem); > + $2[i] = wxConvUTF8.cMB2WC(STR2CSTR(thisItem)); > } > } Ah, yes. My goal would be that none of the class .i files would need to contain typemaps or otherwise muck with low-level stuff like this. I'll apply your patch (assuming it works for me), but will hope to find a better long-term solution. > There's another I think UTF8 problem: The onAbout dialog in caret.rb > uses the (c) character so the string is not shown. Good catch. I'll make a note to do something about this as well. Thanks, Kevin From wxruby at qualitycode.com Sun Jul 24 21:30:04 2005 From: wxruby at qualitycode.com (Kevin Smith) Date: Sun Jul 24 21:25:19 2005 Subject: [Wxruby-users] Moving to wx 2.6 In-Reply-To: <42E41E89.4030909@qualitycode.com> References: <42DDA310.8070504@qualitycode.com> <42DF98F1.2080808@qualitycode.com> <42E41E89.4030909@qualitycode.com> Message-ID: <42E4409C.4060503@qualitycode.com> Kevin Smith wrote: > I have not yet attempted (again) to apply Sean's latest patches in a way > that lets them work with wx 2.5. On the other hand, the code that is > currently checked into the head compiles with both 2.5 and 2.6 on my > system, so I am more optimistic that the problems are not due to > differences between 2.5 and 2.6. I just checked in code that integrates Sean's patches, and tagged a 0.0.20 version. My next step is to make the switch to wxruby2 naming, including having the wx.rb wrapper in the lib/ directory. I'm not sure how this will affect the MSWin and Mac build/install processes. I have only found one true difference between 2.5 and 2.6 so far, and that is the addition of a "skip" parameter to ProgressDialog#update. So, for now, I have left that parameter off. We'll have to try to figure out a clean way to support it. Sean: Please try the latest HEAD (or v0-0-20) as-is. If you find any problems, please let me know so we can work together to find ways to solve them that are compatible with both 2.5 and 2.6. Kevin From wxruby at qualitycode.com Sun Jul 24 21:31:11 2005 From: wxruby at qualitycode.com (Kevin Smith) Date: Sun Jul 24 21:26:25 2005 Subject: [Wxruby-users] Re: I just got wxruby-swig working with unicode! In-Reply-To: References: <42D79938.8090402@xs4all.nl> <42D7BD75.8030708@mindspring.com> <42D8245F.6070801@hibbs.com> <42D83767.6010208@mindspring.com> <42D90C50.4060008@qualitycode.com> <42DAF7DB.7010601@qualitycode.com> <42DB34CD.1090903@qualitycode.com> <42DC27C8.3020009@qualitycode.com> <42DC7D0C.5040309@qualitycode.com> <42DC87CD.1010704@qualitycode.com> <42DD2476.1010501@qualitycode.com> <42DD39E6.3020808@qualitycode.com> <42DF9A31.70302@qualitycode.com> Message-ID: <42E440DF.6030702@qualitycode.com> Jani Monoses wrote: >>> while samples/controls/controls.rb crashes in TextCtrl.new(), >>> something to do with arguments not being valid. I fixed this for now by disabling the second constructor, which isn't really necessary anyway. Kevin From alex at pressure.to Sun Jul 24 22:16:48 2005 From: alex at pressure.to (Alex Fenton) Date: Sun Jul 24 22:11:23 2005 Subject: [Wxruby-users] rubygems versions In-Reply-To: <42E3E832.9020000@nibor.org> References: <42DED317.6050508@pressure.to> <42E3E832.9020000@nibor.org> Message-ID: <42E44B90.4020009@pressure.to> Hi Robin Thanks - it's not down to me, but seems to me like a good idea to use this scheme for versioning. I'm sure this is planned for the final release (2.x.x was suggested) but I think it would be useful to follow it for the pre-release wx-swig versions to ease use and upgrading via rubygems. The question would be what version number to use. Perhaps it could be 0.9.0, towards a 1.0.0 swig-based wxruby(2)? release? cheers alex > > Is there a reason for not using the rubygems versioning policy? > http://docs.rubygems.org/read/chapter/7 > > I'm just curious. > > Robin From wxruby at qualitycode.com Sun Jul 24 22:51:14 2005 From: wxruby at qualitycode.com (Kevin Smith) Date: Sun Jul 24 22:46:31 2005 Subject: [Wxruby-users] wxruby2 version numbers (was: rubygems versions) In-Reply-To: <42E44B90.4020009@pressure.to> References: <42DED317.6050508@pressure.to> <42E3E832.9020000@nibor.org> <42E44B90.4020009@pressure.to> Message-ID: <42E453A2.8060808@qualitycode.com> Alex Fenton wrote: > > Thanks - it's not down to me, but seems to me like a good idea to use > this scheme for versioning. I'm sure this is planned for the final > release (2.x.x was suggested) but I think it would be useful to follow > it for the pre-release wx-swig versions to ease use and upgrading via > rubygems. > > The question would be what version number to use. Perhaps it could be > 0.9.0, towards a 1.0.0 swig-based wxruby(2)? release? Yes, I agree that the rubygems proposed versioning scheme makes sense, and we'll try to adopt it for wxruby2. I am struggling with version numbers for the pre-release versions of wxruby2. For now, I am continuing with the 0.0.xx releases that were started with wxruby-swig. We are up to 0.0.20. As soon as we have a plausible near-release candidate, I will switch to 2.0.0-rc1, and from then on we'll have "normal" release numbers. I considered using 0.9, but that would be confusing with our wxruby 0.6 stable release. I thought about 1.9 but that seems even worse. I even considered doing 2.0.0 that isn't actually a 2.0 release, but that seems even worse than the other two. So I'm back to 0.0.21. Hopefully this state won't last long. Kevin From usrlocalinfo at yahoo.com Sun Jul 24 22:51:03 2005 From: usrlocalinfo at yahoo.com (DJB) Date: Sun Jul 24 22:46:33 2005 Subject: [Wxruby-users] Re: wx 2.6.1 license change? ( was: Re: wxruby) In-Reply-To: <42E41DEF.8030907@qualitycode.com> References: <42D79938.8090402@xs4all.nl> <42D7BD75.8030708@mindspring.com> <42D8245F.6070801@hibbs.com> <42D83767.6010208@mindspring.com> <42D90C50.4060008@qualitycode.com> <42E40675.8030800@yahoo.com> <42E41DEF.8030907@qualitycode.com> Message-ID: <42E45397.7080008@yahoo.com> DISCLAIMER: Seek the advice of an intellectual property attorney before taking any action related to copyright and licensing. This message is for entertainment purposes only and may contain numerous factual errors. Kevin Smith wrote: > Can you point to the 2.6.1 license text that causes a problem? I'm > looking at the wxWidgets CVS repository. It seems that for at least 6 > years, the LGPL v2 has said: The differences can be seen in the .chm manual files distributed with wxWidgets and online at: http://www.wxwidgets.org/manuals/2.6.1/wx_wxlicense.html#wxlicense http://www.wxwidgets.org/manuals/2.6.0/wx_wxlicense.html#wxlicense > My interpretation of that (and I am not a lawyer) would be that as long > as you only distributed binary code, you could do so under your "own > terms", which could prevent modifications and reverse-engineering. > > Kevin LGPL only allows distribution of works based on an LGPL library under "terms of your choice" only if your terms permit reverse-engineering and modifications by end users (see LGPL Section 6). wxWidgets is covered by LGPL but exceptions to various terms of LGPL are granted for binaries. These exceptions to LGPL terms differ between 2.6.0 and 2.6.1. This means vendors distributing shareware or trial versions of software linked to LGPL libraries must do something that doesn't make sense for their situation. Many customers won't pay if the vendors give them full LEGAL permission to patch the trial or shareware version. Or pay for expensive Enterprise editions if the cheaper Standard edition can be patched legally. The 2.6.0 license made it clear that binaries are not subject to LGPL restrictions when being distributed on your own terms because of the phrase "distribute [...] unrestricted under terms of your choice". The 2.6.1 license removed the word "unrestricted", among other things, so that if the binaries are distributed under non-LGPL terms, those terms must permit reverse-engineering and modifications by end users. One more confusion 2.6.1 license introduced is the use of the word "user's" when the licensee ("you") was already identified as "you" in the same sentence: 2.6.1: "you may [...] distribute under the user's own terms" 2.6.0: "you may [...] distribute [...] unrestricted under terms of your choice" Since the licensee was referred in the sentence as "you", the use of the word "user's" cannot simply be assumed to refer to the same. It is not unreasonable to believe "user's" now refers to the end-user of the combined product, especially given that the wxWidgets is free and open source. In other words, the 2.6.1 license is a big risk for closed-source commercial products. If 2.6.2 doesn't fix the license, I wouldn't be surprised if a bunch of closed source projects migrates away from wxWidgets. ps Please ask a GPL Compliance Engineer at Free Software Foundation (fsf.org) before dismissing my explanation. A helpful expert like David Turner will probably respond with a detailed explanation within a week or so. The LGPL is one of the most misunderstood licenses because people don't bother reading it or they don't bother asking the right people for clarifications. From wxruby at qualitycode.com Sun Jul 24 22:51:46 2005 From: wxruby at qualitycode.com (Kevin Smith) Date: Sun Jul 24 22:47:00 2005 Subject: [Wxruby-users] Wxruby2 gemspec In-Reply-To: <42E3E832.9020000@nibor.org> References: <42DED317.6050508@pressure.to> <42E3E832.9020000@nibor.org> Message-ID: <42E453C2.2020908@qualitycode.com> Robin Stocker wrote: > Alex Fenton wrote: > >> WXRUBY2_GEMSPEC = Gem::Specification.new do | s | >> s.name = 'wxruby2' >> s.version = '0.20' Ah. I just noticed this. The current wxruby2 release is 0.0.20, not 0.20. Kevin From wxruby at qualitycode.com Sun Jul 24 23:00:01 2005 From: wxruby at qualitycode.com (Kevin Smith) Date: Sun Jul 24 22:55:16 2005 Subject: [Wxruby-users] Official name change to wxruby2 Message-ID: <42E455B1.1000809@qualitycode.com> The CVS module has been renamed from wxruby-swig to wxruby2, and I have checked in the related changes to reflect the name change. Anyone with a CVS tree will need to re-checkout from CVS because of the module name change. There is now a wx.rb in the lib/ directory, which loads the wxruby2 shared library that gets built. I have tagged this as 0.0.22. Next steps: - Apply Choice.i patch from Jani Monoses - Fix unicode errors in class .i files - Eliminate compiler warnings Kevin From alex at pressure.to Sun Jul 24 23:02:07 2005 From: alex at pressure.to (Alex Fenton) Date: Sun Jul 24 22:56:39 2005 Subject: [Wxruby-users] Wxruby2 gemspec In-Reply-To: <42E453C2.2020908@qualitycode.com> References: <42DED317.6050508@pressure.to> <42E3E832.9020000@nibor.org> <42E453C2.2020908@qualitycode.com> Message-ID: <42E4562F.9040802@pressure.to> > Ah. I just noticed this. The current wxruby2 release is 0.0.20, not 0.20. OK, thanks, I'll correct. That should work fine with rubygems. I need to add a line for the ruby loader/wrapper wx.rb - I'll assume this'll be in lib/wx.rb in CVS. On versions - perhaps if we're renaming the package we should release wxruby2 1.0.0 - by analogy with sqlite (which has versions 1.x.x and 2.x.x) and sqlite3 (which has version 1.x.x). alex From wxruby at qualitycode.com Sun Jul 24 23:12:13 2005 From: wxruby at qualitycode.com (Kevin Smith) Date: Sun Jul 24 23:07:28 2005 Subject: [Wxruby-users] Re: wx 2.6.1 license change? ( was: Re: wxruby) In-Reply-To: <42E45397.7080008@yahoo.com> References: <42D79938.8090402@xs4all.nl> <42D7BD75.8030708@mindspring.com> <42D8245F.6070801@hibbs.com> <42D83767.6010208@mindspring.com> <42D90C50.4060008@qualitycode.com> <42E40675.8030800@yahoo.com> <42E41DEF.8030907@qualitycode.com> <42E45397.7080008@yahoo.com> Message-ID: <42E4588D.4080609@qualitycode.com> DJB wrote: > The differences can be seen in the .chm manual files distributed with > wxWidgets and online at: > > http://www.wxwidgets.org/manuals/2.6.1/wx_wxlicense.html#wxlicense > http://www.wxwidgets.org/manuals/2.6.0/wx_wxlicense.html#wxlicense Perhaps, but I believe the software would be covered by the LICENSE.TXT that is distributed with the software itself, and as far as I can tell the change you refer to was actually made 14 months ago. So based on what I'm seeing in the wxWidgets CVS tree, all wxWidgets versions from 2.5.2 on are bound by the license terms you dislike. Which version of the license is in the 2.6.0 wxWidgets tarball that you downloaded? > Since the licensee was referred in the sentence as "you", the use of the > word "user's" cannot simply be assumed to refer to the same. It is not > unreasonable to believe "user's" now refers to the end-user of the > combined product, especially given that the wxWidgets is free and open > source. I agree that the new wording is confusing and should be changed. > Please ask a GPL Compliance Engineer at Free Software Foundation > (fsf.org) before dismissing my explanation. A helpful expert like David > Turner will probably respond with a detailed explanation within a week > or so. The LGPL is one of the most misunderstood licenses because > people don't bother reading it or they don't bother asking the right > people for clarifications. For this, I probably wouldn't rely on an FSF interpretation, because the wording in question is in the wx-specific exception. The LGPL is clear, but it's not entirely clear whether the wx exception bypasses the LGPL or not. Thanks, Kevin From wxruby at qualitycode.com Sun Jul 24 23:15:03 2005 From: wxruby at qualitycode.com (Kevin Smith) Date: Sun Jul 24 23:10:18 2005 Subject: [Wxruby-users] Wxruby2 gemspec In-Reply-To: <42E4562F.9040802@pressure.to> References: <42DED317.6050508@pressure.to> <42E3E832.9020000@nibor.org> <42E453C2.2020908@qualitycode.com> <42E4562F.9040802@pressure.to> Message-ID: <42E45937.7020104@qualitycode.com> Alex Fenton wrote: > OK, thanks, I'll correct. That should work fine with rubygems. I need to > add a line for the ruby loader/wrapper wx.rb - I'll assume this'll be in > lib/wx.rb in CVS. Correct. > On versions - perhaps if we're renaming the package we should release > wxruby2 1.0.0 - by analogy with sqlite (which has versions 1.x.x and > 2.x.x) and sqlite3 (which has version 1.x.x). Yes, that is an option, especially since we never released a 1.0 version of wxruby1. I lean toward 2.0.0, but am open to other opinions. Kevin From jani at iv.ro Mon Jul 25 10:03:49 2005 From: jani at iv.ro (Jani Monoses) Date: Mon Jul 25 09:59:43 2005 Subject: [Wxruby-users] Re: Official name change to wxruby2 In-Reply-To: <42E455B1.1000809@qualitycode.com> References: <42E455B1.1000809@qualitycode.com> Message-ID: > > There is now a wx.rb in the lib/ directory, which loads the wxruby2 > shared library that gets built. > I checked out the module but see no wx.rb in lib Jani From sean.m.long at gmail.com Mon Jul 25 12:05:00 2005 From: sean.m.long at gmail.com (Sean Long) Date: Mon Jul 25 11:59:46 2005 Subject: [Wxruby-users] Official name change to wxruby2 In-Reply-To: <42E455B1.1000809@qualitycode.com> References: <42E455B1.1000809@qualitycode.com> Message-ID: I also did not see wx.rb in the lib directory. The project compiled fine on OS X 10.4 and I installed it but got an error saying the init function could not be found (not at that computer right now so I can not give you the exact wording). I imagine that this is caused by the missing wx.rb file. I have been pretty busy lately so I have not had too much time to hack on wxruby2 the rest of this week does not look good either because I will be on a business trip for 3 days. Last night I did update the wxruby-swig wiki page to more closely reflect the current project state if anyone has more time that would be something nice to work on, it was a valuable resource in getting me going on added to the project. http://wxruby.rubyforge.org/wiki/wiki.pl?How_To_Add_A_New_Class_To_Wxruby-Swig Sean On 7/24/05, Kevin Smith wrote: > The CVS module has been renamed from wxruby-swig to wxruby2, and I have > checked in the related changes to reflect the name change. Anyone with a > CVS tree will need to re-checkout from CVS because of the module name > change. > > There is now a wx.rb in the lib/ directory, which loads the wxruby2 > shared library that gets built. > > I have tagged this as 0.0.22. > > Next steps: > - Apply Choice.i patch from Jani Monoses > - Fix unicode errors in class .i files > - Eliminate compiler warnings > > Kevin > _______________________________________________ > wxruby-users mailing list > wxruby-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-users > From wxruby at qualitycode.com Mon Jul 25 12:04:44 2005 From: wxruby at qualitycode.com (Kevin Smith) Date: Mon Jul 25 12:00:11 2005 Subject: [Wxruby-users] Missing lib/wx.rb (was: Official name change to wxruby2) In-Reply-To: References: <42E455B1.1000809@qualitycode.com> Message-ID: <42E50D9C.10906@qualitycode.com> Jani Monoses wrote: > I checked out the module but see no wx.rb in lib Doh! It's there now. Last night, I had issued the cvs add command, but right then the rubyforge folks renamed the cvs module as I had asked. So I had to copy all my changes to a new tree, and in the new tree I forgot to redo the cvs add. And I forgot to do a cvs update/diff after I checked in, which was the real process error. Sorry, Kevin From alex at pressure.to Mon Jul 25 16:53:47 2005 From: alex at pressure.to (Alex Fenton) Date: Mon Jul 25 16:48:18 2005 Subject: [Wxruby-users] Official name change to wxruby2 In-Reply-To: References: <42E455B1.1000809@qualitycode.com> Message-ID: <42E5515B.7090609@pressure.to> Sean Long wrote: >Last night I did update the wxruby-swig wiki page to more closely >reflect the current project state if anyone has more time that would >be something nice to work on, it was a valuable resource in getting me >going on added to the project. >http://wxruby.rubyforge.org/wiki/wiki.pl?How_To_Add_A_New_Class_To_Wxruby-Swig > > Have amended a few more details and added http://wxruby.rubyforge.org/wiki/wiki.pl?What_Classes_Are_Implemented_In_Wxruby with a recent snapshot of wxruby vs wxruby cheers alex From roys at mindspring.com Mon Jul 25 23:24:45 2005 From: roys at mindspring.com (Roy Sutton) Date: Mon Jul 25 23:19:19 2005 Subject: [Wxruby-users] Compiling on WinXP, MSVC In-Reply-To: <42E5515B.7090609@pressure.to> References: <42E455B1.1000809@qualitycode.com> <42E5515B.7090609@pressure.to> Message-ID: <42E5ACFD.40806@mindspring.com> Hello all. I'm trying to get my system all set up with MSVC on Win XP and I'm running into a few things that I want to get a good handle on before I change them around. At least the way _I_ built WxWidgets the build process places the libraries in %WXWIN%\lib\vc_lib. The rake build wants them to be in %WXWIN%\lib. I think I should mod the rakemswin file to bring it up-to-date. Second, the wxwin libraries appear to be named wxXXX.lib instead of the bare XXX.lib as specified in rakemswin. Third, the wxmsw[d].lib file appears to now be named wxmsw26[d]_core.lib and we need to add wxmsw26[d]_adv.lib, wxbase26[d].lib and wxmsw26[d]_xrc.lib. Including _xrc requires wxbase26[d]_xml.lib which seems to require something I don't have at all (libexpat?). I'm kinda stuck here. xrc may not be required, only one external is missing from the library, maybe we can do without it? At this point, I'm stuck. Fourth, the output library tries to get written into a bad directory. I've adjusted it to the directory the other libs are in. I have an updated rakemswin if anyone's interested, though you still can't rake a complete build out of it. I'd appreciate any help getting this going. Roy From roys at mindspring.com Mon Jul 25 23:28:41 2005 From: roys at mindspring.com (Roy Sutton) Date: Mon Jul 25 23:23:12 2005 Subject: [Wxruby-users] Compiling on WinXP, MSVC In-Reply-To: <42E5ACFD.40806@mindspring.com> References: <42E455B1.1000809@qualitycode.com> <42E5515B.7090609@pressure.to> <42E5ACFD.40806@mindspring.com> Message-ID: <42E5ADE9.9060003@mindspring.com> Whoops, cried wolf too soon. I had neglected to build wxexap[d].lib so didn't see it as an option for linking. All's good and I've compiled the library. We'll see how far I get now! Roy Roy Sutton wrote: > Hello all. I'm trying to get my system all set up with MSVC on Win XP > and I'm running into a few things that I want to get a good handle on > before I change them around. > > At least the way _I_ built WxWidgets the build process places the > libraries in %WXWIN%\lib\vc_lib. The rake build wants them to be in > %WXWIN%\lib. I think I should mod the rakemswin file to bring it > up-to-date. > > Second, the wxwin libraries appear to be named wxXXX.lib instead of > the bare XXX.lib as specified in rakemswin. > > Third, the wxmsw[d].lib file appears to now be named > wxmsw26[d]_core.lib and we need to add wxmsw26[d]_adv.lib, > wxbase26[d].lib and wxmsw26[d]_xrc.lib. Including _xrc requires > wxbase26[d]_xml.lib which seems to require something I don't have at > all (libexpat?). I'm kinda stuck here. xrc may not be required, only > one external is missing from the library, maybe we can do without it? > At this point, I'm stuck. > > Fourth, the output library tries to get written into a bad directory. > I've adjusted it to the directory the other libs are in. > > I have an updated rakemswin if anyone's interested, though you still > can't rake a complete build out of it. I'd appreciate any help > getting this going. > > Roy > > _______________________________________________ > wxruby-users mailing list > wxruby-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-users > > > From roys at mindspring.com Mon Jul 25 23:55:40 2005 From: roys at mindspring.com (Roy Sutton) Date: Mon Jul 25 23:50:25 2005 Subject: [Wxruby-users] Compiling on WinXP, MSVC In-Reply-To: <42E5ADE9.9060003@mindspring.com> References: <42E455B1.1000809@qualitycode.com> <42E5515B.7090609@pressure.to> <42E5ACFD.40806@mindspring.com> <42E5ADE9.9060003@mindspring.com> Message-ID: <42E5B43C.9030009@mindspring.com> I have updated the 'How to add a new class' Wiki page with a few clarifications that should help people who are doing this for the first time. Now that I've got all this working, does anyone have any suggestions on where I should focus my (somewhat limited) efforts? Is there any particular Windows-specific testing I can do? Attached is my modified rakemswin.rb file. I can't promise my changes reflect what was anticipated. In particular, I think that the file should try to detect the WxWidgets build number so that 26 is not hard-coded into the file as it is now. Perhaps even smarter would be to just slurp up all the .lib names from the target lib directory, allowing for new libs as they might appear. Roy P.S. >grumble< That should have been wxexpat[d].lib below. Roy Sutton wrote: > Whoops, cried wolf too soon. I had neglected to build wxexap[d].lib > so didn't see it as an option for linking. All's good and I've > compiled the library. We'll see how far I get now! > > Roy -------------- next part -------------- # rakemswin.rb # Copyright 2004 by Kevin Smith # released under the wxWidgets license # as part of the wxRuby project ############################# # platform-dependent settings require 'rbconfig' include Config $cpp = "cl.exe" $ld = "link" $link_output_flag = "/dll /out:" $DEBUG = true # native Windows - requires a static build of wxWindows $WXDIR=ENV['WXWIN'] $WXVERSION = '24' if $DEBUG $DEBUGPOSTFIX='d' else $DEBUGPOSTFIX='' end $WXSRC="#$WXDIR/src/msw" $WXINC="#$WXDIR/include" $WXLIBDIR="#$WXDIR/lib/vc_lib" $INCTEMP="#$WXDIR/lib/msw#{$DEBUGPOSTFIX}" $WXLIB="#$WXLIBDIR/wxmsw26#{$DEBUGPOSTFIX}_core.lib" $wx_cppflags = [ "-I#$WXINC", "/D__WXMSW__", "-D__WXMSW__", "-I#$INCTEMP", ].join(' ') $extra_cppflags = [ "/GR", "/GX", "-DSTRICT", "-DWIN32", "-D__WIN32__", "-D_WINDOWS", "/D__WINDOWS__", "-DWINVER=0x0400", "/D__WIN95__", ].join(' ') if $DEBUG $ruby_cppflags.gsub!(/-MD/," /MDd"); $ruby_cppflags.gsub!(/-O[A-Za-z0-9-]*/, "/Od") $extra_cppflags += " -D_DEBUG -D__WXDEBUG__ -DWXDEBUG=1 " else $extra_cppflags += " -DNDEBUG " end if $DEBUG $wx_ldflags = " /DEBUG /PDB:#$WXLIBDIR/vc60.pdb " else $wx_ldflags = "" end $wx_libs = [ "#$WXLIBDIR/wxpng#{$DEBUGPOSTFIX}.lib", "#$WXLIBDIR/wxzlib#{$DEBUGPOSTFIX}.lib", "#$WXLIBDIR/wxjpeg#{$DEBUGPOSTFIX}.lib", "#$WXLIBDIR/wxtiff#{$DEBUGPOSTFIX}.lib", "#$WXLIBDIR/wxbase26#{$DEBUGPOSTFIX}.lib", "#$WXLIBDIR/wxmsw26#{$DEBUGPOSTFIX}_adv.lib", "#$WXLIBDIR/wxmsw26#{$DEBUGPOSTFIX}_xrc.lib", "#$WXLIBDIR/wxbase26#{$DEBUGPOSTFIX}_xml.lib", "#$WXLIBDIR/wxexpat#{$DEBUGPOSTFIX}.lib", $WXLIB,].join(' ') $extra_libs = [ "gdi32.lib", "winspool.lib", "comdlg32.lib", "shell32.lib", "ole32.lib", "oleaut32.lib", "uuid.lib", "odbc32.lib ", "odbccp32.lib", "comctl32.lib", "rpcrt4.lib", "winmm.lib","#{Config::TOPDIR}/lib/msvcrt-ruby18.lib"].join(' ') $extra_objs = "swig/wx.res" rule('.res' => '.rc') do | t | sh("rc -I#$WXINC #{t.prerequisites}") end From defelicedomenico at gmail.com Tue Jul 26 03:37:23 2005 From: defelicedomenico at gmail.com (Domenico De Felice) Date: Tue Jul 26 03:31:46 2005 Subject: [Wxruby-users] Wx::Html* widgets Message-ID: <95868c9a0507260037465e0532@mail.gmail.com> Hello, I'm having problems using the widgets Wx::Http*, such as Wx::HtmlWindow, Wx::HtmlEasyPrinting, etc.. The error I got is "uninitialized constant Wx::HtmlWindow". The code is correct since I'm trying to execute samples in the html/ directory. All other samples work. I can't even see that widgets doing require 'wxruby'; ObjectSpace.each_object(Class) {|c| p c if c.name =~ /Wx/} I see all the widgets but the html* ones. Is this a problem of mine or the html widgets aren't still bound to Ruby? I'm using WxRuby 0.6.0 on GNU/Linux (compiled on my pc) Thanks, Domenico From wxruby at qualitycode.com Tue Jul 26 08:06:12 2005 From: wxruby at qualitycode.com (Kevin Smith) Date: Tue Jul 26 08:01:48 2005 Subject: [Wxruby-users] Wx::Html* widgets In-Reply-To: <95868c9a0507260037465e0532@mail.gmail.com> References: <95868c9a0507260037465e0532@mail.gmail.com> Message-ID: <42E62734.3050301@qualitycode.com> Domenico De Felice wrote: > Hello, > I'm having problems using the widgets Wx::Http*, such as > Wx::HtmlWindow, Wx::HtmlEasyPrinting, etc.. > The error I got is "uninitialized constant Wx::HtmlWindow". > I'm using WxRuby 0.6.0 on GNU/Linux (compiled on my pc) Hi, I forget why, but the html classes are specifically omitted from Linux builds of wxruby 0.6. You can try enabling them to see if whatever problem caused us to disable them has perhaps been fixed. In extconf.rb, you should see this section: if /linux/ =~ RUBY_PLATFORM or /freebsd/ =~ RUBY_PLATFORM CONFIG['CC'] = `wx-config --cxx` CONFIG['LDSHARED'].gsub!("gcc",`wx-config --cxx`.strip) $CFLAGS += " `wx-config --cxxflags`" $LDFLAGS += " `wx-config --libs` -Wl,--version-script,./version-script " ["htmlprocessor.o", "htmlwindow.o", "htmleasyprinting.o"].each do |str| $objs.delete(str) end if ($use_xrc) $LDFLAGS += " -lwx_gtk2_xrc-2.4 " end Just comment out the $objs.delete(str) line (and perhaps the line above and the line below also). Then re-run extconf.rb and attempt the make. I doubt it will work, but if you report the problems we can try to figure out whether it is solveable or not. Kevin From defelicedomenico at gmail.com Tue Jul 26 14:47:12 2005 From: defelicedomenico at gmail.com (Domenico De Felice) Date: Tue Jul 26 14:41:34 2005 Subject: [Wxruby-users] Wx::Html* widgets In-Reply-To: <95868c9a05072611452967af4f@mail.gmail.com> References: <95868c9a0507260037465e0532@mail.gmail.com> <42E62734.3050301@qualitycode.com> <95868c9a05072611452967af4f@mail.gmail.com> Message-ID: <95868c9a0507261147309dc2@mail.gmail.com> On 7/26/05, Kevin Smith wrote: > Hi, [...] > Just comment out the $objs.delete(str) line (and perhaps the line above > and the line below also). Then re-run extconf.rb and attempt the make. I > doubt it will work, but if you report the problems we can try to figure > out whether it is solveable or not. Uhm.. strangely it works :-) It seems to work without any problems (except the fact it cant find the image handler when a html widget try to render an image, but that is not a problem for me) I think that lines should be deleted since they aren't useful (at least in my case) Thank you for the help and for the wxruby bindings :-) Domenico PS: what about creating a .deb package? ;-) From sean.m.long at gmail.com Tue Jul 26 20:40:36 2005 From: sean.m.long at gmail.com (Sean Long) Date: Tue Jul 26 21:26:23 2005 Subject: [Wxruby-users] Patch for wxRuby2 Message-ID: Ok so I made a lot of changes and the controls sample works pretty good now. What I changed or added: - Got all my modifications meshed into wxRuby2. - Added constructors to wxIcon.h - Changed Xrc.i to XmlResource.i and changed wxXrc to wxXmlResource within the file. I also had to change Xrc to XmlResource in rakewx.rb. - For backwards compatability with wxRuby 0.6 I added the subclass methods to XmlResource. - Changed line 5 of wx.i from wxruby2 to wx, could not get wxruby2 to work. I also changed line 13 in fixmodule.rb to mWx and line 11 in fixmainmodule.rb to mWx from mWxruby2. Also changed mWx in functions.i and XmlResource.i - Added the xrc example program (again) - Added typemap to finally get wxItemKind working correctly, gets rid of my fixedswigcode.rb hack. - Added the wxMenuItem class. - Added a type check for wxDateTime so CalendarCtrl now works properly with ruby class DateTime. - Changed $DEBUG in extconf.rb to $DEBUG_BUILD, for some reason it was clashing with mkmf on Windows. - Added wxBeginBusyCursor and wxEndBusyCursor to functions.i - Added wxToolTip class. - Many missing methods for existing classes. - Slight tweaks to the sample programs. I also made this patch so Kevin can use this patch command: patch -p1 static VALUE xrcid(VALUE self,VALUE str_id) { char *tmp = STR2CSTR(str_id); int ret; VALUE retval; ret = wxXmlResource::GetXRCID((const wxChar *)tmp); retval = INT2NUM(ret); return retval; } %} %rename(LoadDialogSubclass) wxXmlResource::LoadDialog(wxDialog *dlg, wxWindow *parent, const wxString &name); %rename(LoadPanelSubclass) wxXmlResource::LoadPanel(wxPanel *pan, wxWindow *parent, wxString &name); %rename(LoadFrameSubclass) wxXmlResource::LoadFrame(wxFrame *frame, wxWindow *parent, const wxString &name); %init %{ extern VALUE mWx; rb_define_module_function(mWx, "xrcid", VALUEFUNC(xrcid), 1); %} %include "classes/include/wxXmlResource.h" -------------- next part -------------- # Copyright 2004 by Kevin Smith # released under the wxWidgets license # as part of the wxRuby project %include "../common.i" %module(directors="1") wxMenuItem %include "include/wxMenuItem.h" -------------- next part -------------- # Copyright 2004 by Kevin Smith # released under the wxWidgets license # as part of the wxRuby project %include "../common.i" %module(directors="1") wxToolTip %{ #include %} %include "include/wxToolTip.h" From sean.m.long at gmail.com Wed Jul 27 02:04:27 2005 From: sean.m.long at gmail.com (Sean Long) Date: Wed Jul 27 01:58:48 2005 Subject: [Wxruby-users] Re: Patch for wxRuby2 In-Reply-To: References: Message-ID: Found a small problem with my patch: In wxMenuItem.h the following two methods are specific to Windows and should not be included: // compatibility only, don't use in new code wxMenuItem(wxMenu *parentMenu, int id, const wxString& text, const wxString& help, bool isCheckable, wxMenu *subMenu = (wxMenu *)NULL); and int GetRealId(); Once these are removed the above patch and additions compiles fine on OS X 10.4 and Windows XP Pro. Sorry I don't have time to submit a new patch to replace the above. I won't be checking this list again until Saturday at the earliest, happy hacking. Sean On 7/26/05, Sean Long wrote: > Ok so I made a lot of changes and the controls sample works pretty good now. > > What I changed or added: > > - Got all my modifications meshed into wxRuby2. > - Added constructors to wxIcon.h > - Changed Xrc.i to XmlResource.i and changed wxXrc to wxXmlResource > within the file. > I also had to change Xrc to XmlResource in rakewx.rb. > - For backwards compatability with wxRuby 0.6 I added the subclass methods to > XmlResource. > - Changed line 5 of wx.i from wxruby2 to wx, could not get wxruby2 to > work. I also > changed line 13 in fixmodule.rb to mWx and line 11 in > fixmainmodule.rb to mWx from mWxruby2. > Also changed mWx in functions.i and XmlResource.i > - Added the xrc example program (again) > - Added typemap to finally get wxItemKind working correctly, gets rid > of my fixedswigcode.rb hack. > - Added the wxMenuItem class. > - Added a type check for wxDateTime so CalendarCtrl now works properly > with ruby class DateTime. > - Changed $DEBUG in extconf.rb to $DEBUG_BUILD, for some reason it was > clashing with mkmf on Windows. > - Added wxBeginBusyCursor and wxEndBusyCursor to functions.i > - Added wxToolTip class. > - Many missing methods for existing classes. > - Slight tweaks to the sample programs. > > I also made this patch so Kevin can use this patch command: > patch -p1 in the directory above wxruby2 > > As I said before I am going to be out of town starting Wed. so I will > not have time to respond or fix anything related to this patch until > next week, > I may have time tonight to atleast check this list but that is about it. > > Sean Long > > > From jani at iv.ro Wed Jul 27 03:10:16 2005 From: jani at iv.ro (Jani Monoses) Date: Wed Jul 27 03:05:55 2005 Subject: [Wxruby-users] Re: Wx::Html* widgets In-Reply-To: <95868c9a0507261147309dc2@mail.gmail.com> References: <95868c9a0507260037465e0532@mail.gmail.com> <42E62734.3050301@qualitycode.com> <95868c9a05072611452967af4f@mail.gmail.com> <95868c9a0507261147309dc2@mail.gmail.com> Message-ID: > Domenico > PS: what about creating a .deb package? ;-) I'll try to do that soon :) From alex at pressure.to Wed Jul 27 21:47:43 2005 From: alex at pressure.to (Alex Fenton) Date: Wed Jul 27 21:42:15 2005 Subject: [Wxruby-users] SWIGging ConfigBase Message-ID: <42E8393F.7050609@pressure.to> Hi all I'm trying to write an .i file for ConfigBase. If I can figure out a few general SWIG things then I think most of it will work. Apols for the noob swig questions. The C++ class has lots of overloaded methods called Read, which return different kinds of values. In wxruby-not-swig these are implemented as read, read_bool, read_int and so on. read() means read_string(). In ruby the methods read config_value = conf.read_bool(key, default) but in C++ it's bool Read(const wxString& key , bool* d , bool defaultVal ) const; There's also versions that receive just two arguments, the key and a reference to a typed variable that holds the default value which will be modified if there is a config value for that key or else left unchanged: bool Read(const wxString& key , bool* b ) const; I'm having two problems. 1) How correctly to rename a method. I'm trying %rename("ReadBool") wxConfigBase::Read(wxString const &key, bool *d, bool defaultVal); but it doesn't seem to give me a read_bool() method where I expect it. 2) How to deal with returning one of the parameters passed by ref, rather than the c++ return value (which is always "true" if something was read). I've tried, from the swig manual page on ruby void wxConfigBase::ReadBool(char *, bool *OUTPUT, bool); after my %rename directive, but again, no joy. Also, if someone could show me how to correctly map strings in these kind of declarations, that'd be great. I've tried the following for read_string, but I keep getting the C++ bool return value in ruby. bool wxConfigBase::Read(char *, char *, char* *OUTPUT); thanks alex From wxruby at qualitycode.com Wed Jul 27 23:06:33 2005 From: wxruby at qualitycode.com (Kevin Smith) Date: Wed Jul 27 23:01:07 2005 Subject: [Wxruby-users] Compiling on WinXP, MSVC In-Reply-To: <42E5B43C.9030009@mindspring.com> References: <42E455B1.1000809@qualitycode.com> <42E5515B.7090609@pressure.to> <42E5ACFD.40806@mindspring.com> <42E5ADE9.9060003@mindspring.com> <42E5B43C.9030009@mindspring.com> Message-ID: <42E84BB9.8080201@qualitycode.com> Roy Sutton wrote: > I have updated the 'How to add a new class' Wiki page with a few > clarifications that should help people who are doing this for the first > time. Great. > Now that I've got all this working, does anyone have any suggestions on > where I should focus my (somewhat limited) efforts? Is there any > particular Windows-specific testing I can do? If nothing else, running each of the samples would be a good start. > Attached is my modified rakemswin.rb file. I can't promise my changes > reflect what was anticipated. In particular, I think that the file > should try to detect the WxWidgets build number so that 26 is not > hard-coded into the file as it is now. Perhaps even smarter would be to > just slurp up all the .lib names from the target lib directory, allowing > for new libs as they might appear. I'll try to reconcile this with what Sean Long has sent in. I don't have a Windows box myself, and he does, so I have pretty much been trusting what he sends. Thanks for your help! Kevin From wxruby at qualitycode.com Thu Jul 28 01:27:18 2005 From: wxruby at qualitycode.com (Kevin Smith) Date: Thu Jul 28 01:21:54 2005 Subject: [Wxruby-users] Patch for wxRuby2 In-Reply-To: References: Message-ID: <42E86CB6.1060006@qualitycode.com> Sean Long wrote: > Ok so I made a lot of changes and the controls sample works pretty good now. I am quickly learning why Linus and other project maintainers ask folks to send small, self-contained patches, rather than large, monolithic ones like this. For anyone submitting patches, please try to create individual patches for each unit of work. That way, I can more easily review each one, and if I have questions about one of them, I can still apply the rest easily. Also, I can process a couple at a time when I have a spare moment, instead of doing a marathon session of getting it all to work at once. > What I changed or added: > > - Got all my modifications meshed into wxRuby2. Good to hear. > - Added constructors to wxIcon.h I had to comment out one of them in the .h file. For some reason all the %ignore lines in the .i file are being ignored by SWIG. > - Changed Xrc.i to XmlResource.i and changed wxXrc to wxXmlResource > within the file. I think that's probably a good change, but I would like to have seen it as two separate patches (one to create XmlResource.i, and a second to move the existing xrcid function into it and get rid of Xrc.i. However, do we need custom code for xrcid any more? Won't it automatically be exposed by SWIG as XmlResource.get_xrcid and isn't that good enough? I haven't merged this one in yet. > I also had to change Xrc to XmlResource in rakewx.rb. If XmlResource is in swig/classes/ (which is where it belongs) then Xrc should have been removed entirely from rakewx.rb. > - For backwards compatability with wxRuby 0.6 I added the subclass methods to > XmlResource. Ok. > - Changed line 5 of wx.i from wxruby2 to wx, could not get wxruby2 to > work. I also > changed line 13 in fixmodule.rb to mWx and line 11 in > fixmainmodule.rb to mWx from mWxruby2. > Also changed mWx in functions.i and XmlResource.i Let's figure this one out. I really want the module to be wxruby2, not wx, so I didn't apply your changes. Perhaps you just needed to do 'rake clean_src' to clear out all the old files that still referred to wx? > - Added the xrc example program (again) Ok. I guess I dropped it on the floor somewhere. Sorry. > - Added typemap to finally get wxItemKind working correctly, gets rid > of my fixedswigcode.rb hack. Cool. One of these days I need to really understand all the different kinds of typemaps. They are VERY powerful, but also very cryptic. > - Added the wxMenuItem class. Ok. I had to %ignore a few items. > - Added a type check for wxDateTime so CalendarCtrl now works properly > with ruby class DateTime. Hm. At one point I had decided not to support wxDateTime at all, because I felt that folks should be using Ruby's DateTime class instead. Is there a compelling reason to keep wxDateTime? > - Changed $DEBUG in extconf.rb to $DEBUG_BUILD, for some reason it was > clashing with mkmf on Windows. Ok, but I didn't see this in the patch you sent. > - Added wxBeginBusyCursor and wxEndBusyCursor to functions.i Ok, but the ruby way is to pass a block to BusyCursor.busy: BusyCursor.busy do ...stuff here end So the cursor is automatically cleaned up. I changed the controls sample to do it this way. Unfortunately, I can't test that sample on my Linux box because we don't yet support the Notebook class on Linux. > - Added wxToolTip class. Ok. I had to ignore one method. > - Many missing methods for existing classes. I had to %ignore a few. > - Slight tweaks to the sample programs. The only sample I saw changed was controls.rb. I changed the busy cursor part (see above). The other two changes looked confusing. You commented out one parameter, and you commented out a call to event.enable. Please explain why you made those changes. > > I also made this patch so Kevin can use this patch command: > patch -p1 in the directory above wxruby2 Thanks. Kevin From wxruby at qualitycode.com Thu Jul 28 23:24:40 2005 From: wxruby at qualitycode.com (Kevin Smith) Date: Thu Jul 28 23:19:05 2005 Subject: [Wxruby-users] Compiling on WinXP, MSVC In-Reply-To: <42E5B43C.9030009@mindspring.com> References: <42E455B1.1000809@qualitycode.com> <42E5515B.7090609@pressure.to> <42E5ACFD.40806@mindspring.com> <42E5ADE9.9060003@mindspring.com> <42E5B43C.9030009@mindspring.com> Message-ID: <42E9A178.2090504@qualitycode.com> Roy Sutton wrote: > Attached is my modified rakemswin.rb file. I can't promise my changes > reflect what was anticipated. In particular, I think that the file > should try to detect the WxWidgets build number so that 26 is not > hard-coded into the file as it is now. Perhaps even smarter would be to > just slurp up all the .lib names from the target lib directory, allowing > for new libs as they might appear. I really want to hear from other MSWin users about what the rakemswin.rb file should look like before I make any changes. I suspect part of the difference is that Sean is using a "monolithic" wx library, and you have the new-style modular version. I would love the rakefile to auto-detect which you have, and do the right thing. After all, part of the beauty of rakefiles is that they are ruby code, so detecting should be a snap. I also totally agree about the version autodetection. We use the version in several places, so I would like to see rakemswin.rb set $wx_version in a way that matches what wx-config sets it to (e.g. "2.5.3"). Thanks, Kevin From wxruby at qualitycode.com Thu Jul 28 23:44:55 2005 From: wxruby at qualitycode.com (Kevin Smith) Date: Thu Jul 28 23:39:23 2005 Subject: [Wxruby-users] SWIGging ConfigBase In-Reply-To: <42E8393F.7050609@pressure.to> References: <42E8393F.7050609@pressure.to> Message-ID: <42E9A637.2050805@qualitycode.com> Alex Fenton wrote: > Hi all > > I'm trying to write an .i file for ConfigBase. If I can figure out a few > general SWIG things then I think most of it will work. Apols for the > noob swig questions. We're all swig noobs here :-) ConfigBase is an interesting choice. Do you need it for compatibility with other wx apps? If not, I would think that one of the Ruby configuration storage packages (e.g. yaml) might be a better choice. > I'm having two problems. > > 1) How correctly to rename a method. I'm trying > > %rename("ReadBool") wxConfigBase::Read(wxString const &key, bool *d, > bool defaultVal); > > but it doesn't seem to give me a read_bool() method where I expect it. I recently did a %rename in Menu.i which looks like this: %rename(AppendItem) wxMenu::Append(wxMenuItem *item); > 2) How to deal with returning one of the parameters passed by ref, > rather than the c++ return value (which is always "true" if something > was read). I've tried, from the swig manual page on ruby > > void wxConfigBase::ReadBool(char *, bool *OUTPUT, bool); > > after my %rename directive, but again, no joy. Ah, that's a tricky one. Can you send what you have so far so I have something to look at and play with? This might be a case where it would be easier to extend the class with a couple little C++ functions that do the type conversion, and then have swig wrap those instead of the underlying methods. Thanks, Kevin From alex at pressure.to Fri Jul 29 03:51:50 2005 From: alex at pressure.to (Alex Fenton) Date: Fri Jul 29 03:46:11 2005 Subject: [Wxruby-users] SWIGging ConfigBase In-Reply-To: <42E9A637.2050805@qualitycode.com> References: <42E8393F.7050609@pressure.to> <42E9A637.2050805@qualitycode.com> Message-ID: <42E9E016.60706@pressure.to> > ConfigBase is an interesting choice. Do you need it for compatibility > with other wx apps? If not, I would think that one of the Ruby > configuration storage packages (e.g. yaml) might be a better choice. I did pick that one cos I need it to move an app from 0.6.0 to 2. But it does something that AFAIK no single ruby class does - i.e. a platform-independent interface to persistent settings. I'm not sure how the magic works - the registry on windows maybe? - but it's useful. YAML or similar would do for serialising settings, but I'd have to write code to create a .weft-qda-conf in $HOME or something portably. > I recently did a %rename in Menu.i which looks like this: > > %rename(AppendItem) wxMenu::Append(wxMenuItem *item); hmmm >> 2) How to deal with returning one of the parameters passed by ref, >> rather than the c++ return value (which is always "true" if something >> was read). I've tried, from the swig manual page on ruby >> >> void wxConfigBase::ReadBool(char *, bool *OUTPUT, bool); >> >> after my %rename directive, but again, no joy. > > > Ah, that's a tricky one. Can you send what you have so far so I have > something to look at and play with? Attached. All the Read methods are of a type, so if you could point me the way with one .. thanks alex -------------- next part -------------- # Copyright 2004 by Kevin Smith # released under the wxWidgets license # as part of the wxRuby project %include "../common.i" %include "../typemap.i" %module(directors="1") wxConfigBase %{ #include %} %ignore wxConfigBase::wxConfigBase(const wxString& appName = wxEmptyString, const wxString& vendorName = wxEmptyString); bool wxConfigBase::Read(char *, char *, char* *OUTPUT); %ignore wxConfigBase::Read(wxString const &key,long *l); %ignore wxConfigBase::Read(wxString const &key,long *l,long defaultVal); %rename("ReadBool") wxConfigBase::Read(wxString const &key, bool *d, bool defaultVal); void wxConfigBase::ReadBool(char *, bool *OUTPUT, bool); %ignore wxConfigBase::SetUmask(int mode); %include "include/wxConfigBase.h" From sean.m.long at gmail.com Sat Jul 30 16:28:50 2005 From: sean.m.long at gmail.com (Sean Long) Date: Sat Jul 30 16:23:05 2005 Subject: [Wxruby-users] Compiling on WinXP, MSVC In-Reply-To: <42E9A178.2090504@qualitycode.com> References: <42E455B1.1000809@qualitycode.com> <42E5515B.7090609@pressure.to> <42E5ACFD.40806@mindspring.com> <42E5ADE9.9060003@mindspring.com> <42E5B43C.9030009@mindspring.com> <42E9A178.2090504@qualitycode.com> Message-ID: > I really want to hear from other MSWin users about what the rakemswin.rb > file should look like before I make any changes. I suspect part of the > difference is that Sean is using a "monolithic" wx library, and you have > the new-style modular version. Actually if you look in extconf.rb on Windows the modular version is used look for the lines like: $WXLIB = "#$WXLIBDIR/wxbase26#{$DEBUG_BUILDPOSTFIX}.lib" $WXLIB += " #$WXLIBDIR/wxbase26#{$DEBUG_BUILDPOSTFIX}_net.lib" etc. > I would love the rakefile to auto-detect > which you have, and do the right thing. After all, part of the beauty of > rakefiles is that they are ruby code, so detecting should be a snap. The main problem with Windows is that it does not have the wx-config script like OS X and Linux, so we will have to do this in a rakefile. Sean From wxruby at qualitycode.com Sat Jul 30 17:39:16 2005 From: wxruby at qualitycode.com (Kevin Smith) Date: Sat Jul 30 17:33:40 2005 Subject: [Wxruby-users] wxruby2 and extconf.rb (was: Compiling on WinXP, MSVC) In-Reply-To: References: <42E455B1.1000809@qualitycode.com> <42E5515B.7090609@pressure.to> <42E5ACFD.40806@mindspring.com> <42E5ADE9.9060003@mindspring.com> <42E5B43C.9030009@mindspring.com> <42E9A178.2090504@qualitycode.com> Message-ID: <42EBF384.9060301@qualitycode.com> Sean Long wrote: > The main problem with Windows is that it does not have the wx-config > script like OS X and Linux, so we will have to do this in a rakefile. Exactly. Glancing at the extconf.rb, it looks it is doing almost exactly what rakemswin.rb already is doing (or needs to do). Unless there's some magic in extconf.rb that can't happen in rakemswin.rb, I *really* want to get rid of extconf.rb. If it really is necessary for some reason to keep extconf.rb, I want to move it out of src/, probably up to the project root directory. Let me know what you think. I also just now noticed that there is a version-script file in src/. It looks like Nick checked it in a long time ago, but I can't see where it is used. I also want to delete that, or find a better home for it. Kevin From nochoice at xs4all.nl Sat Jul 30 18:06:42 2005 From: nochoice at xs4all.nl (Jonathan Maasland) Date: Sat Jul 30 17:51:21 2005 Subject: [Wxruby-users] Can't compile the cvs-tree Message-ID: <42EBF9F2.30505@xs4all.nl> Hi folks, Let me start off by saying I've just been following wxruby development for two or three days now and have read up on alot on what has been going on. I must say I'm impressed and happy about all the things being developed and created by you guys! You got me all excited and I know I'm not the only one. If I have an opportunity to spend more time investigating Swig and wx I might even be able to help out somewhere I can..... who knows, I'd like it but like all of you guys I have a busy schedule :) Anyway, enough of that. The second reason for this email was that I'm having difficulty compiling the current source tree. I have done a cvs update right before writing this email just to be sure. I am running Gentoo and I have three versions of Wx installed: 2.4.2, 2.5.3 and 2.6.1 all of course compiled for GTK (using emerge) and the last two are I believe built with unicode support. In order to switch between versions I simply link my /usr/bin/wx-config to the approriate config-scripts. The result of this change clearly shows in the build commands issued. ------snips alot of text------- While typing this email and writing my initial problem down I noticed one small difference in Wx source-code of init.cpp and wxruby's App.i that I hadn't noticed before. After two evenings of reading and learning wx and wxruby code I found the solution to my compile problem after fifteen minutes of writing this email. The incredibly simple fix I made was to swig/classes/App.i on line 16 changed from: int wxEntry( int argc, char *argv[]); to: int wxEntry( int &argc, char *argv[]); :)) Writing things down in a different environment sometimes makes you see things you hadn't noticed before :) I am really happy atm! The only thing I don't understand is why I'm the first here to experience this. In the end it doesn't matter.... I hope this helped someone so far. ------ I waited with finishing and sending this email for the build to complete. Unfortunately it failed again. I'm really really exhausted atm so I'm just gonna lazily post the relevant output without doing some more digging: i686-pc-linux-gnu-g++ -c -I/usr/lib/wx/include/gtk-ansi-release-2.5 -I/usr/include/wx-2.5 -DGTK_NO_CHECK_CASTS -D__WXGTK__ -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -O2 -march=i686 -fPIC -I /usr/lib/ruby/site_ruby/1.8 -I /usr/lib/ruby/site_ruby/1.8/i686-linux -I /usr/lib/ruby/site_ruby -I /usr/lib/ruby/1.8 -I /usr/lib/ruby/1.8/i686-linux -I . -o obj/Sizer.o src/Sizer.cpp In file included from src/Sizer.cpp:1092: src/Sizer.h:25: error: conflicting return type specified for `virtual wxSizerItem* SwigDirector_wxSizer::Insert(unsigned int, wxSizerItem*)' /usr/include/wx-2.5/wx/sizer.h:324: error: overriding `virtual void wxSizer::Insert(unsigned int, wxSizerItem*)' src/Sizer.cpp: In member function `virtual wxSizerItem* SwigDirector_wxSizer::Insert(unsigned int, wxSizerItem*)': src/Sizer.cpp:1163: error: void value not ignored as it ought to be src/Sizer.cpp: In function `VALUE _wrap_wxSizer_Add__SWIG_0(int, VALUE*, long unsigned int)': src/Sizer.cpp:1248: error: cannot convert `arg1->wxSizer::Add(arg2, arg3, arg4, arg5, arg6)' from type `void' to type `wxSizerItem*' src/Sizer.cpp: In function `VALUE _wrap_wxSizer_Add__SWIG_1(int, VALUE*, long unsigned int)': It continues to give 'cannot convert' errors for all other methods (I think, it's a quite a list). Maybe I can find some time tommorow to look at this. However I don't think this fix will be as easy as the previous :( ----- I'm looking forward to your reactions. Thanks for wxruby! Jonathan Maasland From wxruby at qualitycode.com Sat Jul 30 19:30:03 2005 From: wxruby at qualitycode.com (Kevin Smith) Date: Sat Jul 30 19:24:31 2005 Subject: [Wxruby-users] Can't compile the cvs-tree In-Reply-To: <42EBF9F2.30505@xs4all.nl> References: <42EBF9F2.30505@xs4all.nl> Message-ID: <42EC0D7B.1020907@qualitycode.com> Jonathan Maasland wrote: > Hi folks, > > Let me start off by saying I've just been following wxruby development > for two or three days now and have read up on alot on what has been > going on. I must say I'm impressed and happy about all the things being > developed and created by you guys! You got me all excited and I know I'm > not the only one. Thanks. Words of support and encouragement are always appreciated. > I am running Gentoo and I have three versions of Wx installed: 2.4.2, > 2.5.3 and 2.6.1 all of course compiled for GTK (using emerge) and the > last two are I believe built with unicode support. Ok. I'm using 2.5.3 with unicode myself, so that's the one I would recommend you get working first. Based on your report below, I think that's what you're doing. > The incredibly simple fix I made was to swig/classes/App.i on line 16 > changed from: > int wxEntry( int argc, char *argv[]); > to: > int wxEntry( int &argc, char *argv[]); I just checked a simpler fix into CVS: We no longer manually prototype wxEntry at all. It's already declared in wx/init.h so we can just use that. > The only thing I don't understand is why I'm the first here to > experience this. In the end it doesn't matter.... I hope this helped > someone so far. I have no idea why that wasn't causing problems for me. > I waited with finishing and sending this email for the build to > complete. Unfortunately it failed again. I'm really really exhausted atm > so I'm just gonna lazily post the relevant output without doing some > more digging: Ok. > In file included from src/Sizer.cpp:1092: > src/Sizer.h:25: error: conflicting return type specified for `virtual > wxSizerItem* SwigDirector_wxSizer::Insert(unsigned int, wxSizerItem*)' > /usr/include/wx-2.5/wx/sizer.h:324: error: overriding `virtual void > wxSizer::Insert(unsigned int, wxSizerItem*)' > src/Sizer.cpp: In member function `virtual wxSizerItem* > SwigDirector_wxSizer::Insert(unsigned int, wxSizerItem*)': Hm. Your 2.5.3 sizer.h doesn't match mine. In mine, all the Insert methods return wxSizerItem pointers. Oddly, the 2.5.3 wx docs claim those methods return void. [...Researching...]. Ok, the wxWidgets CVS tree shows that the DEBIAN_2_5_3_2 tag includes a patch that causes wxSizer::Insert to return a wxSizerItem*. The vanilla WX_2_5_3 tag had them declared as void returns. Grrrrr. I'm still trying to figure out how to support different versions of wx where they have conflicting API's. If we put conditionals in the swig/classes/include/.h files, then the files in src/ will be version-dependent. That may be unavoidable, but I would sure like to either minimize it, or embrace it by having multiple src/ directories (src/2.5.3/ and src/2.6.1/ etc.). Hm. That's probably the way to go. Comments? Thanks, Kevin From wxruby at qualitycode.com Sat Jul 30 19:35:11 2005 From: wxruby at qualitycode.com (Kevin Smith) Date: Sat Jul 30 19:29:34 2005 Subject: [Wxruby-users] Patch for wxRuby2 In-Reply-To: References: <42E86CB6.1060006@qualitycode.com> <42EBF02A.50503@qualitycode.com> Message-ID: <42EC0EAF.7040806@qualitycode.com> (Copying the list, since I'm guessing you intended your reply to be public) Sean Long wrote: >>My other question stands: Do we still need to create the xrcid global >>function as a special case? > > Depends on how closely we want to follow wxWidgets c++ implementation. Ah. I just now noticed that in addition to the XmlResource::GetXRCID method, there is also a convenience macro named XRCID. Yes, we should support both. The XRCID macro can just go in Functions.i, so Xrc.i can still disappear. >>So can we kill off DateTime.i? > > My local copy and the copy I just got from CVS do not have DateTime.i > just the wxDateTime.h files. You are so right! No need to kill something that already doesn't exist. We'll leave wxDateTime out of wxruby2. > How about just a DateTime.i with a SWIG comment at the top saying not > to add this class? That would be the simple solution, not sure if SWIG > will process it correctly. I'll try something along those lines. Thanks, Kevin From wxruby at qualitycode.com Sat Jul 30 19:42:09 2005 From: wxruby at qualitycode.com (Kevin Smith) Date: Sat Jul 30 19:36:33 2005 Subject: [Wxruby-users] Fwd: fix Choice.cpp unicode string In-Reply-To: <42E43FF3.5040002@qualitycode.com> References: <29e1155305072412281ab845ff@mail.gmail.com> <29e11553050724124322e2434a@mail.gmail.com> <42E43FF3.5040002@qualitycode.com> Message-ID: <42EC1051.6070807@qualitycode.com> Kevin Smith wrote: > Jani Monoses wrote: > >> This is needed so that samples/etc/choice.rb shows the strings in the >> choice box. >> One of the few places that missed UTF8 convertion. >> > > Ah, yes. My goal would be that none of the class .i files would need to > contain typemaps or otherwise muck with low-level stuff like this. I'll > apply your patch (assuming it works for me), but will hope to find a > better long-term solution. I finally got around to checking in your temporary solution. Kevin From alex at pressure.to Sat Jul 30 21:58:41 2005 From: alex at pressure.to (Alex Fenton) Date: Sat Jul 30 21:52:56 2005 Subject: [Wxruby-users] classes to be ignored etc Message-ID: <42EC3051.2030402@pressure.to> Hi just a quick update on http://wxruby.rubyforge.org/wiki/wiki.pl?What_Classes_Are_Implemented_In_Wxruby I've added a clearer comparison of the two versions, plus info on classes that are being dropped or shouldn't be implemented b/c standard library is preferred. obviously these are up for discussion, just my view based on what's in ruby by default or easy to implement. Kevin - looking again at ConfigBase, I don't think it's worth porting. I plan to change the little bits of existing application code that use it before moving to wxruby2. But it was interesting, thanks for your help. I'm going back to work on TreeCtrl, of which I have a version that compiles and works but is missing methods. alex From roys at mindspring.com Sat Jul 30 22:52:05 2005 From: roys at mindspring.com (Roy Sutton) Date: Sat Jul 30 22:46:29 2005 Subject: [Wxruby-users] Latest checked in files Message-ID: <42EC3CD5.7050909@mindspring.com> The latest tarball appears to require SWIG to build. I'm guessing one of the swig output files is missing in the CVS. It stops here: NotebookEvent.cpp swig -noruntime -noextern -w401 -w801 -w515 -c++ -ruby -o src/NotebookSizer.cpp swig/classes/NotebookSizer.i Exception `RuntimeError' at c:/ruby/lib/ruby/gems/1.8/gems/rake-0.5.4/lib/rake.rb:485 - Command failed with status (0): [swig -noruntime -noextern -w401 -w801 -w...] rake aborted! Command failed with status (0): [swig -noruntime -noextern -w401 -w801 -w...] I had resisted installing swig until I got further into the project. Maybe I'll have to bite the bullet now. :) From roys at mindspring.com Sun Jul 31 00:18:23 2005 From: roys at mindspring.com (Roy Sutton) Date: Sun Jul 31 00:12:55 2005 Subject: [Wxruby-users] SWIG compilation Message-ID: <42EC510F.1030305@mindspring.com> The result of the compilation after installing swig results in lots of errors of the sort: WindowDisabler.obj : error LNK2001: unresolved external symbol _SWIG_Ruby_ConvertPtr I can see this is defined in rubydef.swg but I'm not sure why this isn't just included in the files that need it. Can any swig experts tell me what I need to do to progress? I'm using Swigwin 1.3.25, btw. From nochoice at xs4all.nl Sun Jul 31 07:12:57 2005 From: nochoice at xs4all.nl (Jonathan Maasland) Date: Sun Jul 31 06:57:35 2005 Subject: [Wxruby-users] Can't compile the cvs-tree In-Reply-To: <42EC0D7B.1020907@qualitycode.com> References: <42EBF9F2.30505@xs4all.nl> <42EC0D7B.1020907@qualitycode.com> Message-ID: <42ECB239.50603@xs4all.nl> Kevin Smith wrote: > I just checked a simpler fix into CVS: We no longer manually prototype > wxEntry at all. It's already declared in wx/init.h so we can just use > that. doh! of course :-) > Hm. Your 2.5.3 sizer.h doesn't match mine. In mine, all the Insert > methods return wxSizerItem pointers. Oddly, the 2.5.3 wx docs claim > those methods return void. [...Researching...]. Ok, the wxWidgets CVS > tree shows that the DEBIAN_2_5_3_2 tag includes a patch that causes > wxSizer::Insert to return a wxSizerItem*. The vanilla WX_2_5_3 tag had > them declared as void returns. Grrrrr. > > I'm still trying to figure out how to support different versions of wx > where they have conflicting API's. If we put conditionals in the > swig/classes/include/.h files, then the files in src/ will be > version-dependent. That may be unavoidable, but I would sure like to > either minimize it, or embrace it by having multiple src/ directories > (src/2.5.3/ and src/2.6.1/ etc.). Hm. That's probably the way to go. > Comments? > > Thanks, > > Kevin hmm.... indeed. This is quite a problem, I looked at the 2.6.1 code and it's broken (on multiple places) with 2.5.3. Building wxruby2 against 2.6 fails as well only at a different class now: ---- i686-pc-linux-gnu-g++ -c -I/usr/lib/wx/include/gtk2-ansi-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 -O2 -march=i686 -fPIC -I /usr/lib/ruby/site_ruby/1.8 -I /usr/lib/ruby/site_ruby/1.8/i686-linux -I /usr/lib/ruby/site_ruby -I /usr/lib/ruby/1.8 -I /usr/lib/ruby/1.8/i686-linux -I . -o obj/Icon.o src/Icon.cpp src/Icon.cpp: In constructor `SwigDirector_wxIcon::SwigDirector_wxIcon(long unsigned int, const wxString&, long int, int, int, bool)': src/Icon.cpp:789: error: invalid conversion from `long int' to `wxBitmapType' src/Icon.cpp:789: error: initializing argument 2 of `wxIcon::wxIcon(const wxString&, wxBitmapType, int, int)' src/Icon.cpp: In function `VALUE _wrap_new_wxIcon(int, VALUE*, long unsigned int)': src/Icon.cpp:847: error: invalid conversion from `long int' to `wxBitmapType' src/Icon.cpp:847: error: initializing argument 2 of `wxIcon::wxIcon(const wxString&, wxBitmapType, int, int)' ---- It does compile Sizer.i correctly however :)) Is there a specific and compelling reason you want to support the 2.5 release of wx? I think it'd be quite acceptable to require 2.6.1 especially because the 2.5 series is considered a development-branch. (see http://www.wxwidgets.org/roadmap.htm ) It would simplify matters greatly. If it's a matter of package availability, well we could always try to create and distribute the needed ones ourselves (just a thought). Thanks, Jonathan From nochoice at xs4all.nl Sun Jul 31 07:49:28 2005 From: nochoice at xs4all.nl (Jonathan Maasland) Date: Sun Jul 31 07:34:01 2005 Subject: [Wxruby-users] Can't compile the cvs-tree In-Reply-To: <42ECB239.50603@xs4all.nl> References: <42EBF9F2.30505@xs4all.nl> <42EC0D7B.1020907@qualitycode.com> <42ECB239.50603@xs4all.nl> Message-ID: <42ECBAC8.6020301@xs4all.nl> I hate to reply to myself but I just thought I'd update a bit on the compilation status. I removed Icon.(cpp h i) and the build finished succesfully. However running the samples gives me an ugly segmentation fault without any meaningful message or reason: ---- ruby -I lib/ samples/controls/controls.rb lib/wxruby2.so: [BUG] Segmentation fault ruby 1.8.2 (2004-12-25) [i686-linux] Aborted ---- Is there a way to set a debug flag or such so I can find out why and where it failed? Thanks again, Jonathan Jonathan Maasland wrote: >Kevin Smith wrote: > > > >>I just checked a simpler fix into CVS: We no longer manually prototype >>wxEntry at all. It's already declared in wx/init.h so we can just use >>that. >> >> > >doh! of course :-) > > > >>Hm. Your 2.5.3 sizer.h doesn't match mine. In mine, all the Insert >>methods return wxSizerItem pointers. Oddly, the 2.5.3 wx docs claim >>those methods return void. [...Researching...]. Ok, the wxWidgets CVS >>tree shows that the DEBIAN_2_5_3_2 tag includes a patch that causes >>wxSizer::Insert to return a wxSizerItem*. The vanilla WX_2_5_3 tag had >>them declared as void returns. Grrrrr. >> >>I'm still trying to figure out how to support different versions of wx >>where they have conflicting API's. If we put conditionals in the >>swig/classes/include/.h files, then the files in src/ will be >>version-dependent. That may be unavoidable, but I would sure like to >>either minimize it, or embrace it by having multiple src/ directories >>(src/2.5.3/ and src/2.6.1/ etc.). Hm. That's probably the way to go. >>Comments? >> >>Thanks, >> >>Kevin >> >> > >hmm.... indeed. This is quite a problem, I looked at the 2.6.1 code and >it's broken (on multiple places) with 2.5.3. Building wxruby2 against >2.6 fails as well only at a different class now: >---- >i686-pc-linux-gnu-g++ -c -I/usr/lib/wx/include/gtk2-ansi-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 -O2 >-march=i686 -fPIC -I /usr/lib/ruby/site_ruby/1.8 -I >/usr/lib/ruby/site_ruby/1.8/i686-linux -I /usr/lib/ruby/site_ruby -I >/usr/lib/ruby/1.8 -I /usr/lib/ruby/1.8/i686-linux -I . -o obj/Icon.o >src/Icon.cpp >src/Icon.cpp: In constructor `SwigDirector_wxIcon::SwigDirector_wxIcon(long > unsigned int, const wxString&, long int, int, int, bool)': >src/Icon.cpp:789: error: invalid conversion from `long int' to >`wxBitmapType' >src/Icon.cpp:789: error: initializing argument 2 of `wxIcon::wxIcon(const > wxString&, wxBitmapType, int, int)' >src/Icon.cpp: In function `VALUE _wrap_new_wxIcon(int, VALUE*, long unsigned > int)': >src/Icon.cpp:847: error: invalid conversion from `long int' to >`wxBitmapType' >src/Icon.cpp:847: error: initializing argument 2 of `wxIcon::wxIcon(const > wxString&, wxBitmapType, int, int)' >---- >It does compile Sizer.i correctly however :)) > >Is there a specific and compelling reason you want to support the 2.5 >release of wx? I think it'd be quite acceptable to require 2.6.1 >especially because the 2.5 series is considered a development-branch. >(see http://www.wxwidgets.org/roadmap.htm ) >It would simplify matters greatly. > >If it's a matter of package availability, well we could always try to >create and distribute the needed ones ourselves (just a thought). > >Thanks, >Jonathan >_______________________________________________ >wxruby-users mailing list >wxruby-users@rubyforge.org >http://rubyforge.org/mailman/listinfo/wxruby-users > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wxruby-users/attachments/20050731/1ea8dbd6/attachment-0001.htm From wxruby at qualitycode.com Sun Jul 31 12:07:07 2005 From: wxruby at qualitycode.com (Kevin Smith) Date: Sun Jul 31 12:01:32 2005 Subject: [Wxruby-users] classes to be ignored etc In-Reply-To: <42EC3051.2030402@pressure.to> References: <42EC3051.2030402@pressure.to> Message-ID: <42ECF72B.2080108@qualitycode.com> Alex Fenton wrote: > Hi > > just a quick update on > > http://wxruby.rubyforge.org/wiki/wiki.pl?What_Classes_Are_Implemented_In_Wxruby > > > I've added a clearer comparison of the two versions, plus info on > classes that are being dropped or shouldn't be implemented b/c standard > library is preferred. obviously these are up for discussion, just my > view based on what's in ruby by default or easy to implement. Nice. I see a few things I'll probably change at some point. The MBConv stuff will probably be needed for good unicode support, but I'll know more when I get back to that. Some classes like NotebookSizer have been deprecated in wx 2.5+, so we'll be dropping those from wxruby2. Still, it's a great list and is mostly accurate. > Kevin - looking again at ConfigBase, I don't think it's worth porting. Ok. Sounds good to me. If someone feels motivated later, I can help them add it. Otherwise we'll leave it out for now. Kevin From wxruby at qualitycode.com Sun Jul 31 12:09:48 2005 From: wxruby at qualitycode.com (Kevin Smith) Date: Sun Jul 31 12:04:06 2005 Subject: [Wxruby-users] Latest checked in files In-Reply-To: <42EC3CD5.7050909@mindspring.com> References: <42EC3CD5.7050909@mindspring.com> Message-ID: <42ECF7CC.7070608@qualitycode.com> Roy Sutton wrote: > swig -noruntime -noextern -w401 -w801 -w515 -c++ -ruby -o > src/NotebookSizer.cpp swig/classes/NotebookSizer.i > Exception `RuntimeError' at > c:/ruby/lib/ruby/gems/1.8/gems/rake-0.5.4/lib/rake.rb:485 - Command > failed with status (0): [swig -noruntime -noextern -w401 -w801 -w...] > rake aborted! > Command failed with status (0): [swig -noruntime -noextern -w401 -w801 > -w...] It looks like you still have swig/classes/NotebookSizer.i, but that file was recently removed from CVS because the class was deprecated in wx. If you delete that file (so your working tree matches the CVS tree), you should be able to continue the build without having swig. Kevin From wxruby at qualitycode.com Sun Jul 31 12:11:02 2005 From: wxruby at qualitycode.com (Kevin Smith) Date: Sun Jul 31 12:05:20 2005 Subject: [Wxruby-users] SWIG compilation In-Reply-To: <42EC510F.1030305@mindspring.com> References: <42EC510F.1030305@mindspring.com> Message-ID: <42ECF816.8030009@qualitycode.com> Roy Sutton wrote: > The result of the compilation after installing swig results in lots of > errors of the sort: > > WindowDisabler.obj : error LNK2001: unresolved external symbol > _SWIG_Ruby_ConvertPtr > > I can see this is defined in rubydef.swg but I'm not sure why this isn't > just included in the files that need it. Can any swig experts tell me > what I need to do to progress? I'm using Swigwin 1.3.25, btw. Hm. Are you using Ruby 1.6? I can't think of anything else off-hand, but if you tell me you're using Ruby 1.8 I can research it further. Kevin From wxruby at qualitycode.com Sun Jul 31 12:17:27 2005 From: wxruby at qualitycode.com (Kevin Smith) Date: Sun Jul 31 12:11:44 2005 Subject: [Wxruby-users] wxruby2: wx 2.6 only? Ubuntu wx 2.6 package? (was: Can't compile the cvs-tree) In-Reply-To: <42ECB239.50603@xs4all.nl> References: <42EBF9F2.30505@xs4all.nl> <42EC0D7B.1020907@qualitycode.com> <42ECB239.50603@xs4all.nl> Message-ID: <42ECF997.60006@qualitycode.com> Jonathan Maasland wrote: > > hmm.... indeed. This is quite a problem, I looked at the 2.6.1 code and > it's broken (on multiple places) with 2.5.3. Building wxruby2 against > 2.6 fails as well only at a different class now: > ---- > i686-pc-linux-gnu-g++ -c -I/usr/lib/wx/include/gtk2-ansi-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 -O2 > -march=i686 -fPIC -I /usr/lib/ruby/site_ruby/1.8 -I > /usr/lib/ruby/site_ruby/1.8/i686-linux -I /usr/lib/ruby/site_ruby -I > /usr/lib/ruby/1.8 -I /usr/lib/ruby/1.8/i686-linux -I . -o obj/Icon.o > src/Icon.cpp > src/Icon.cpp: In constructor `SwigDirector_wxIcon::SwigDirector_wxIcon(long > unsigned int, const wxString&, long int, int, int, bool)': > src/Icon.cpp:789: error: invalid conversion from `long int' to > `wxBitmapType' Hm. I thought Sean and I had fixed that already. I guess not. > Is there a specific and compelling reason you want to support the 2.5 > release of wx? Well, there is a specific and compelling selfish reason: I'm using Ubuntu Linux, and they offer wx 2.5.3 (Debian variant) in their standard package repository. I really hate installing libraries outside the apt package manager because it screws up all the dependency checking. > If it's a matter of package availability, well we could always try to > create and distribute the needed ones ourselves (just a thought). That's a good point. Since Ubuntu seems to be one of the few systems where 2.6 is not at least as available as 2.5, I should probably package up an Ubuntu 2.6. It's not enough for me to have it as a .DEB. I want it hosted at an apt repo somewhere on the internet. Fortunately, I recently learned how to host my own apt repo, so this now seems like an appealing option. Ok. I'm almost convinced that we should go with wx 2.6. Are there any volunteers to build an Ubuntu package that I could host? If not, I'll have to fumble through it myself, but assuming I can get it working, I'll drop 2.5 and everything will get much simpler. Thanks, Kevin From wxruby at qualitycode.com Sun Jul 31 12:21:33 2005 From: wxruby at qualitycode.com (Kevin Smith) Date: Sun Jul 31 12:15:50 2005 Subject: [Wxruby-users] Segfault running samples (was: Can't compile the cvs-tree) In-Reply-To: <42ECBAC8.6020301@xs4all.nl> References: <42EBF9F2.30505@xs4all.nl> <42EC0D7B.1020907@qualitycode.com> <42ECB239.50603@xs4all.nl> <42ECBAC8.6020301@xs4all.nl> Message-ID: <42ECFA8D.5060602@qualitycode.com> Jonathan Maasland wrote: > I removed Icon.(cpp h i) and the build finished succesfully. However > running the samples gives me an ugly segmentation fault without any > meaningful message or reason: > ---- > ruby -I lib/ samples/controls/controls.rb > lib/wxruby2.so: [BUG] Segmentation fault > ruby 1.8.2 (2004-12-25) [i686-linux] > > Aborted > ---- > Is there a way to set a debug flag or such so I can find out why and > where it failed? You can run it inside gdb, and at least get a stack trace. I'm no gdb expert but if I remember correctly, you would do something like: gdb ruby set args samples/controls/controls.rb run (program segfaults) bt You should definitely start with minimal, as it is the simplest sample we have. It's not quite truly minimal because it has an icon, menu bar, and status bar. You could try commenting those out, too. Kevin From roys at mindspring.com Sun Jul 31 16:53:50 2005 From: roys at mindspring.com (Roy Sutton) Date: Sun Jul 31 16:48:26 2005 Subject: [Wxruby-users] SWIG compilation In-Reply-To: <42ECF816.8030009@qualitycode.com> References: <42EC510F.1030305@mindspring.com> <42ECF816.8030009@qualitycode.com> Message-ID: <42ED3A5E.8070905@mindspring.com> I was a baaaaad boy. I just overlaid my last tarball with the most recent one. I really /should/ know better. I completely wiped my wxruby2 directory, but saved my modified rakemswin. It still doesn't work and still callls swig during compilation. It swigs the following file now: swig -runtime -w401 -w801 -w515 -c++ -ruby -o src/wx.cpp swig/wx.i SWIG(1): Warning(120): -c, -runtime, -noruntime command line options are deprecated. ruby swig/renamer.rb src/wx.cpp ruby swig/fixmainmodule.rb src/wx.cpp The link still fails at the end with all the _SWIG_Ruby_* undefined external symbols. This is with Ruby 1.8. I won't have any time tonight to look over this and my time is somewhat limited the early part of the week. Roy Kevin Smith wrote: > Roy Sutton wrote: > >> The result of the compilation after installing swig results in lots >> of errors of the sort: >> >> WindowDisabler.obj : error LNK2001: unresolved external symbol >> _SWIG_Ruby_ConvertPtr >> >> I can see this is defined in rubydef.swg but I'm not sure why this >> isn't just included in the files that need it. Can any swig experts >> tell me what I need to do to progress? I'm using Swigwin 1.3.25, btw. > > > Hm. Are you using Ruby 1.6? I can't think of anything else off-hand, > but if you tell me you're using Ruby 1.8 I can research it further. > > Kevin > _______________________________________________ > wxruby-users mailing list > wxruby-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-users > > > From wxruby at qualitycode.com Sun Jul 31 22:16:27 2005 From: wxruby at qualitycode.com (Kevin Smith) Date: Sun Jul 31 22:10:49 2005 Subject: [Wxruby-users] SWIG compilation In-Reply-To: <42ED3A5E.8070905@mindspring.com> References: <42EC510F.1030305@mindspring.com> <42ECF816.8030009@qualitycode.com> <42ED3A5E.8070905@mindspring.com> Message-ID: <42ED85FB.8020303@qualitycode.com> Roy Sutton wrote: > I was a baaaaad boy. I just overlaid my last tarball with the most > recent one. I really /should/ know better. I completely wiped my > wxruby2 directory, but saved my modified rakemswin. It still doesn't > work and still callls swig during compilation. It swigs the following > file now: > > swig -runtime -w401 -w801 -w515 -c++ -ruby -o src/wx.cpp swig/wx.i > SWIG(1): Warning(120): -c, -runtime, -noruntime command line options are > deprecated. > ruby swig/renamer.rb src/wx.cpp > ruby swig/fixmainmodule.rb src/wx.cpp Hm. Perhaps wx.i changed, but wx.h/cpp didn't, so my CVS didn't update the src/ files, but rake on your system doesn't realize they haven't changed. Ugh. Maybe I need to somehow tell CVS to check src/ in if any files have been touched, even if they haven't changed. I wonder if there's a way to do that on a per-directory basis. > The link still fails at the end with all the _SWIG_Ruby_* undefined > external symbols. This is with Ruby 1.8. I won't have any time tonight > to look over this and my time is somewhat limited the early part of the > week. That really sounds like it's not linking in swig itself. Can we see the link command that's being executed? Kevin From roys at mindspring.com Sun Jul 31 23:47:49 2005 From: roys at mindspring.com (Roy Sutton) Date: Sun Jul 31 23:42:12 2005 Subject: [Wxruby-users] SWIG compilation In-Reply-To: <42ED85FB.8020303@qualitycode.com> References: <42EC510F.1030305@mindspring.com> <42ECF816.8030009@qualitycode.com> <42ED3A5E.8070905@mindspring.com> <42ED85FB.8020303@qualitycode.com> Message-ID: <42ED9B65.5000003@mindspring.com> Kevin, Here's the link command: link /DEBUG /PDB:C:\RubyDev\wxWidgets-2.6.1/lib/vc_lib/vc60.pdb swig/wx.res obj/App.obj obj/ArtProvider.obj obj/Bitmap.obj obj/BitmapButton.obj obj/BoxSizer.obj obj/Brush.obj obj/BusyCursor.obj obj/BusyInfo.obj obj/Button.obj obj/CalendarCtrl.obj obj/CalendarDateAttr.obj obj/CalendarEvent.obj obj/Caret.obj obj/CheckBox.obj obj/CheckListBox.obj obj/Choice.obj obj/ClassInfo.obj obj/ClientDC.obj obj/CloseEvent.obj obj/Colour.obj obj/ColourData.obj obj/ColourDialog.obj obj/ComboBox.obj obj/CommandEvent.obj obj/Control.obj obj/ControlWithItems.obj obj/Cursor.obj obj/DC.obj obj/Dialog.obj obj/DirDialog.obj obj/Event.obj obj/EvtHandler.obj obj/FileDialog.obj obj/FindDialogEvent.obj obj/FindReplaceData.obj obj/FindReplaceDialog.obj obj/FlexGridSizer.obj obj/FocusEvent.obj obj/Font.obj obj/FontData.obj obj/FontDialog.obj obj/Frame.obj obj/GDIObject.obj obj/Gauge.obj obj/Grid.obj obj/GridCellBoolEditor.obj obj/GridCellChoiceEditor.obj obj/GridCellEditor.obj obj/GridCellFloatEditor.obj obj/GridCellNumberEditor.obj obj/GridCellTextEditor.obj obj/GridEvent.obj obj/GridRangeSelectEvent.obj obj/GridSizeEvent.obj obj/GridSizer.obj obj/Icon.obj obj/IdleEvent.obj obj/Image.obj obj/ImageList.obj obj/IndividualLayoutConstraint.obj obj/KeyEvent.obj obj/LayoutConstraints.obj obj/ListBox.obj obj/ListCtrl.obj obj/Log.obj obj/LogTextCtrl.obj obj/MDIChildFrame.obj obj/MDIParentFrame.obj obj/Mask.obj obj/MemoryDC.obj obj/Menu.obj obj/MenuBar.obj obj/MenuItem.obj obj/MessageDialog.obj obj/MouseEvent.obj obj/MoveEvent.obj obj/Notebook.obj obj/NotebookEvent.obj obj/NotifyEvent.obj obj/Object.obj obj/PaintDC.obj obj/PaintEvent.obj obj/Panel.obj obj/Pen.obj obj/Point.obj obj/ProgressDialog.obj obj/RadioBox.obj obj/RadioButton.obj obj/ScrolledWindow.obj obj/SingleChoiceDialog.obj obj/Size.obj obj/SizeEvent.obj obj/Sizer.obj obj/Slider.obj obj/SpinButton.obj obj/SpinCtrl.obj obj/SpinEvent.obj obj/SplitterEvent.obj obj/StaticBitmap.obj obj/StaticBox.obj obj/StaticBoxSizer.obj obj/StaticLine.obj obj/StaticText.obj obj/StatusBar.obj obj/TextCtrl.obj obj/TextEntryDialog.obj obj/TipProvider.obj obj/TipWindow.obj obj/ToggleButton.obj obj/ToolBar.obj obj/ToolTip.obj obj/TreeEvent.obj obj/UpdateUIEvent.obj obj/Window.obj obj/WindowDC.obj obj/WindowDisabler.obj obj/wx.obj obj/RubyConstants.obj obj/RubyStockObjects.obj obj/RubyEventTypes.obj obj/Functions.obj obj/Mac.obj obj/Events.obj obj/Xrc.obj C:\RubyDev\wxWidgets-2.6.1/lib/vc_lib/wxpngd.lib C:\RubyDev\wxWidgets-2.6.1/lib/vc_lib/wxzlibd.lib C:\RubyDev\wxWidgets-2.6.1/lib/vc_lib/wxjpegd.lib C:\RubyDev\wxWidgets-2.6.1/lib/vc_lib/wxtiffd.lib C:\RubyDev\wxWidgets-2.6.1/lib/vc_lib/wxbase26d.lib C:\RubyDev\wxWidgets-2.6.1/lib/vc_lib/wxmsw26d_adv.lib C:\RubyDev\wxWidgets-2.6.1/lib/vc_lib/wxmsw26d_xrc.lib C:\RubyDev\wxWidgets-2.6.1/lib/vc_lib/wxbase26d_xml.lib C:\RubyDev\wxWidgets-2.6.1/lib/vc_lib/wxexpatd.lib C:\RubyDev\wxWidgets-2.6.1/lib/vc_lib/wxmsw26d_core.lib oldnames.lib user32.lib advapi32.lib wsock32.lib gdi32.lib winspool.lib comdlg32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib comctl32.lib rpcrt4.lib winmm.lib c:/ruby/lib/msvcrt-ruby18.lib /dll /out:lib/wxruby2.so Exception `RuntimeError' at c:/ruby/lib/ruby/gems/1.8/gems/rake-0.5.4/lib/rake.rb:485 - Command failed with status (96): [link /DEBUG /PDB:C:\RubyDev\wxWidgets-2.6...] I should try compiling some of the example swig code to see how it all works I suppose. The odd thing is that this wasn't an issue until the latest tarball, so something in the latest files has changed this swig dynamic. Kevin Smith wrote: > Roy Sutton wrote: > >> I was a baaaaad boy. I just overlaid my last tarball with the most >> recent one. I really /should/ know better. I completely wiped my >> wxruby2 directory, but saved my modified rakemswin. It still doesn't >> work and still callls swig during compilation. It swigs the >> following file now: >> >> swig -runtime -w401 -w801 -w515 -c++ -ruby -o src/wx.cpp swig/wx.i >> SWIG(1): Warning(120): -c, -runtime, -noruntime command line options >> are deprecated. >> ruby swig/renamer.rb src/wx.cpp >> ruby swig/fixmainmodule.rb src/wx.cpp > > > Hm. Perhaps wx.i changed, but wx.h/cpp didn't, so my CVS didn't update > the src/ files, but rake on your system doesn't realize they haven't > changed. Ugh. Maybe I need to somehow tell CVS to check src/ in if any > files have been touched, even if they haven't changed. I wonder if > there's a way to do that on a per-directory basis. > >> The link still fails at the end with all the _SWIG_Ruby_* undefined >> external symbols. This is with Ruby 1.8. I won't have any time >> tonight to look over this and my time is somewhat limited the early >> part of the week. > > > That really sounds like it's not linking in swig itself. Can we see > the link command that's being executed? > > Kevin > _______________________________________________ > wxruby-users mailing list > wxruby-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-users > > >