Re: "a reference to"
Re: "a reference to"
- Subject: Re: "a reference to"
- From: has <email@hidden>
- Date: Thu, 10 Jan 2008 17:45:30 +0000
On 10 Jan 2008, at 03:34, Chris Page wrote:
2. [Implicit get's] invisible nature means that users cannot
obviously see - and thereby understand - why their code fails in
some cases, because their experience of the common-case behaviour
has given them a faulty understanding of how AppleScript and Apple
event IPC actually work.
The get events do show up in the event log, which should help.
Nope. The event log is far too abstract to be useful for learning
purposes. You need to understand how AppleScript works before you can
interpret it effectively. Until then, an extra event popping up here
and there is just one more mystery to add to all the others on the pile.
It would be interesting to know whether there's a clearer way to
indicate to the scripter what's going on in the event log.
There may be various ways you could tinker with its current
presentation that might yield marginal improvements. However, as I've
said at various times and places [1], the only way to fundamentally
address all these problems is to completely rethink and redesign
AppleScript, taking advantage of all the work that's been done in end-
user programming over the decade-and-a-half since the original
AppleScript team sat down with a blank sheet of paper and thought to
itself: "So what now?"
has
[1] Most recently: <http://lists.apple.com/archives/Applescript-studio/2008/Jan/msg00061.html
>
--
http://appscript.sourceforge.net
http://rb-appscript.rubyforge.org
_______________________________________________
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