Script Editor - BrineSoft Online Help

The dialog enables to change working settings. The setings are saved to a file called Workspace (*.ws). Settings that are common to all Workspaces are stored to Options instead.

Paths

Script and Projects files folder
It defines a folder where the script files are looked for. This mainly determines which files are displayed by the list box on the left side in the user interface. Displaying the path underlined signals that the path already exists.

This folder contains shared scripts (libraries)
Files in the folder defined by the Workspace get some extra privileges. Tick this checkbox when you intend to use scripts in the folder accross more other Workspaces.

Toggle Absolute/Relative

Toggles between absolute and relative path to the folder. The relative path it the path relative to the currently running ScriptEditor.exe.

Browse

The button displays a dialog for a folder selection.

Editor

Used scripting languages
The list specifies the languages used within the Workspace. If you intend to use only one language select only that one in the list. The list affects file filters in file dialogs, the list of scripts, and so on. Properties of the languages are described in the file ScriptEditor.xml, therefore it is easy to add a new language by modifying the file.

During script execution
Do nothing
No extra action is taken when the script execution is started.
Minimize Editor
The user interface of the Editor is minimized to a button in the Windows Task Bar when the script execution is started, and it is restored when it is finished. The user interface is restored when the script fails as well.
Hide Editor
The user interface of the Editor is hidden when the script execution is started, and it is showed when it is finished. The user interface is showed when the script fails as well.

Project Execution

Execute project (*.wsf) by
The combo box determines what scripting engine will be used to execute the script.

Windows Script Host - window based - the engine is the Window's standard WScript.exe. The project name is passed to it on the command line. When the project execution fails a modal dialog window describing the error will pop up.

Windows Script Host - command line based - the engine is the Window's standard CScript.exe. The project name is passed to it on the command line. The command line window (DOS-box) remains open when the project execution is over and therefore the reason is visible if the project failed.

Script execution time-out
With this option it is possible to limit the project execution in the following ways:

Never
No time-out is applied. This option should be avoided mainly during the project development; if the script writer makes an endless loop in the script, the script execution must be killed in the Running Scripts window.
User defined
Time is the time, in seconds, for which the project can run. Projects can be easily and safely killed in the Running Scripts window in case of an endless loop.

Script Execution

Execute script (*.vbs, *.js, ...) by
The combo box determines what scripting engine will be used to execute the script.

Microsoft Script Control - the engine is embedded in the Editor. Therefore, if the script execution fails the Editor will highlight the line in the script where the error occured and will place the cursor at the appropriate place. However, keep in mind that WSH (Windows Script Host) is not available in this mode and therefore the object WScript is missing.

Windows Script Host - window based - the engine is the Window's standard wscript.exe. The script name is passed to it on the command line. When the script execution fails a modal dialog window describing the error will pop up.

Windows Script Host - command line based - the engine is the Window's standard cscript.exe. The script name is passed to it on the command line. The command line window (DOS-box) remains open when the script is over and therefore the reason is visible if the script execution fails.

MS Internet Explorer - The Internet Explorer is asked to execute the script. The default way of the script execution is selected this way. It is the same as if the user double-clicks the script file in the Explorer, or types name of the script file in the Run dialog.

Script execution time-out
With this option it is possible to limit the script execution in the following ways:

None
No time-out is applied. This option should be avoided mainly during the script development; if the script writer makes an endless loop the script the script execution must be killed in the Running Scripts window, if possible, or with the Windows Task Manager.
When script hangs
This option is available only for Microsoft Script Control. The Script Control has an ability to detect that the script execution hanged, for example, due to an endless loop in the script. When such a situation occurs the user is prompted to either terminate the process, or try again. This is the recommended option for scripts executed by the Script Control.
User defined
Time is the time, in seconds, for which the script can run. This is the recommended option for scripts executed by WScript.exe or CScript.exe. However, processes executed by these two can be easily and safely killed in the Running Scripts window in case of an endless loop.

Used Objects

It is the list of COM (OLE Automation) objects that are displayed on tab Objects on the left side in the Editor user interface. Having the objects, their methods and properties available this way makes easier to use them during the script editing. Therefore it is convenient to specify the most used objects here. However, some objects display their user interface or the fragments of it (message boxes) during its initialization (MS Office). Specifying such objects in the list should be avoided.

Test All Objects

To make sure that all the listed objects are valid and don't display any GUI during initialization, click the button Test All Objects.