Re: KVC with an path, AppleScript and InterfaceBuilder
Re: KVC with an path, AppleScript and InterfaceBuilder
- Subject: Re: KVC with an path, AppleScript and InterfaceBuilder
- From: Thomas Engelmeier <email@hidden>
- Date: Tue, 24 Jan 2006 16:52:29 +0100
Hi Matt,
Is there anything special I need to do to in order to have paths
resolved for AppleScript properties?
Everything depends upon Cocoa Scripting's peculiar view of KVC-
compliance. I
suggest that you write a completely separate set of accessors for
the use of
Cocoa Scripting's KVC, and key the .sdef to them. (It is usual to
put these
accessors in a category.)
I'm just new to the Cocoa scripting variant, for Carbon I already
have my "workflow" to get it done. The category variant is neat, I
just felt adding scriptability starts to make the code .. well,
bloated?..
Is there any well known magic for the following two tasks:
- validation - happens usually automatically with min / max values
for Cocoa UI bindings?
- recordability for a KVC application - synthesize AppleEvents to
self to allow recording?
The details in the .sdef are extraordinarily
touchy.
Well, IMO like pretty much everything bound dynamically with Cocoa.
Hard to make anything ready for prime time without a comprehensive
suite of regression and unit-tests. This is one of the parts where
AppleScript comes in ;-)
If you are just getting started adding scriptability, I have put up
a tutorial that might help:
<http://www.tidbits.com/matt/scriptability/scriptabilityTutorial.html>
Merci -
Tom_E
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden