SWIG 1.3.29 isn''t going to cut it for us. We''ll have to wait until 1.3.30, unless I can hack together a nasty workaround for a problem with the object tracking. It seem that each SWIG module gets its own hash for tracking objects. This means that, for example, you create a find dialog (in FindReplaceDialog.cpp) events you get from it (from FindDialogEvent.cpp) won''t be the same Ruby object, because those two modules don''t share the same hash table. We''re getting painfully close now, though. I think I know how this is supposed to work and will be able to have some things working soon. The lack of unit tests is beginning to bug me. I think I''ll see if I can begin hooking in unit tests so we can start validating the new things we''re doing. Roy
On Tue, 2006-04-18 at 01:33 -0400, Roy Sutton wrote:> SWIG 1.3.29 isn''t going to cut it for us. We''ll have to wait until > 1.3.30, unless I can hack together a nasty workaround for a problem with > the object tracking.Ugh. If true, it sounds like I shouldn''t check in my current changes. Or at least I should check in the wx 2.6.3 stuff, but not the swig 1.3.29 stuff. I don''t suppose it''s easy to disable the new swig memory tracking code.> It seem that each SWIG module gets its own hash > for tracking objects.Hm. I sure wish SWIG would support multiple-module linking. We could give in to swig''s wishes and cram every wx .i file into one single .cpp file. It would be a huge file (maybe 300k?) that would take forever to compile. But it would avoid one of our post-processing steps. Can you point to the swig code in question? So far I''ve been pretty successful at finding inexpensive ways to tweak the swig output to do what we want.> The lack of unit tests is beginning to bug me. I think I''ll see if I > can begin hooking in unit tests so we can start validating the new > things we''re doing.That would be fantastic! Kevin
Kevin Smith wrote:> On Tue, 2006-04-18 at 01:33 -0400, Roy Sutton wrote: > >> SWIG 1.3.29 isn''t going to cut it for us. We''ll have to wait until >> 1.3.30, unless I can hack together a nasty workaround for a problem with >> the object tracking. >> > > Ugh. If true, it sounds like I shouldn''t check in my current changes. Or > at least I should check in the wx 2.6.3 stuff, but not the swig 1.3.29 > stuff. I don''t suppose it''s easy to disable the new swig memory tracking > code. >Object tracking is purely optional. I am hacking around theirs with a bit of the fixmodules.rb magic. However, it''s not really how I want things done.>> It seem that each SWIG module gets its own hash >> for tracking objects. >> > > Hm. I sure wish SWIG would support multiple-module linking. We could > give in to swig''s wishes and cram every wx .i file into one single .cpp > file. It would be a huge file (maybe 300k?) that would take forever to > compile. But it would avoid one of our post-processing steps. > > Can you point to the swig code in question? So far I''ve been pretty > successful at finding inexpensive ways to tweak the swig output to do > what we want. >The SWIG code in question is in rubytracking.swg. swig_ruby_trackings and swig_ruby_hash_delete are static. I also notified them of the swig_up ''bug'' if you have multiple modules. I don''t think it is asking too much for multi-module support out of the box. Of course, if they fix it, it''ll break ours, but at least we might not have to have so many post-SWIG fixups.>> The lack of unit tests is beginning to bug me. I think I''ll see if I >> can begin hooking in unit tests so we can start validating the new >> things we''re doing. >> > > That would be fantastic! >First test for getting the same object back you put in seems to be working! One test down, ??? to go.> Kevin >Roy
Kevin Smith wrote:> Ugh. If true, it sounds like I shouldn''t check in my current changes. Or > at least I should check in the wx 2.6.3 stuff, but not the swig 1.3.29 > stuff.What 1.3.29 specific stuff wouldn''t be compatible with either future or past versions of SWIG? I agree we need to ''drop anchor'' on a SWIG version at some point. Object tracking looks to be implementable with external (to SWIG) changes and I think the upcoming changes to mark/free that Charlie Savage spoke of may be as well. Can you drop your changes into an archive and either mail the list or place onto a Web site so I can take a look? Roy
On Tue, 2006-04-18 at 10:26 -0400, Roy Sutton wrote:> What 1.3.29 specific stuff wouldn''t be compatible with either future or > past versions of SWIG?All of our post-processing is fairly swig-version-specific. It''s really had to predict what might or might not work with any earlier or later version of swig. It would have to be tested, and it''s hard (and very slow) to test multiple swig versions.> Can you drop your changes > into an archive and either mail the list or place onto a Web site so I > can take a look?Ok. I''ll try to check it all in tonight. At least on my machine, it compiles, and at least some of the samples run. They tend to crash randomly, though, probably due to the object deletion tracking. Kevin
Any news on the checkin? Roy Kevin Smith wrote:> On Tue, 2006-04-18 at 10:26 -0400, Roy Sutton wrote: > >> What 1.3.29 specific stuff wouldn''t be compatible with either future or >> past versions of SWIG? >> > > All of our post-processing is fairly swig-version-specific. It''s really > had to predict what might or might not work with any earlier or later > version of swig. It would have to be tested, and it''s hard (and very > slow) to test multiple swig versions. > > >> Can you drop your changes >> into an archive and either mail the list or place onto a Web site so I >> can take a look? >> > > Ok. I''ll try to check it all in tonight. At least on my machine, it > compiles, and at least some of the samples run. They tend to crash > randomly, though, probably due to the object deletion tracking. > > Kevin > > > _______________________________________________ > wxruby-users mailing list > wxruby-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-users > > > >
On Thu, 2006-04-20 at 18:48 -0400, Roy Sutton wrote:> Any news on the checkin?:-) Just before checking my email and finding your message, I finished the checkin. I tagged it as 0.0.31, and noted in the README and Changelog that it is VERY UNSTABLE. The Changelog has a comprehensive list of all the changes I made to get it to compile and somewhat work with wxWidgets 2.6.3 and SWIG 1.3.29. Hopefully we can stabilize it quickly. Kevin
Great work, Kevin! I''m compiling now and it looks good except for one thing: TextCtrl doesn''t have a function called overflow (on Windows). I will submit a patch with that removed shortly if everything else compiles OK. Roy Kevin Smith wrote:> On Thu, 2006-04-20 at 18:48 -0400, Roy Sutton wrote: > >> Any news on the checkin? >> > > :-) > > Just before checking my email and finding your message, I finished the > checkin. I tagged it as 0.0.31, and noted in the README and Changelog > that it is VERY UNSTABLE. > > The Changelog has a comprehensive list of all the changes I made to get > it to compile and somewhat work with wxWidgets 2.6.3 and SWIG 1.3.29. > > Hopefully we can stabilize it quickly. > > Kevin > > > _______________________________________________ > wxruby-users mailing list > wxruby-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-users > > > >
I ran into that the TextCtrl overflow problem compiling on Mac OS X, I only have wx2.6.2 installed and thought that was the problem. Going to install wx2.6.3 before testing it again. Sean On 4/20/06, Roy Sutton <roys at mindspring.com> wrote:> Great work, Kevin! I''m compiling now and it looks good except for one > thing: TextCtrl doesn''t have a function called overflow (on Windows). > I will submit a patch with that removed shortly if everything else > compiles OK. > > Roy > > Kevin Smith wrote: > > On Thu, 2006-04-20 at 18:48 -0400, Roy Sutton wrote: > > > >> Any news on the checkin? > >> > > > > :-) > > > > Just before checking my email and finding your message, I finished the > > checkin. I tagged it as 0.0.31, and noted in the README and Changelog > > that it is VERY UNSTABLE. > > > > The Changelog has a comprehensive list of all the changes I made to get > > it to compile and somewhat work with wxWidgets 2.6.3 and SWIG 1.3.29. > > > > Hopefully we can stabilize it quickly. > > > > Kevin > > > > > > _______________________________________________ > > wxruby-users mailing list > > wxruby-users at rubyforge.org > > http://rubyforge.org/mailman/listinfo/wxruby-users > > > > > > > > > _______________________________________________ > wxruby-users mailing list > wxruby-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-users >
Hmm, it also fails to link. It appears to be pulling in the ruby tracking code even though I did not yet re-add the %trackobjects to any SWIG files. Curiouser and curiouser. I have a patch to the cleanup file which can fix the trackobjects. Roy Kevin Smith wrote:> On Thu, 2006-04-20 at 18:48 -0400, Roy Sutton wrote: > >> Any news on the checkin? >> > > :-) > > Just before checking my email and finding your message, I finished the > checkin. I tagged it as 0.0.31, and noted in the README and Changelog > that it is VERY UNSTABLE. > > The Changelog has a comprehensive list of all the changes I made to get > it to compile and somewhat work with wxWidgets 2.6.3 and SWIG 1.3.29. > > Hopefully we can stabilize it quickly. > > Kevin > > > _______________________________________________ > wxruby-users mailing list > wxruby-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-users > > > >
I forgot to mention that I''m targeting wx unicode myself. I assume we
also want it to work with non-unicode builds, but I think unicode is
preferred.
This weekend, I''m hoping to apply the dangling patches that have come
in
over the last few months (like /darwin/ in the rakefile). So if y''all
(Roy and Sean) could submit any new patches soon, that would be great.
I''ll take them in darcs or diff/patch format, or even just as a
description in English ("I removed the Xxx method").
Kevin
On Thu, 2006-04-20 at 20:49 -0700, Sean Long wrote:> I ran into that the TextCtrl overflow problem compiling on Mac OS X, I
> only have wx2.6.2 installed and thought that was the problem. Going to
> install wx2.6.3 before testing it again.
>
> Sean
>
> On 4/20/06, Roy Sutton <roys at mindspring.com> wrote:
> > Great work, Kevin! I''m compiling now and it looks good
except for one
> > thing: TextCtrl doesn''t have a function called overflow (on
Windows).
> > I will submit a patch with that removed shortly if everything else
> > compiles OK.
> >
> > Roy
> >
> > Kevin Smith wrote:
> > > On Thu, 2006-04-20 at 18:48 -0400, Roy Sutton wrote:
> > >
> > >> Any news on the checkin?
> > >>
> > >
> > > :-)
> > >
> > > Just before checking my email and finding your message, I
finished the
> > > checkin. I tagged it as 0.0.31, and noted in the README and
Changelog
> > > that it is VERY UNSTABLE.
> > >
> > > The Changelog has a comprehensive list of all the changes I made
to get
> > > it to compile and somewhat work with wxWidgets 2.6.3 and SWIG
1.3.29.
> > >
> > > Hopefully we can stabilize it quickly.
> > >
> > > Kevin
> > >
> > >
> > > _______________________________________________
> > > wxruby-users mailing list
> > > wxruby-users at rubyforge.org
> > > http://rubyforge.org/mailman/listinfo/wxruby-users
> > >
> > >
> > >
> > >
> > _______________________________________________
> > wxruby-users mailing list
> > wxruby-users at rubyforge.org
> > http://rubyforge.org/mailman/listinfo/wxruby-users
> >
>
> _______________________________________________
> wxruby-users mailing list
> wxruby-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/wxruby-users
Here is the first one in english: in rakeutil.rb change: $macosx = /powerpc-darwin/ =~ RUBY_PLATFORM to: $macosx = /darwin/ =~ RUBY_PLATFORM and then Mac OS X will be detected on PPC and Intel Macs Sean On 4/21/06, Kevin Smith <wxruby at qualitycode.com> wrote:> I forgot to mention that I''m targeting wx unicode myself. I assume we > also want it to work with non-unicode builds, but I think unicode is > preferred. > > This weekend, I''m hoping to apply the dangling patches that have come in > over the last few months (like /darwin/ in the rakefile). So if y''all > (Roy and Sean) could submit any new patches soon, that would be great. > I''ll take them in darcs or diff/patch format, or even just as a > description in English ("I removed the Xxx method"). > > Kevin > > > On Thu, 2006-04-20 at 20:49 -0700, Sean Long wrote: > > I ran into that the TextCtrl overflow problem compiling on Mac OS X, I > > only have wx2.6.2 installed and thought that was the problem. Going to > > install wx2.6.3 before testing it again. > > > > Sean > > > > On 4/20/06, Roy Sutton <roys at mindspring.com> wrote: > > > Great work, Kevin! I''m compiling now and it looks good except for one > > > thing: TextCtrl doesn''t have a function called overflow (on Windows). > > > I will submit a patch with that removed shortly if everything else > > > compiles OK. > > > > > > Roy > > > > > > Kevin Smith wrote: > > > > On Thu, 2006-04-20 at 18:48 -0400, Roy Sutton wrote: > > > > > > > >> Any news on the checkin? > > > >> > > > > > > > > :-) > > > > > > > > Just before checking my email and finding your message, I finished the > > > > checkin. I tagged it as 0.0.31, and noted in the README and Changelog > > > > that it is VERY UNSTABLE. > > > > > > > > The Changelog has a comprehensive list of all the changes I made to get > > > > it to compile and somewhat work with wxWidgets 2.6.3 and SWIG 1.3.29. > > > > > > > > Hopefully we can stabilize it quickly. > > > > > > > > Kevin > > > > > > > > > > > > _______________________________________________ > > > > wxruby-users mailing list > > > > wxruby-users at rubyforge.org > > > > http://rubyforge.org/mailman/listinfo/wxruby-users > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > wxruby-users mailing list > > > wxruby-users at rubyforge.org > > > http://rubyforge.org/mailman/listinfo/wxruby-users > > > > > > > _______________________________________________ > > wxruby-users mailing list > > wxruby-users at rubyforge.org > > http://rubyforge.org/mailman/listinfo/wxruby-users > > _______________________________________________ > wxruby-users mailing list > wxruby-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-users >
On Fri, 2006-04-21 at 08:19 -0700, Sean Long wrote:> Here is the first one in english: > > in rakeutil.rb > change: > $macosx = /powerpc-darwin/ =~ RUBY_PLATFORM > to: > $macosx = /darwin/ =~ RUBY_PLATFORM > > and then Mac OS X will be detected on PPC and Intel MacsChecked in. Thanks. Kevin