Re: Curious problem with Scripter
Re: Curious problem with Scripter
- Subject: Re: Curious problem with Scripter
- From: Bill Cheeseman <email@hidden>
- Date: Thu, 26 Apr 2001 13:44:23 -0400
on 4/26/01 10:07 AM, Richard 23 at email@hidden wrote:
>
Let's just say that although sometimes quite useful, I have found
>
enough little inconsistencies in the "advanced" script editors to
>
stick close to Script Editor, warts and all. It seems to run scripts
>
closest to how they will perform in the wild, other than....
[pet peeve omitted]
This is a very important point, which bears emphasis. I do a lot of beta
testing of AppleScript implementations. In that context, it is essential to
use a tool like Scripter or Script Debugger to figure out what is going
wrong in an application. However, one must always remember to test a problem
in Script Editor, or in one of the debuggers with debugging turned off, as
well, to make sure the problem is not a figment of the debugger's
imagination. Despite my best intentions, I sometimes forget to take this
final step and end up raising alarums about a bug that isn't.
The same point can be made about third-party scripting additions, which
should be turned off for most beta testing (but not when looking for
terminology conflicts).
--
Bill Cheeseman - email@hidden
Quechee Software, Quechee, Vermont, USA
The AppleScript Sourcebook - www.AppleScriptSourcebook.com
Vermont Recipes - www.stepwise.com/Articles/VermontRecipes