Silhouette has an embedded Python interpreter that can be used to control key bindings and invoke Actions. When Silhouette starts up, it executes the startup.py script, which in turn runs the keybinds.py script. There is a search path when looking for these scripts, so users can modify their scripts without modifying the default scripts.
The Silhouette scripting functionality is implemented in the fx module.
Script Search Path
Silhouette has multiple search paths where it looks for scripts. First, it checks in $(SFX_SCRIPT_PATH), then in $(SFX_USER_PATH)/scripts. These can easily be overridden on a per-user basis by setting the environment variables. Finally Silhouette looks in $(SFX_RESOURCE_PATH)/scripts, where SFX_RESOURCE_PATH is the path to the Silhouette resources directory on Windows and Linux, and the Resources bundle folder on Macintosh OSX.
In an environment where the stock Silhouette install lives on a server and cannot be written to by a normal user, the easiest way to support user-specific scripts is to set SFX_SCRIPT_PATH to some writable location in the user's home directory, such as $HOME/Silhouette/scripts. When adding user-defined Actions, you should copy the entire actions directory to the new location, and add your custom actions to that.
The Silhouette Console can be used to enter interactive scripts. This is useful for running quick code snippets or testing scripting commands. The fx module is imported automatically in the interactive console.
For example, load a Project and then open the Console tab. Press Enter until you see a >> prompt, and type the following command:
The current project name will be printed to the console.
User Interface Scripting
Most of the UI functions in Silhouette can be controlled by custom keybinds, which are normally defined in keybinds.py. Keys can be configured to perform simple, global operations such as activating a control, or complex operations such as toggling states or cycling through modes each time a key is pressed. Binds can also examine the current node and tool to perform different operations depending on the current state.
The easiest way to get familiar with key binding is to examine the default keybinds file. More information on the bind functions can be found in the Scripting Reference.
Silhouette Actions are commands, written as scripts, that show up in the Actions menu. Actions can operate on the Silhouette object model with proper undo/redo behavior, execute rendering loops, import/export data using custom formats, and other powerful operations.
An Action is implemented as a Python class that is subclassed from fx.Action. It must implement two functions, available() and execute().
available() is called to determine if the Action can be executed with the current Silhouette state. If an Action requires one or more selected objects, for example, it should check the selection to make sure there are enough selected objects, and return True if everything is order or False otherwise. An assertion can also be used to return a message that is displayed in the status bar when the action is hovered over, in the event the action is not available.
execute() is called to actually perform the command. The action should use an undo block if it manipulates the object model, or it can clone the project and work from the copy if it needs to manipulate some state for rendering.
Actions can create their own sub-menus by prefixing their label with the sub-menu name followed by the '|' character.
The easiest way to get familiar with actions is to examine the bundled actions, found in the scripts/actions directory. Many actions also make use of some helper functions and classes found in the scripts/tools directory.
More information on the various Action functions can be found in the Scripting Reference.
Hooks can be used to perform various operations when certain events happen. The available hooks are:
|startupComplete||called after startup initialization finishes|
|project_selected||called when then active project changes|
|node_selected||called when the active node changes|
|post_load||called after a Project is loaded|
|pre_save||called just before a Project is saved|
|post_saved||called just after a Project is saved|
|pre_render||called just before rendering begins|
|post_render||called just after rendering finishes|
|post_save_frame(frame, path, type)||called just after a frame is saved during rendering|
Hooks are assigned by editing the fx.hooks dictionary, usually in startup.py.
Hook Example: node_selected
# set the view mode to 'Foreground' each time a 'Roto' node is selected def nodeSelected(): node = activeNode() if node != None and node.type == "RotoNode": fx.viewer.setViewMode(1) fx.hooks["node_selected"] = nodeSelected
Hook Example: post_load
# parse the project name for a version field, and set an environment # variable with the version number. Later, the variable can be used # in the output format specification def post_load(): p = fx.activeProject() if p: name = p.path name = os.path.basename(name) name = os.path.splitext(name) version = name.split('_')[-1] if version.startswith('v'): os.environ["PROJECT_VERSION"] = version fx.hooks["post_load"] = post_load