Message-Id: <200005150111.SAA36674@public.lists.apple.com>
Subject: Re: Script Debugger or Scripter?
Date: Sun, 14 May 2000 21:09:30 -0400
From: Xandra Lee <xandra@rochester.rr.com>
To: "HOnza Koudelka" <koudelka@appleklub.cz>,
        <applescript-users@public.lists.apple.com>

>Which one should I buy? Which one is better for what?
>
>I am just choosing between Script Debugger 2.0 and Scripter 2.2.
>HOnza

Well here's an answer you won't like:
Buy Both!
I preface the following with the following caveats:
* it's written from the viewpoint of a novice scripter, Not a pro.
* Im unfairly comparing the current version of Scripter, with the "old" 
version of Debugger
  (not fair really, but I didn't even know 2.0 was available)
 
---------------------------------------------------------
Script Debugger:(the following is based on Debugger 1.5)
---------------------------------------------------------
+ + +. It's scriptable, (I can't tell you how often I use these 
capability)
 --ex's:  You can do things like write scripts That have debugger open 
and save a folder full of applets to text (even dumb stuff like being 
able to auto locate various windows, count)

+ This one's largely personal taste, but I find Debuggers Interface, and 
dictionary handling  superior to Scripters'. (**see Command builder 
window, which would be an exception to this under Scripter). If  your 
beginning Scripting, you'll likely find the transition from Script Editor 
seamless.

+ Its ability to report full, AS formatted results in event logs (is 
assume, because of lack of 32k text limit) This may sound silly, but 
there are times when this is very useful.

+  Script Tools (the included package of Additions) contains some real 
gems.

+. Excellent printed manual (1.5 - I haven't seen what they've put out 
for 2.0).

+  Exceptional compatability with other products (I've never once had a 
conflict with anything--you'd be impressed to if you saw my extensions 
folder) Without knowing anything about programming my guess is that this 
is a good sign of a very solidly built product.

-  You can only set "markers" for handlers, and globals making Scripters' 
navigational abilities far superior.

-  Not nearly as strong as Scripter in terms of accessing frequently used 
syntax

---------------------------------------------------------
Scripter 2.2:
---------------------------------------------------------
+ Definitely the more "powerful" tool (at least comparing it to SD1.5). 
This products' usefulness grows with your development as a scripter - 
particularly in terms of debugging. It's likely you'll end up purchashing 
this one in the end if you become a serious scripter.

+  Exceptional access to frequently used syntax via "Collections", 
"Wraps", "Scriptbase"

+. Numerous top-notch built-in tools: "Wraps", the "Call box", 
"Associations", (Scripters version of "using terms from") to name a few, 
are outstanding conveniences.
**(see below)

+  Command builder windows: provide auto boilerplate syntax. Exceptional 
Feature.

+  Top-Notch navigation capabilities, allow you to jump to anywhere 
quickly within a script.

+  A very good printed manual, hindered only by the absence of an index.

+  Simpler interaction with FaceSpan.

+  Scriptbase **(see below)

-/+ Dictionary handling: you can't drag drop apps/OSAXen to open a 
dictionary. The ability to open all installed OSAXen is nice, but the 
opening a single OSAX is awkard (there's not even a button to go to 
Scripting Additions Folder.) 

-- It's not scriptable

Other than its lack of scriptability, my only gripes with Scripter are 
really in the category of minor annoyances, rather than product 
weaknesses (and I must apologize for stating them publicly,  without even 
affording  Main Event the courtesy of reporting them privately): I only 
mention them here, because most are rarely cited.

That said, here's my list of cons:
  -Too much of the products' stregnths are hidden keyboard commands 
--you'll need to really scour the manual to find them. (they really 
should also appear in menus)

 - Very few of menu commands have keyboard shortcuts (you'll definitely 
need Qkeys, or OneClick)
   Complaints about Scripter having "too many windows", could be easily 
resolved by providing shortcuts for these windows along with with a 
command/shortcut for hiding all but the Script window & App pallette.

- Truly silly stuff: If you try to save a script which hasn't been 
recompiled, Scripter won't even try to compile it, instead, it will bring 
up a dialog box asking if you'd like to save as text.(Argh!), event logs 
are not formatted (making for difficult reading). You can't use replace 
for all instances of "<" -- not fun when you've just pasted a script from 
an email.

**I've not bothered to explain the details of these features since Bill 
Cheesmans' excellent review (at AppleScriptSourcebook.com) covers them 
beautifully.

---------------------------------------------------------
Both Products
---------------------------------------------------------
+++ Very Stable, well thought out programs
+++ Excellent Support
+++ More than worth they're price. (In time saved)
+++++ You'll learn applescript MUCH quicker using these rather than 
Script Editor

My only wish is that more software developers matched the quality and 
usefulness of these two fine programs.

xandra


Alixandra Leigh
AceDesign
xandra@rochester.rr.com