On 2/28/05 7:43 PM, "Gnarlodious" <email@hidden> wrote:
>> So far, I'm spending about 90% of my time figuring out why my
>> clever solutions don't work. :-(
> One of the first things you learn about Applescript is that when you run
> into something that won't work you're better off giving up and starting a
> new project.
It usually means you're trying to make AppleScript act like some form of C,
and do everything itself. That's not the best use of the language. It's best
used as a glue for many disparate applications, not as a standalone
language. If you keep that in mind, it's a lot nicer to work with and use.
It's when you try and force it to be Obj-C that you'll loose your bloody
mind.
--
Nothing makes a man more aware of his capabilities and of his limitations
than those moments when he must push aside all the familiar defenses of ego
and vanity, and accept reality by staring, with the fear that is normal to a
man in combat, into the face of Death.
-- Major Robert S. Johnson, USAAF.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Applescript-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/applescript-users/email@hidden
This email sent to email@hidden
