Re: [Rubycocoa-talk] Objective-C Ubiquity?

[Dave H. <gr...@gr...>]

On Jun 5, 2005, at 2:38 PM, Sam Roberts wrote:

> I don't think you can use ruby cocoa without having a basic
> understanding of cocoa coding

That makes sense.

> with obj-c.

Happily, I don't think this is the case, which is good, because the 
more I have to fiddle with Objective-C, the more I detest it.  Its 
basic syntax is catastrophically obtuse. I find AppleScript (for 
example) far more clear and readable. Alas, the AppleScript <-> Cocoa 
bridge is woefully incomplete. One of the things that drove me to Ruby 
(and RubyCocoa) in the first place. (And one reason I won't go near 
Perl with a ten-foot pole.)

> The ruby-cocoa developers can't document cocoa, its too huge, and there
> are lots of great cocoa books around.

Of course. I don't expect to have Cocoa documented in Ruby per se. What 
I'm missing are critical details about the interface.

For example, where on earth is the application itself? The Obj-C-based 
documentation states that the variable "NSApp" contains the application 
object. When I use AppleScript, the application is the default 
environment until/unless I use a
	tell app "Somebody Else"
		blah blah blah
	end tell
block to change my context.

I haven't found any hints so far for getting my hands on the 
application itself in Ruby. I don't think a Cocoa manual's going to be 
much help there.