ScriptManager

(Show (Hide table-of-contents) table-of-contents)

ScriptManager is part of the CategoryAplTree project.

Overview

The purpose of this namespace is to offer a GUI from which all scripts (namespace scripts as well as class and interface scripts) are accessible.

The GUI shows ...

• which scripts are different from their file version.
• which scripts do point to an invalid location.

• which scripts differ from their SubVersion base version.

• which scripts have SALT backup files, and how many.

This is a screenshot:

Note that a blank in the columns "SALT" and "SVN" (for SubVersion) have similar meanings: A blank in the SVN column means that the SubVersion base matches the SALTed script. A slash in the SVN column means that the file is not SubVersioned. A blank in the SALT column means that the workspace script matches the SALTed script.

While most scripts shown by the ScriptManager are probably SALTed they are not necessarily SubVersioned. A script that is not SubVersioned is indicated by a slash (/) in the SVN column.

At start-up time the ScriptManager sorts the table by the SALT column in order to make sure that the trouble makers are on top of the table. In the screen shot however the table is sorted by "Name" as indicated by the small triangle in the column header.

The ScriptManager offers all the features needed to solve the problems indicated by the GUI.

Features

From the GUI the user can:

• Compare the workspace version with the file version with CompareIt!.

• Compare the workspace version with any SALT backup files.

• Compare a SubVersioned script with its SubVersion base file.

• Update all or selected scripts in the workspace with their file version with a single click.
• Load a script anywhere into the workspace.
• Save a workspace script on file.
• Save a workspace script under a different name and/or a different location.
• Delete a script, by default from the workspace but if desired also from file.
• Edit a script.
• Create ordinary (container) namespaces anywhere in the namespace tree.
• Scripts can be added to a list of Favorites. Loading one or more Favorites is a quick thing to do.

Loading multiple scripts from file into, say, a new workspace is a one-click goal. Cherry on the cake is that base classes as well as :Inluded Namespace scripts are loaded if not already available.

Details

Keyboard shortcuts

=

Start CompareIt! and compare the currently selected script in the workspace with its file version.

Ctrl+=

Start CompareIt! and compare the SALTed script with its SubVersion basis. Note that from within CompareIt! you can change both, the workspace and the file version.

Ctrl+U

Update all scripts in the workspace: all scripts that do not match are overwritten with their file version.

Ctrl+L

Open a file-selection dialogue box in order to load a single script.

Ctrl+R

Reload the currently selected script from file.

Ctrl+Del

Delete the currently selected script from the workspace and optionally also from disk.

Ctrl++

Add the currently selected script to the list of favorites.

Ctrl+S

Save the currently selected script.

Ctrl+Shift+S

Save the currently selected script under a different name.

Ctrl+Enter on a row

Edit the currently selected script.

F5

Refresh the table.

Ctrl+F5

Refresh the list of Favorites.

F6

Change the path of the currently selected script.

F8

Load multiple Favorites in one go.

F9

Create an ordinary namespace.

F10

Start Windows Explorer on the folder the currently selected script was loaded from.

F12

Start the Favorite Manager.

Double-click on a row

Edit the currently selected script.

Menu commands

Although literally all commands can be triggered by a keyboard shortcut, they are accessible via menus as well, either from the menu bar or from the context menu.

The "File" menu

... situated in the menu bar:

The "Command" menu

... situated in the menu bar:

The "Favorites" menu

... situated in the menu bar:

The context menu

How to use it

1. Download ScriptManager.zip.

2. Unzip the files and save them in their future home directory.

3. Call the function #.ScriptManager.SetHomepath and pass the name of that directory as right argument. The function saves the name of that directory in the Windows Registry for future use.

4. Copy the namespace #.ScriptManager from the workspace ScriptManager into your workspace. For using #.ScriptManager from ⎕SE see below.

To start the #.ScriptManager run this statement:

      #.ScriptManager.Run ''

If you want to highlight a particular script right from the start:

      #.ScriptManager.Run #.ScriptManager

ScriptManager as a Dyalog User Command

ScriptManager can be used as a User Command. For details see UserCommands/ScriptManager.

Project Page

For bug reports, future enhancements and a full version history see ScriptManager/ProjectPage

Version Information

CategoryAplTree