Re: a Smile, Script Debugger, Scripter
Re: a Smile, Script Debugger, Scripter
- Subject: Re: a Smile, Script Debugger, Scripter
- From: Cal <email@hidden>
- Date: Tue, 30 Jan 2001 05:30:41 -0500
"Jeff Handy" <email@hidden> wrote:
Expanding on the subject of debuggers; I'd like to get a roll-call of
sorts as to your favorite of development environments.
I'm somewhat decided on buying two copies of Script Debugger, but I'm
still sort of on the fence. I've tried both SD and Scripter and like
them both. I really like the browser with SD, but I like the scriptbase
functionality of Scripter. I don't have the option of buying both, or
that's what I'd do.
FYI, Scripter also has browsers (more than one, very accurate).
Control-double-click on an App Bar icon gets the Object Map and
command-option-double-click gets you the Object Prober -- these are
hierarchical schemes of the object classes in a dictionary and in the
application.
T&B <email@hidden> wrote:
Scripter has a browser hidden away in its interface. You can see a
snapshot of it and other GUI elements at:
http://www.tandb.com.au/applescript/snapshots/
Be aware that more than twice as many screen shots appear for SD (14)
than Scripter (6). Much of the "soul" of Scripter isn't there.
and a feature comparison tables at:
http://www.tandb.com.au/applescript/editors/
Despite T&B's valiant effort in this area, IMO it's impossible to see
the Scripter story using this sort of chart.
And a very brief "how to" show the browsers at:
http://www.tandb.com.au/applescript/tutorial/05/
This also doesn't tell the story.
The problem is that, unless you live with all these applications for
several months, using them every day, there's no way to get a good
feel. Anyone making purchasing decisions mainly based on these views
will probably be disappointed.
In T&B's words:
"The overall experience of using a script editor can not be read
entirely from a clinical analysis..."
Respectfully,
Cal