LNS Home
Script Debugger
Download & Buy
x Explore
x Edit
x Run & Debug
x Deploy
What's New In 4.5
bullet Documentation
bullet Blog Posts
My SD Story
Software Updates
 
4.0.9 Update
3.0.9 Update
bullet 2.0.5 Update
x Free Downloads
 
XML Tools
XSLT Tools
x Property List Tools
x List & Record Tools
Register Your Copy of Script Debugger
Join the Script Debugger Mailing List
x AppleScript/ Scripting Links
Products
x Script Debugger 4.5
Site Contents
bullet Mark’s Blog
Product Registration
Bug Reporting
x Freeware
Contacting Us

SD4 Headling


image

External Editor

image

Script Debugger lets you use an alternative text-editing application to edit a script — BBEdit, TextWrangler, or TextMate. Script Debugger’s implementation of this feature is seamless. With a script window open in Script Debugger, you open the same script in an external editor and edit it there. When you save and close the document in the external editor, you are back in the Script Debugger document, which has taken on the changes you made in the external editor.

To start an external editing session on the frontmost script window:

  • Choose File > Edit With BBEdit. Actually, the name of the application shown in this menu item will depend on which of the three applications you have and which ones are running. Script Debugger will prefer a running application to one that is not running, and among running applications or non-running applications it will prefer the order BBEdit, TextWrangler, TextMate.

Thus, for example, if you have both BBEdit and TextMate, this menu item will be called Edit With BBEdit if both BBEdit and TextMate are running or if neither is running, but it will be called Edit With TextMate if TextMate is running and BBEdit isn’t.

When you start an external editing session, two things happen:

  1. In the frontmost Script Debugger script window, a dialog appears warning that the script is being edited externally.

    image

    Additionally, the script window is watermarked in its lower right corner with the word “Locked”.

    image
  2. A new window opens in the external editing application, containing the text of the Script Debugger script window (and the external editing application comes to the front).

At this point, the normal chain of events is that you would edit the document in the external editing application:

  • Whenever you save the document in the external editing application, the Script Debugger copy is updated to match.

  • When you close the document in the external editing application, the warning dialog is removed from the Script Debugger script window (and Script Debugger comes to the front). This is the normal way in which an external editing session ends in good order.

Alternatively, you might change your mind and decide to break off the external editing session prematurely without reflecting the changes from the external editing application back into the Script Debugger document. To do so:

  • Switch back to Script Debugger and click Cancel in the warning dialog.


Explore | Edit | Run & Debug | Deploy | What's New In 4.5 | My SD Story


Copyright © 1998-2009 Late Night Software Ltd. - All Rights Reserved.