Publishers of technology books, eBooks, and videos for creative people

Home > Articles > Design > Adobe Creative Suite

  • Print
  • + Share This
This chapter is from the book

Scripting Editors

Scripts are text files—which means that (at least in theory) you can write them in any old text editor. Scripting editors, in contrast, supply some tools that you'll soon find you can't live without.

A decent script editor should do three things:

  1. Provide color-coding and indenting. This makes the script much easier to read (Figure 4.3).
    Figure 4.3

    Figure 4.3 Color coding and indenting in the ExtendScript Toolkit. Both serve to visually organize the script.

  2. Check syntax. Each scripting language follows its own syntax, or grammatical structure. The editor should check that syntax and warn you when you've run afoul of the law.
  3. Run the script. You should be able to run a script in a scripting editor by clicking a single button, as you can with Apple's Script Editor. Windows, in contrast, doesn't include a scripting editor. Without a third-party editor, in Windows you have to write your script in Notepad and then save the file with the correct extension (.js or .vbs). To run your script, you have to navigate to the file and double-click it. To debug the script, you have no option but to go back and forth until it finally runs successfully (or you die of old age).


Apple provides a free scripting editor called Script Editor with every Mac. Not only does it fulfill all of my requirements for script editors, it's perfect for beginners. Because some applications are "recordable" in AppleScript, you can record yourself manually performing tasks in a program, and they will be written out as AppleScript code in the editor—similar to recording Actions in Creative Suite or recording a macro in Microsoft Office. Before you get too excited, though, you should understand that few applications have been written to take advantage of this feature.

Two other AppleScript editors to consider are Satimage's Smile (available free at and Late Night Software's Script Debugger (free demo, $199, available at


If you own Creative Suite, you're in luck because you also own Adobe's ExtendScript Toolkit, an "extended" implementation of JavaScript. The ExtendScript Toolkit works with both ExtendScripts and good old JavaScripts. It meets all of my basic script editor requirements, plus throws in some features typically found only in editors you pay good money for (see "The ExtendScript Toolkit"). These extra features generally fall into the category of helping you figure out what you've done wrong. Debugging is the process of tracking down and identifying errors other than syntax errors, incorrect math, and generally harebrained commands.


As mentioned earlier, the Windows operating system does not provide a free scripting editor. Instead, you must type your script in a text editor like Notepad, save it with the .vbs file name extension, and then double-click the file itself to run the script.

Some scripting VBScript editors to consider are Adersoft's VbsEdit ($49, available at and Modelworks' SitePad Pro (starting at $129.95, available at

  • + Share This
  • 🔖 Save To Your Account