Re: Source Text of Script Objects
Re: Source Text of Script Objects
- Subject: Re: Source Text of Script Objects
- From: Paul Berkowitz <email@hidden>
- Date: Mon, 31 Dec 2001 17:25:33 -0800
On 12/31/01 4:47 PM, "Shane Stanley" <email@hidden> wrote:
>
On 1/1/02 10:23 AM +1000, Paul Berkowitz, email@hidden, wrote:
>
>
> That's why I expressed the hope recently, on a different list (AppleScript
>
> Studio), that the AppleScript team might stop what they're doing for a while
>
> to implement the 15-20 most important commands from Jon's and Akua, or the
>
> equivalent. I really think it's the most important thing they could do now.
>
>
So give us your list. I'm curious to see whether there's a common set that
>
people want, or whether we'd end up with something approaching n * 20
>
commands, where n is the number of people drawing up a list.
I'm prepared to trust the AppleScript team to pick judiciously, considering
also that some things may be harder than others to do, in order to avoid the
n * 20 situation.
The few commands I think most essential?
type text -- Sigma's Additions
keys pressed -- Jon's commands , or go all out with
input state -- Akua Sweets
the ticks -- Jon's Commands
extended info for -- Akua Sweets -- i.e. beef up 'info for' from Standard
apply catalog info -- Akua Sweets
the entries in -- Akua , i.e. beef up 'list folder'
the clock -- Akua
?? puppet menu -- Akua, if they can do it better
play sound -- Jon's
munge -- Akua, or an equivalent from ACME, whatever
Fortunately, most of the commands in Akua and Jon's to duplicate and get
around the hobbled classic Finder shouldn't be necessary in OSX, although a
'deleteFile' without going to the trash would be a nice addition to the
Finder. And Akua's List suite, useful as it is, can all be replicated in
vanilla AppleScript.
There's lots more that would be great, but those are my top 10 essential
osaxen-that-should-be-built-in.
--
Paul Berkowitz