rubycocoa-talk

[Rubycocoa-talk] Getting at the "Param" argument to RBApplicationInit

[Scott T. <ea...@ma...>]

On Mac OS X (Leopard), I'm trying to embed Ruby into an Objective-C application (as opposed to writing a Cocoa application in Ruby).  I've got it working, but I was curious about one aspect.

To initialize Ruby, I'm calling RBApplicationInit to initialize Ruby.  I know how to get at the argc and argv parameters, but the last parameter, the "id" valued parameter... how is that passed to the Ruby script named in the first parameter of RBApplicationInit?

Scott

Re: [Rubycocoa-talk] Getting at the "Param" argument to RBApplicationInit

[kimura w. <ki...@us...>]

Hi,

I think RBBundleInit() is suited for your purpose.
The interface of RBBundleInit is like this.

  // <RubyCocoa/RBRuntime.h>
  int RBBundleInit (const char* path_to_ruby_program,
                    Class       objc_class, 
                    id          additional_param);
                  
  - path_to_ruby_program:
    path of ruby script in the bundle. e.g. "main.rb".
    RubyCocoa expects the path as related path from Resources/.

  - objc_class:
    an ObjC class to specify your bundle. e.g. AppDelegate.

  - additional_param:
    you can pass nil.

On Sat, 22 Mar 2008 22:32:19 -0700, Scott Thompson wrote:
> On Mac OS X (Leopard), I'm trying to embed Ruby into an Objective-C 
> application (as opposed to writing a Cocoa application in Ruby).  
> I've got it working, but I was curious about one aspect.
> 
> To initialize Ruby, I'm calling RBApplicationInit to initialize 
> Ruby.  I know how to get at the argc and argv parameters, but the 
> last parameter, the "id" valued parameter... how is that passed to 
> the Ruby script named in the first parameter of RBApplicationInit?
> 
> Scott

Re: [Rubycocoa-talk] Getting at the "Param" argument to RBApplicationInit

[Scott T. <ea...@ma...>]

On Mar 25, 2008, at 8:52 AM, kimura wataru wrote:

> Hi,
>
> I think RBBundleInit() is suited for your purpose.
> The interface of RBBundleInit is like this.
>
>  // <RubyCocoa/RBRuntime.h>
>  int RBBundleInit (const char* path_to_ruby_program,
>                    Class       objc_class,
>                    id          additional_param);
>
>  - path_to_ruby_program:
>    path of ruby script in the bundle. e.g. "main.rb".
>    RubyCocoa expects the path as related path from Resources/.
>
>  - objc_class:
>    an ObjC class to specify your bundle. e.g. AppDelegate.
>
>  - additional_param:
>    you can pass nil.

Thank you.  I will try it.

However.  I don't want to pass "nil" as the additional_param, I want  
to pass an object. Inside of my Ruby program, how do I find the object  
that I pass into the additional_param parameter?

Scott

Re: [Rubycocoa-talk] Getting at the "Param" argument to RBApplicationInit

[Scott T. <ea...@ma...>]

> Thank you.  I will try it.
>
> However.  I don't want to pass "nil" as the additional_param, I want
> to pass an object. Inside of my Ruby program, how do I find the object
> that I pass into the additional_param parameter?


To answer my own question, after looking at samples on the web that  
use RBBundleInit, it appears that the invocation I was missing is this:

require 'osx/cocoa'
OSX.init_for_bundle do |bundle, additional_param, consoleLog|
   # bundle - The bundle being initialized.  Presumably an NSBundle?   
Passed as second param to RBBundleInit
   # additional_param  - Whatever you passed to RBBundleInit in the  
third parameter
   # consoleLog    - Used to pass NSLog messages to the console
   # ...do something here...
end
Experimentally, I was able to determine that I can use a similar block  
with RBApplicationInit.  However, since I have no real need to get at  
command line arguments, and given that this mechanism was recommended  
here, I'll stick with this.
Scott