Re: [Rubycocoa-talk] Calling Ruby from existing Cocoa App

[Jonathan P. <jp...@dc...>]

On 31 Jan 2006, at 17:26, David wrote:

> I had came to this solution as well when testing and it does work.   
> I would have thought though that this could be encapsulated into an  
> RBObject class so that you can hide some of this and do some sanity  
> checks as well?  There is a initWithRubyObject in RBObject but  
> would it be useful to have a initWithRubyObjectName?

Can you give an example of how you'd like/expect things to work? I'm  
not quite clear on it yet.

> I was also thinking that with XCode it should be possible to write  
> a script that will read your ruby files and generate an objc  
> interface file for them each time you build..  that would be cool..

Certainly possible - although how useful it is depends on how broad  
your interface is going to be. If there are relatively few entry  
points into ruby then it's probably easy enough to keep two files up  
to date (as you would have to do anyway with a plain objc header and  
implementation).

Cheers,
Jonathan