On Jul 28, 2007, at 4:01 PM, 12 34 wrote:

> matt neuburg wrote:
>> 12 34 <rubyforum / web.knobby.ws> wrote:
>>
>>>
>>> I am missing that when creating an AppleScript app
>>> that after creating the UI (in IB), XCode creates such things "on  
>>> awake
>>> from nib" and "on clicked" which got me over one big hump. I'm  
>>> looking
>>> for something similar for Ruby--RubyCocoa doesn't seem to do this
>>
> Maybe I'm misremembering, but I thought XCode created the on clicks,
> etc. automatically which gave a framework to put in the AS script
> pieces. But I'd better look at this again in both AS and RubyCocoa  
> apps.
> But what I understood in my RubyCocoa reading was that the user had to
> create all the links to the UI.
>
>> You're wrong about that. RubyCocoa is Cocoa; indeed, you get far  
>> *more*
>> events / notifications than you do with AppleScript Studio.
>>
> I think I get that, but to me it looks like another language to learn.
> But as I said in another response I may do it.
>
>> If I were doing what you are doing, though I would just write a  
>> native
>> Objective-C Cocoa app with the Ruby script built in, calling the Ruby
>> script thru NSTask at the appropriate moment. You could in fact do  
>> the
>> same thing with AppleScript Studio, just as in the example in my book
>> where AppleScript suddenly turns to Perl to do some heavy lifting.
>>
>> m.
> Matt
>
> If I knew Obj-C I'd probably have enough experience to handle Cocoa
> easily. I'm afraid there's too much interaction with the Ruby  
> script to
> make the going back and forth to AS worthwhile, but I'll consider it.
> Just to confirm, you're talking about Chap. 23, p.364 "Do shell  
> script"?
>
> BTW, it was your article on Ruby that got me to dive into Ruby.
> -- 
> Posted via http://www.ruby-forum.com/.
>
Been a while since I messed with Obj-C and Cocoa, but as I remember,  
yes, InterfaceBuilder and XCode together can somehow or other  
generate a lot of the glue. but I am out the loop on that stuff now.