Workspace Files
When a Workspace is saved, ALD will create a folder of the same name within the ‘workspaces’ folder inside the install folder as described in the Saving A Workspace section.
The Workspace folder will contain the following files when created via ALD:
• sareas.3ad — the file defining ‘areas’ or quick directories set using ^_ar_ variable names
• sdefault_paths.3ad — containing default location paths for loading text, raster graphics and object graphics, as well as the default path for the ‘3d’ folder
• sfctrl.3ad — the font file definitions for those fonts not installed under Windows.
• siconusr.3ic — toolbars, toolbar action definitions and icon definitions.
• simports.3ad — default import options for different file types set using ^_import_ variable names
• spref.3ad — saved application preferences
• stuk.3ad — strings 1000–1099, 2300–2399 and strings numbered greater than 4000 are saved and loaded. However, if this file is edited to change other string numbers, they will also be set using this file.
• swkdefuk.3ad — keyboard definitions
• s3b2p*.3ad — saved print settings (where * might be the number of the print group)
|
|
When a Workspace is active, when saving application preferences, the user will be prompted to save changes to the Workspace version of the system file rather than the install folder version.
|
In addition, two JavaScript files are also created — load.js and unload.js — these will be executed when the Workspace is loaded (load.js) and unloaded (unload.js). They are provided so that developers can execute JavaScript code specific to the Workspace. For example, a set of global functions could be created when the Workspace is loaded for a customer or template solution, and then destroyed when the Workspace is unloaded. Another example, using the 12.2.0.0 enhancement of specifying multiple library paths, would be to point ALD to a specific set of libraries when the Workspace loads, and then remove those libraries from the search list when the Workspace is unloaded.
|
|
The developer is responsible for restoring anything they set in load.js to the default state when the Workspace is unloaded using unload.js — ALD will make no attempt to undo any changes made by load.js.
|
Workspaces can also hold other system files with customisations. These are not saved by the Workspace saving actions, but will be loaded if they are present within the Workspace folder. As with JavaScript objects, the developer is responsible for managing the ‘unsetting’ of any changes within these files. The files allowed are:
• simpuser.3ad
• snumuk.3ad
• suser.3ad, suser2.3ad and suser3.3ad
• scoluser.3ad
• slinesuk.3ad and slinesuser.3ad
• scharuk.3ad
• siconusr.3ic
• stransu.3ad
• sunipair.3ad
• scontext.3ad
• userkeys.3k
• smapsu.3ad
• sidxcoll*.3ad and sidxgrp.3ad
|
|
Files listed above with the ‘uk’ end to the name will use the localised version if the UI language is set — for example, stde.3ad will be loaded and saved if the German interface is being used.
|
