Re: upgrade issues: 8.1 --> X
Re: upgrade issues: 8.1 --> X
- Subject: Re: upgrade issues: 8.1 --> X
- From: email@hidden
- Date: Wed, 14 Mar 2001 18:26:04 -0800
>
>>>Why are we even talking about scripting additions past Classic Mac OS
9?
Because in one form or another they will be there. Osax are our friends.
Yes there are somethings currently handled by Osax that would be better
handled by FBA's, but overall osax are pretty cool.
Also there are some things some Osax do that FBA's should not do, like
display dialogs or other user interface things.
>
>>>Scriptable applications have so many benefits over scripting additions,
it's not funny; yet I rarely see them mentioned. Instead, I see Apple
trying to offer support for this old mechanism in ways that make things
more complicated for end users.
In many cases they do have benefits over osax, but not all. Would you drop
the standard additions? Would use use an FBA to display a dialog or a
progress bar? There are a number of OSAX and OSAX commands that are
perfectly appropriate to be used as extensions of the core appleScript
language. At the same time there are a number of Osax which would be far
better implemented as FBAs.
One of the coolest things about AppleScript is that we can use the display
dialog command in a number of applications and the dialog is displayed from
within the application, no need to activate another app.
>
>>>IMHO, rather than trying to support the old scripting addition
mechanism in the Mac OS X non-classic environment, Apple should seize this
perfect opportunity to get developers to repackage scripting additions as
scriptable FBAs
What I'd like to see is a clear and simple guideline from Apple about when
a particular task or function is best handled by a Scripting Additon and
when best handled by an FBA. Then I'd like to see software developers
(including apple) follow the guideline.
>
>>and to push users to move to using scriptable FBAs.
I think apple should refrain from pusing users around as much as possible.
ES