Re: Interface Builder 3 -- Completely New!
Re: Interface Builder 3 -- Completely New!
- Subject: Re: Interface Builder 3 -- Completely New!
- From: Chris Hanson <email@hidden>
- Date: Sat, 27 Oct 2007 01:47:37 -0700
On Oct 26, 2007, at 7:32 PM, R. Matthew Emerson wrote:
One example case I ran into was in trying to set the class of File's
Owner to my NSWindowController subclass. I can drag an NSObject off
the palette and set its class to my custom class, but then I don't
get the outlets and actions that I should inherit from
NSWindowController.
I'm using a Common Lisp programming environment with an Objective-C
bridge, so I don't even have header files for IB to parse.
Just add the outlets and actions in Interface Builder 3's Object
Identity inspector -- the same one you used to set its custom class --
in the "Class Actions" and "Class Outlets" slices. Set the class name
first, and then its outlets and actions.
Interface Builder 3 specifically allows you to set a custom class that
doesn't have a corresponding Objective-C header file and add arbitrary
outlets and actions to it in order to support languages bridged to
Objective-C.
Since you're using a bridge, I also thought I should point out that
BridgeSupport is an important new Leopard feature: Leopard's public
frameworks have XML descriptions of the APIs they expose that can be
used by language bridges. This lets them avoid messy things like
having to parse header files to figure out how to generate calls into
or parse results from the Objective-C runtime. That's how Ruby and
Python can be used for Cocoa in Leopard; it would be great to see
other languages like Common Lisp use them as well.
-- Chris
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden