In fact sending yourself apple events is THE way to make your
application recordable
The up side to this is you factor the user interface away from the
functionality
Done to the fullest extent you get a way that someone could conceivably
put a different user interface on your application and their UI would
drive your application via Apple Events
If you check out a very recordable/scriptable application like Quark you
can do pretty much anything Quark is capable of without every opening
Quark itself
On Tuesday, July 30, 2002, at 08:12 PM, Noah Desch wrote:
On Tuesday, July 30, 2002, at 09:55 PM, Alex Rice wrote:
On Tuesday, July 30, 2002, at 07:16 PM, Will Leshner wrote:
That's AppleEvents, not AppleScript. I wouldn't be surprised if RB
used AppleEvents all over the place behind the scenes.
Really for what? Apple Events are for interprocess or interapplication
communication. I'm not a Carbon programmer. I am just curious why one
would use Apple Events outside of making your app scriptable.
Well you have to use them to make your app recordable too, and RB is
recordable. I didn't see the stack trace but in a recordable
application it's sometimes considered good form to implement all
actions by sending apple events to yourself and letting your apple
event interpreter initiate the requested task. I don't know if that's
how RB works but it would offer a plausible explanation.
|