Re: General questions from a non-Applescript coder.
Re: General questions from a non-Applescript coder.
- Subject: Re: General questions from a non-Applescript coder.
- From: Gnarlodious <email@hidden>
- Date: Wed, 27 Apr 2005 13:27:39 -0600
Entity Shawn Milo spoke thus:
> 1. Should I learn Applescript? To some extent, it seems foolish not to
> stick with Python and bash scripting, since that's applicable outside
> of the Mac environment, and I can share code with more people. Is this
> a case where the answer depends solely on whether I intend to script
> to Mac apps such as iTunes and Finder, or just do other
> maintainance/one-off scripts?
Yes you should learn at least SOME Applescript. Anything you can do in
Terminal or shell you can do inside an Applescript with a nifty little GUI.
Pretty great. I am just now learning that rsync commands are best assembled
in Applescript and sent to Terminal. Really makes the tool usable.
> 2. When Automator is used, and the procedure is saved, is it in
> Applescript? I can see how being able to share and edit these scripts
> would be immensely useful.
I don't know, maybe someone else does. I only learned this morning Tiger
will include an RPN calculator. Good work Apple! Wonder if it will be
scriptable?
> 3. Is there a "must-have" book for beginners? I usually learn much
> better if I tackle a small script, and then use Google and a mailing
> list when I get stuck. But it's nice to have a reference book. I'll
> never read one beginning-to-end like I'm taking a class, so I like to
> have something more like a reference than a textbook, although I like
> one with plenty of working examples of the syntax. From the Amazon
> reviews, it seems like "AppleScript : The Definitive Guide" by Matt
> Neuburg is well-regarded, as is the "Missing Manual," by Adam
> Goldstein.
I would say forego the book and learn the keywords Google uses to find what
you want. Never failed me. If you want in-depth Applescript info the book is
a good investment.
And of course, this list.
> 4. In the reviews for the "Definitive Guide," it is made pretty clear
> that Applescript has, or at least had, "as a language and development
> environment has some terrible problems," and "when you're banging your
> head against the keyboard because a script doesn't work as expected,
> it's good to know that the language is not without unique
> 'personality' and that you're not alone." Those two quotes were from
> two separate, well-written and coherent reviews, written in 2004. Has
> the language evolved since then?
It certainly has, but like human language the subtleties of Applescript will
amaze you and are under constant evolution.
The pros never "bang their head", they methodically track down why it won't
work and ask here if it's a bug or syntax or what.
Waffled foreheads are a symptom of broken keyboards and inexperienced
Applescripters :=)
(hey that should be my new sig)
-- Gnarlie's Applescript page:
http://Gnarlodious.com/Apple/AppleScript/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Applescript-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden