Re: What makes AppleScript COOL!
Re: What makes AppleScript COOL!
- Subject: Re: What makes AppleScript COOL!
- From: "Stockly, Ed" <email@hidden>
- Date: Fri, 07 Dec 2007 19:46:25 -0800
- Thread-topic: What makes AppleScript COOL!
>>>>>1) Script recording. This would help both Apple and scripters: Apple
wouldn't be blamed for every developer's (sometimes poor) choices in how they
expose their app, and scripters would have a much easier time dealing with
these implementation decisions since it wouldn't take so much trial and error
to figure out how to get something done.
I used recording a lot in OS 9 if I was struggling to figure out how to
issue a particular command.
It's nearly gone in OSX and I don't miss it.
What I do miss is Scripter's Command Builder, which would allow you to build
working commands by pointing and clicking at command components pulled from
the application's dictionary.
It also provided a better way of looking at dictionaries.
>>>>2) Debugging. Why is it still necessary to buy a (relatively)
expensive 3rd party application in order to debug Applescript code?
Get over it. Script Debugger is relatively cheap. I script Quark, InDesign,
PhotoShop, just to name a few, on scripts that are run on hundreds of macs.
To keep them all going all I really need is a single copy of Script Debugger
(Although I think we bought 4 copies). Compared to the money we spend on all
our installations with those apps, the cost of SD is a drop in the bucket.
If you're serious about AppleScripting you should use the best tools
available to write and debug your scripts. (Deployment is a different
matter, see below).
>>>>3) Provide example scripts and real language/dictionary documentation
for the code that *is* controlled by Apple Guide from 1999!?)
Agreed.
Just one other point about third party software vs. Apple software.
Without naming names, suppose all my scripts depended on a third party osax
or FBA for basic every day operation. Text handling, for example, or parsing
XML data, or copying and deleting files. I can imagine myself explaining to
my boss or some other department head that the reason the script won't work
on these new macs is that some software I downloaded for free from the
internet isn't compatible with his new processor or the new system and won't
be until the guy who writes it and releases it has bought an Intel mac and
upgraded to the latest system and has the time to work on it.
There's plenty third party developers do that's good and useful,and I buy
their products and my company buys them too, but there are some eggs I'd
rather keep in my own basket or Apple's.
ES
_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users
This email sent to email@hidden