Customization usingAny time a StageTool module loads a TCL file, it looks for a user-defined configuration file as well, and will load that after its normal TCL file if it finds one. These "config" files normally have the same names as the original files, but are stored in a special directory called
config. The modules look in several places for these files: first, it looks in the directory where Geomview was launched for a directory called
configand looks for the file there. Then it looks in the user's home directory for a directory called
.StageTools/config. If not found, it looks in the main StageTools directory for a
configdirectory (whichever one it is) should contain a directory hierarchy mimicking the one in the main
StageToolsdirectory. For example, if CenterStage loads
StageTools/module/CenterStage/file.tcl, then it will look for
configdirectory contains one.
Note that the original TCL file is loaded first, then the
configversion. Thus your configuration files need not include all the code that you are not changing, only the routine or commands that you need to modify. Since the configuration files are all stored in the same
configdirectory, it is easy tell what file you have modified, and copy these modifications to any new distribution (after comparing the modified routines to the new ones to see if anything has been changed that you need to handle differently).
[More examples should be given.]