Re: Push for AppleScript in OS X
Re: Push for AppleScript in OS X
- Subject: Re: Push for AppleScript in OS X
- From: email@hidden
- Date: Fri, 2 Feb 2001 17:00:34 -0800
>
> I think it would be in our best interests if everyone sent their desire
to
>
> have AppleScript in OS X.
>
>
The good news is that you're about one year too late, ).
>
>Mark<<This issue occupied much of our time during a panel discussion I
was
involved with at Macworld.
It's funny, Mark, the first time we met was at Apple Headquarters
discussing the importance AppleScript in Rhapsody. At that same visit Cal
arranged for presentations to the board of directors from a small group of
Apple customers who depend on AppleScript.
Here it is how many years later and we're still worried about basically the
same thing!
>
>>>>The issue at hand is actually quite serious. While its true that the
AppleScript language its self is well positioned in MacOS X, scriptability
in MacOS X as a whole is in a terrible state.
Personally I feel that judgement is a bit hasty and harsh. First,
AppleScript thrives in the Classic environment and an appleScript running
in Classic can interact with OS X applications.
Second, Apple is doing pretty much what they've said all along (or at least
for as long as they've been saying things publicly and officially) and that
is that AppleScript will be a key technology in Mac OS X but that it will
be a slow start.
Just how slow is where my only concern lies.
I feel certain it will progress in OS X faster than it did in the classic
OS over the years. But even if it moves slowly, we still maintain much of
the functionality through classic scripting.
>
>>During Macworld it became very clear that with the initial release of
MacOS X we are not going to enjoy anywhere near the level of scriptability
in the core OS (Desktop, Dock, Preferences, Networking, Printing) that we
enjoy today with MacOS 9.
Again, that's pretty much what we've been expecting all along.
Right now Apple has a terrific AppleScript team. They're focus has been on
OS 9.1. I believe the plan is to move that team to OS X at the appropriate
time. Based on what I've heard from people inside of apple and out I
believe we're much better off with an experienced AppleScript "A" team who
know the technology and the system software rather than two teams working
on AppleScript independently.
Time is nature's way of keeping everything from happening all at once.
>
>>Additionally, all of Apple's recent consumer applications (iTumes,
iMovie,Final Cut Pro, etc.) are *not* scriptable. I see this as a very bad
precedent.
Have you seen the preview version of QuickTime? That would be a good
precedent. Apple has been pretty consistent in their development of new
technology and applications and appleScript. Basically the technology
evolves in secrecy, scant attention is paid to AppleScript until it is
released and then after a time, AppleScript is implemented in stages.
Considering that iTunes is a modified version of another scriptable app, I
wouldn't be surprised if it's not the first to become scirptable. (Heck, I
haven't tried this but I wouldn't be surprised i you couldn't just paste
the AETE from its predecesor into it and have a scriptable app).
>
>>>So, to conclude, its not the language that's at risk, but support for
scripting in the OS that's the problem.
Well, first, the language is always at risk. Particularly when you have
OSAX developers wanting to clutter up the namespace with hideous commands
like "Akua copy" or "MT this" or "SMIL That" yuk, yuk, yuk!
While I agree we should do our utmost to ensure that Apple provide the most
support for scripting possible, we should also recognize what they've done
and how far they've gone so far to make the transition as smooth as
possible for all of us.
This is not the time to panic.
>
>>>If scripting in MacOS X matters to you or your organization, you must
make this clear in a respectful way to Apple. If we are not making our
needs clear to Apple, they may choose not to do this work in favor of some
other feature enhancement.
I certainly agree with that!
HTH,
ES