BrineSoft Script Editor
Script Editor - BrineSoft Online Help Prev Page Prev Page
Overview
What Is WSF
Why Use WSF
Scripting Languages
System Requirements
Command Line Options
Errors Handling
Find WSH Error
Bookmarks
Working with Bookmarks
Workspaces
Understanding Workspaces
Interim Workspace
Default Workspace
Workspace Files
Workspace Content
New Workspace Wizard
User Interface
Main Window
Find
Find in Files
Workspace Settings
Options
Object Properties
Replace Selection
Select Jobs
Tools
Select Scripting Language
Create a Windows Shortcut
Get Script File
New Project Wizard
Main Menu
Menu File
Menu Edit
Menu Find
Menu Workspace
Menu Project
Menu Run
Menu Options
Menu Tools
Menu View
Menu Window
Menu Help
Temporary Files
Temporary Files ~$
Temporary Files ~@
Working with Project Tree
Edit <job>
Edit <script>
Edit <object>
Edit <reference>
Edit <resource>
Edit <runtime>
Edit <comment>
Embedding All Scripts
Checking a Project
Working with Files
Open a Project or a Script
Run a Project or a Script
Save a Project or a Script
Close a Project or a Script
Miscellaneous
Microsoft Script Control
File ScriptEditor.xml
Purchase Script Editor
Register the Product
Registration Benefits
 BrineSoft Main Page | Script Editor Page | Download this Help File

Tools

The dialog enables to specify external tools which can be uses from within the Editor.
The items, as defined in this dialog, will appear in Tools menu. Optionally they can appear in the tool bar as well.

Command line use

The parts that contain spaces (long names) must be enclosed in quotation marks, for example:

"c:\Program Files\My Program Group\MyApplication.exe" %EDITOR_FILE%

Consider that prefixed parameters usually must be enclosed together with the prefix, for example:

"c:\Program Files\My Program Group\MyApplication.exe" "-fc:\Some data\My Project\MyDataFile.dat"

Keep in mind that executable file is expected on the command line. To start other file, such as *.bat,
call Cmd.exe, for example:

Cmd.exe "c:\My Batch Files\DoSomething.bat"

To close the command line window (DOS-box) automatically, use /c switch with Cmd.exe, for example:

Cmd.exe /c c:\SomeBatch.bat

Macros

To pass parameters to the tool application several macros can be used on the command line:

Macro Expands to
%EDITOR_EXE% Folder in which ScriptEditor.exe is running.
%SCRIPTS% Folder with script files as defined by Workspace in use
%EDITOR_FILE% Name (incl. drive, path and extension) of the script file that is open in the editor. Empty string if no file is open or the currently selected file is a project.
%PROJECT_FILE% Name (incl. drive, path and extension) of the project file that is open in the editor. Empty string if no file is open or the currently selected file is a script.
%OPEN_FILE% Name (incl. drive, path and extension) of the file open in editor, regardless it is project or script. Empty string if no file is open.
%EXTERNAL_SCRIPT% Name (incl. drive, path and extension) of the external script file if the currently selected file is a project, and currently selected element is <script>. Otherwise an empty string.
%STRING_AT_CURSOR% String constant in the script at the cursor position. Empty string if character " (quotation mark) can't be found both left and right of the cursor, or if the currently selected file is a project.
%REF_OBJECT% Name of the referenced object if the currently selected file is a project, and currently selected element is <reference>. Otherwise an empty string.
%CURRENT_JOB% Name of the <job> element currently selected in the project. If the currently selected element is a sub-element of <job>, name of that <job>. If <package> element is selected name of the first <job> in the project.
%DESKTOP% Windows' Desktop directory
%TEMP% Windows' temporary
%WINDOWS% Windows' main directory (e.g. c:\WINNT)

See Also
User Interface, Options, Workspace Settings