 |
 |
Apple
Events vs. AppleScript
continued
|
When an application that supports Apple Events receives one, it
must first recognize it as an Apple Event (and not a key press,
menu selection, etc.) Then it must determine which Apple Event was
sent. There are a number of standard Apple Events specified by Apple,
but FaxTool uses its own custom Apple Events in order to fax seamlessly
from FileMaker.
|
Apple Events and Parameters
An Apple Event can also be accompanied by additional information, known
as parameters. Parameters are sent along with the relevant Apple
Event, and are used by the receiving application to customize the
result of the Apple Event. For example, suppose we have an Apple
Event called "Say". We could send: Say "Hello" - where
"Say" is the Apple Event, and "Hello" is the parameter.
Changing the parameter changes the result.
By using the scripts, fields, and calculations available in FileMaker,
a developer can send information direcctly to FaxTool, and custom
faxing is the result.
|
Wow.
I made it through that. So tell me, why are Apple Events better for
me now?
FaxTool was designed to receive Apple Events directly from FileMaker, and
pass them on to FAXstf. There is no scripting "overhead" as there
is in AppleScript, and you do not have to have all of the AppleScript
extensions and files loaded into your system.
Apple Events have a direct pipeline from application to application, because
both applications send and receive information in a format that
is specifically designed to send special information. AppleScript
relies on generic language that must be resolved in order to execute
a script. In other words, it goes through a committee until the
application gets the information that is being sent to it. |
| |
| Apple
Events vs. AppleScript 1
| 2 | 3
| 4 | 5
| 6 | |
|
AppleEvents
vs. AppleScript