on 2004-09-30 3:20 PM, m at email@hidden wrote:
> Don't know if it's been mentioned as an advantage yet, but doesn't
> using AppleEvents internally as a layer between your Model and your
> Views/Controllers make recordability of AppleEvents a no brainer?
Yes. This was always the main reason to use send-to-self Apple events, and
I'm told that it now works on Mac OS X. AppleScript is designed so that
direct Apple events to self are very fast, unlike interapplication Apple
events.
But there have never been very many recordable applications, because this is
not an orthodox way to write applications. Any technology that requires
developers to work in unfamiliar ways imposes an adoption hurdle on itself
right from the start.
This technique also facilitates AppleScript "attachability" and
"tinkerability," features that are even less common than recordability. A
factored, send-to-self scriptable application can allow end-user scripts to
intercept menu items or other functions and substitute the script's
functionality for that implemented by the application. The prime example of
this is Late Night Software's Script Debugger. Dangerous and powerful stuff!
--
Bill Cheeseman - email@hidden
Quechee Software, Quechee, Vermont, USA
http://www.quecheesoftware.com
The AppleScript Sourcebook - http://www.AppleScriptSourcebook.com
Vermont Recipes - http://www.stepwise.com/Articles/VermontRecipes
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/email@hidden
This email sent to email@hidden
