Re: AppleScript a miserable and utter failure
Re: AppleScript a miserable and utter failure
- Subject: Re: AppleScript a miserable and utter failure
- From: Doug McNutt <email@hidden>
- Date: Wed, 28 Sep 2005 12:01:04 -0600
At 08:02 -0700 9/28/05, Jon Pugh wrote in part:
>Daring Fireball: The English-Likeness Monster <http://daringfireball.net/2005/09/englishlikeness_monster>
Which says in part. . .
>The problem is that System Events also defines "user domain", not as a constant, but rather as a property of the System Events application itself. It uses the same four-character Apple Event code, 'fldu'.
A simple improvement to AppleScript which would eliminate a whole lot of these problems is to make it easy to discover - in a dictionary from within Apple's script editor with no 3rd party stuff required - the actual event codes defined by applications and their definitions using those forbidden terms like "class", "property", "inherits", "method", and the like.
No one should be forced to use the <<event codes>>, or even to read about them. But those of us who are so frustrated that we run to MPW, perl, or shell scripts just to get out of AppleScript as soon as possible might find the Script Editor more friendly.
Step one would be a simple preference in Script Editor to show the codes. Step two would be a second set of programmer-friendly definitions (C headers perhaps) in the dictionaries.
But then AppleScripters are NOT programmers - right?
--
Applescript syntax is like English spelling:
Roughly, but not thoroughly, thought through.
_______________________________________________
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