Re: Follow-Up: Bug ID 24013620: Apple Configurator 2, AppleScript Library not discoverable
Re: Follow-Up: Bug ID 24013620: Apple Configurator 2, AppleScript Library not discoverable
- Subject: Re: Follow-Up: Bug ID 24013620: Apple Configurator 2, AppleScript Library not discoverable
- From: has <email@hidden>
- Date: Thu, 14 Jan 2016 03:44:30 +0000
Jean-Christophe Helary wrote:
It's supposed to behave like this. Too bad.
The reviewer obviously didn't understand the real intent of your ticket,
which is an enhancement request along the lines of:
Script Editor's "Open Dictionary..." window currently lists
SDEF-enabled ("AppleScriptable") applications, scripting additions, and
SDEF-enabled AppleScript libraries installed in standard Script
Libraries folders ("~/Library/Script Libraries", "/Library/Script
Libraries"etc.) only.
Please enhance Script Editor's "Open Dictionary..." window to
automatically discover and list SDEF-enabled AppleScript libraries that
are embedded *within* installed applications .app bundles as well.
[insert illustrative use case here]
This is not the reviewer's fault, mind, as I doubt your ticket would
make much sense to anyone who isn't already deeply steeped in
AppleScript arcana and recent discussions here. It's not your fault
either - as Shane and I have been trying to tell the Chrises: Understand
Your Users. Telling an audience of non-programmers to "file bug reports"
on complex technical issues is not productive. Untrained amateur coders
frequently don't understand either the problem or its solution with
sufficient depth or accuracy to construct a useful analysis, nor know
how to phrase that ticket so that it's quickly, clearly understood by
busy professional programming staff.
If Chris really wants clear, accurate, detailed, and *useful* Radar
tickets regarding his library system, the best way to get those is to
write them himself. To do that, he needs to 1. follow and participate in
the relevant discussions on this list, listening to what users say and
prompting them for further details, and 2. spend some time studying how
third-party AS libraries (and also write some himself!) are currently
being understood, written, and used (and misunderstood, miswritten, and
misused) by users. This way he can spot any problems users are having
(even if they don't realize it themselves) and figure out *precisely*
why they're having them and explain it in clear, precise,
programmer-friendly terms. Apple bureaucracy allowing, he might even
copy those tickets here (or at least push others in the right
direction), allowing users to follow and file duplicates on issues that
affect them directly - in turn helping Apple prioritize those tickets
and set development, documentation, and QA resources appropriately.
In other words, Mr Page is the professional software engineer here, not
us, so if he wants the job done right he needs to be the one who steps
up as domain expert/responsible adult/designated driver, and do what's
required to make the product fully fit for both its declared purpose
*and* its target audience. Leaving AppleScript's non-programmer audience
to flounder unaided in technical waters beyond their level is just a
lazy cop-out, and a great disservice to everyone.
HTH,
has
_______________________________________________
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