Re: "a reference to"
Re: "a reference to"
- Subject: Re: "a reference to"
- From: Phil <email@hidden>
- Date: Wed, 9 Jan 2008 23:59:29 -0500
On Jan 9, 2008, at 10:34 PM, Chris Page wrote:
Perhaps one problem is that it can take some time to learn the
relationship between scripts and events, including the fact that the
text "{foo, bar}" in the event log represents an actual list object
rather than the conceptual collection of objects within the target
application?
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.
Is it necessary to limit the scope of thinking to the way the current
AppleScript tools work? (i.e. there is a better way: look at how other
tools <cough> Script Debugger, for example </cough> do things)
Seriously, the current 'out of the box' tools are nothing to be proud
of. Why not re-imagine how the tools could/should operate and the
functionality they could/should provide? I can't believe the number
of ways in which AppleScript hasn't changed in nearly 15 years. It's
2008 and the default AppleScript toolbox is still a pumped up TextEdit
and logs... just like back in the day on System 7. That was somewhat
understandable for a 1.0 product but where's the progress? While
AppleScript is far from perfect, many its issues and limitations could
be addressed/worked around just by providing more capable development/
debugging tools.
Thanks,
Phil
_______________________________________________
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