On or about 7/2/05 10:23 AM, thus spake "Christopher Hickman"
<email@hidden>:
> In my main script, I'd like to do this...
>
> foo
> -- result: -[UtilityClass doFoo] is called
>
> ...instead of this...
>
> call method "doFoo" --implemented by application's delegate, receiver implied
> -- result: -[UtilityClass doFoo] is called
Well, it seems to me that in your second formulation you stack the deck by
making it seem like "call method" is somehow problematic. But why is it? If
your method is a class method, then you can say:
call method "doFoo" of class "UtilityClass"
and *not* implement it with the application's delegate. And if (as your
formulation above implies) it is an instance method, you can say
call method "doFoo" of object someObject
provided you can get a reference to an instance of this class into
someObject - and you can, by setting things up in IB, just as any Cocoa
programmer would have to do. So what's the point of introducing the sdef
into the story? m.
PS You'll notice that I'm not answering the question. That's because I don't
know the answer. You can easily add an sdef to a ASS app to add customized
terminology to it, but I do not know whether you can use terms from that
sdef from within a script *of* that application. Why not try it and see?
--
matt neuburg, phd = email@hidden, http://www.tidbits.com/matt/
pantes anthropoi tou eidenai oregontai phusei
AppleScript: the Definitive Guide -
http://www.amazon.com/exec/obidos/ASIN/0596005571/somethingsbymatt
Take Control of Word 2004, Tiger, and more -
http://www.takecontrolbooks.com/tiger-customizing.html
Subscribe to TidBITS! It's free and smart. http://www.tidbits.com/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Applescript-studio mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/applescript-studio/email@hidden
This email sent to email@hidden
