A first draft of the wxruby binary release for the macintosh is now available at: http://www.nicreations.net/wxruby-0.2-osx-panther.dmg Install the metapackage (mpkg). You will need to choose a folder for the sample apps. wxruby.bundle is installed in /usr/lib/ruby/1.6/powerpc-darwin7.0 A few questions: 1) Should I just leave the samples in a folder instead of making the user ''install'' them? 2) How much interest is there in a Jaguar release? I can do it, but I wasn''t sure how many people were running it. Download it and break it so I can fix it. Sorry this took so long. Nick
On 8 Feb 2004, at 21:40, Nick wrote:> A first draft of the wxruby binary release for the macintosh is now > available at:Great.> Install the metapackage (mpkg). You will need to choose a folder for > the sample apps. wxruby.bundle is installed in > /usr/lib/ruby/1.6/powerpc-darwin7.0I didn''t. Hm. Did I have to press "customize" button ? The hardcoded path doesn''t work for me. I run a self compiled 1.8.1 in /usr/local . Running ruby and getting the install path should be easy, though I don''t know how. But after I copied the bundle I got it to work (great)> 1) Should I just leave the samples in a folder instead of making the > user ''install'' them?> Download it and break it so I can fix it.I find the Readme.osx could be clearer. Also the src tool could just be bundled. The first question that comes to me is "Where do I click to see it working". Even I knew about the Scr Tool it took me a while to figure. For that tool (and maybe generally) I had to put a bang into each example I wanted to run (#!/usr/bin/env ruby). I guess it wouldn''t harm to put them there anyway. If my working directory wasn''t the example directory, pictures were not loaded and it said something like file handler of type 9 not installed. A very confusing message. The few examples I tried worked (listctrl, calendar) though TreeCtrl did not open and crash on a right click. Good work, Torsten
Torsten Rueger wrote:> On 8 Feb 2004, at 21:40, Nick wrote: > >> A first draft of the wxruby binary release for the macintosh is now >> available at: > > > Great. > >> Install the metapackage (mpkg). You will need to choose a folder for >> the sample apps. wxruby.bundle is installed in >> /usr/lib/ruby/1.6/powerpc-darwin7.0 > > > I didn''t. Hm. Did I have to press "customize" button ?It''s on the second panel, when you pick your drive, there is a ''pick your folder'' option.> > The hardcoded path doesn''t work for me. I run a self compiled 1.8.1 in > /usr/local . Running ruby and getting the install path should be easy, > though I don''t know how. > > But after I copied the bundle I got it to work (great)I designed it to work with the default version of ruby that comes with OS X - in fact I''m a little shocked it worked with Ruby 1.8.1 at all as I compiled it for 1.6.7. This must be that ''dynamic binding'' all the kids are talking about.> >> 1) Should I just leave the samples in a folder instead of making the >> user ''install'' them? > > > >> Download it and break it so I can fix it. > > > I find the Readme.osx could be clearer. Also the src tool could just > be bundled. > The first question that comes to me is "Where do I click to see it > working". Even I knew about the Scr Tool it took me a while to figure.Very true. I need to change the permissions on the scripts to be executable. Most of my testing was from using the command line. Did you see any Menu Bars with ScrUI? I added a hack into wxruby so that ScrUI is no longer necessary, but since libwx_mac_2.4.rsrc isn''t in the bundle I couldn''t control the MenuBar. I''m planning to attack this for version 0.3.> > For that tool (and maybe generally) I had to put a bang into each > example I wanted to run (#!/usr/bin/env ruby). I guess it wouldn''t > harm to put them there anyway.Well, that gets difficult, simply because the scripts need to run on both Linux and Mac. Linux distros are notorious for putting things in random locations.> > If my working directory wasn''t the example directory, pictures were > not loaded and it said something like file handler of type 9 not > installed. A very confusing message.I was trying the samples from the command line (ruby sample.rb), so I really wasn''t testing from ScrUI. A lot of the issues with the samples can be fixed by bundling them, but it took me a long time to get to this point (Job has been eating a lot of time recently). Which do you think is the best to recommend - command line, ScrUI, or bundling?> > The few examples I tried worked (listctrl, calendar) though TreeCtrl > did not open and crash on a right click.Ok, I''ve never seen that. I''ll check it out.> > Good work, > > Torsten > > _______________________________________________ > wxruby-users mailing list > wxruby-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-users > >
On 9 Feb 2004, at 16:58, Nick wrote:> > It''s on the second panel, when you pick your drive, there is a ''pick > your folder'' option.I only have one drive. So that was chosen correctly, so I didn''t change. What I''m saying is, could that be made clearer ?> in fact I''m a little shocked it worked with Ruby 1.8.1 at all as I > compiled it for 1.6.7.Well I do get a lot of warnings like : /usr/local/lib/ruby/site_ruby/1.8/powerpc-darwin/wxruby.bundle: warning: defining Wx::DataFormat.allocate is deprecated; use rb_define_alloc_func()> Most of my testing was from using the command line.Very cool. I didn''t even try that before. But it works ! Put it big and loud in the README, because usually in os x commandline applications can''t have a UI. That''s another reason I was saying about the clicking.> Did you see any Menu Bars with ScrUI?I see the same "ruby" Menu with both. I can really only quit from there, though the services and stuff are there too.> I added a hack into wxruby so that ScrUI is no longer necessary, but > since libwx_mac_2.4.rsrc isn''t in the bundle I couldn''t control the > MenuBar.Very nice. BTW I have a separate wxWindows installation in /usr/local/ , does that interfere ?>> For that tool (and maybe generally) I had to put a bang into each >> example I wanted to run (#!/usr/bin/env ruby). I guess it wouldn''t >> harm to put them there anyway. > > Well, that gets difficult, simply because the scripts need to run on > both Linux and Mac. Linux distros are notorious for putting things in > random locations.That''s why I suggested the /usr/bin/env approach. I think that''s as portable as it gets. Sure /usr/local/bin/ruby or something might be a problem.> was trying the samples from the command line (ruby sample.rb), so I > really wasn''t testing from ScrUI.Same issue. It''s the samples that would need to be "fixed" to check the path a little.> but it took me a long time to get to this pointGood job.> Which do you think is the best to recommend - command line, ScrUI, or > bundling?Commandline is fine if it works. SrcUI only if the association could be made to work, ie no editing of paths and just click. As it stands, commandline. Torsten
> The few examples I tried worked (listctrl, calendar) though TreeCtrl > did not open and crash on a right click.Was that a ruby exception or a segfault style crash? Which example did it happen on? Nick Torsten Rueger wrote:> On 8 Feb 2004, at 21:40, Nick wrote: > >> A first draft of the wxruby binary release for the macintosh is now >> available at: > > > Great. > >> Install the metapackage (mpkg). You will need to choose a folder for >> the sample apps. wxruby.bundle is installed in >> /usr/lib/ruby/1.6/powerpc-darwin7.0 > > > I didn''t. Hm. Did I have to press "customize" button ? > > The hardcoded path doesn''t work for me. I run a self compiled 1.8.1 in > /usr/local . Running ruby and getting the install path should be easy, > though I don''t know how. > > But after I copied the bundle I got it to work (great) > >> 1) Should I just leave the samples in a folder instead of making the >> user ''install'' them? > > > >> Download it and break it so I can fix it. > > > I find the Readme.osx could be clearer. Also the src tool could just > be bundled. > The first question that comes to me is "Where do I click to see it > working". Even I knew about the Scr Tool it took me a while to figure. > > For that tool (and maybe generally) I had to put a bang into each > example I wanted to run (#!/usr/bin/env ruby). I guess it wouldn''t > harm to put them there anyway. > > If my working directory wasn''t the example directory, pictures were > not loaded and it said something like file handler of type 9 not > installed. A very confusing message. > > The few examples I tried worked (listctrl, calendar) though TreeCtrl > did not open and crash on a right click. > > Good work, > > Torsten > > _______________________________________________ > wxruby-users mailing list > wxruby-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-users > >
On 12 Feb 2004, at 01:30, Nick wrote:> Was that a ruby exception or a segfault style crash? Which example did > it happen on? >I clicked around a little more on treectrl . I actually do get it to expand, but I have to be sooo precise with the clicking. Only around two square pixels near the back of the arrow make it happen, where the asterix is below. |\ | \ *| > Node name | / | / I can get a context menu now. That''s new. But when I right click somewhere else, then usually the next click anywhere will cause the app to disappear silently. But now that I start from the console I get the stack: treetest.rb:669:in `onRMouseUp'': undefined method `get_position'' for #<Wx::MouseEvent:0x34310c> (NoMethodError) from treetest.rb:105:in `initialize'' from treetest.rb:105:in `call'' from treetest.rb:1231:in `main_loop'' from treetest.rb:1231 Good luck with this, Torsten BTW: this is what I get also on startup: ## Component Manager: attempting to find symbols in a component alias of type (regR/carP/x!bt)