Re: on neophytes vs perfectionists (was Re: Tell Blocks Considered Harmful)
Re: on neophytes vs perfectionists (was Re: Tell Blocks Considered Harmful)
- Subject: Re: on neophytes vs perfectionists (was Re: Tell Blocks Considered Harmful)
- From: Paul Scott <email@hidden>
- Date: Thu, 18 Dec 2008 15:28:33 -0800
On Dec 18, 2008, at 2:38 PM, Ed Stockly wrote:
Make is the verb. By itself it does nothing. It needs an subject
(object) to do anything.
set resultObject to make new newTypeClass ¬
at atInsertionLoc ¬
with properties withPropertiesRecord
You need to tell it what to make and sometimes where to make it and
you can define the properties the new objects is made with.
<snip the rest of the obvious>
Duh.
Look here for a ton of very well written AppleScript iTunes examples.
http://dougscripts.com/itunes/index.php
Exactly my point. You have to dig through the cob-"Web"s to find out
any details. Who the @#$% is Doug? And what the %$#@ does he have to
do with iTunes? I thought I was scripting iTunes, not DougTunes.
Where's Apple's iTunes scripting guide? You can't have it both ways:
blame the third-party vendors for poor documentation and then neglect
your own responsibilities. Sheesh.
No offense intended toward "Doug", or anyone else who helps out. I
really appreciate it. I'm pointing the finger at Apple. I'm an Apple
zealot because they produce fantastic products. As a result, I expect
a lot from them. But this is one area they need to improve quite a bit.
In addition, if you master scripting one single scriptable
application you can take that knowledge to script almost any
scriptable app.
HTH,
Not hardly. On both counts.
Have you ever even used "make"? (that's rhetorical sarcasm) Half the
time it doesn't support what you think it should. And getting it to
work the other half of the time can sometimes be a challenge. Why
doesn't Apple take the lead and document these things for each of
their scriptable applications?
Knowing how to use "make" (or "copy," or any verb) with one
application doesn't necessarily apply to any other. Each application
has different "objects," some of which are supported and others that
aren't. Without documentation it gets frustrating really fast.
Anyway, my original point is that I find AppleScript to be much less
approachable than Chris would suggest. And I stand by it. I don't want
to get drawn into a long debate.
I've about all I'm going to say on the subject for awhile. AppleScript
is frustrating enough by itself without having to get caught up in
even more frustrating discussions. I've got scripts to write.
Paul
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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