Sourcing Custom Plug-ins and Generic Tcl Scripts

Nuke Custom Plug-ins

The Nuke developer’s kit (NDK) allows developers to create and compile their own binary plug-ins.

To Source a Custom Plug-in

1.

Place the plug-in file in the plug-in path directory. Its name should include a .dll (on Windows), .so (on Linux) or .dylib (on Mac) extension.

For more information on plug-in path directories, see Loading Gizmos, NDK Plug-ins, and Python and Tcl Scripts.

2.

Create a menu option referencing the plug-in file (see Defining Custom Menus and Toolbars).

Or instruct artists to invoke the plug-in by opening the Script Editor and entering nuke.load ("plug-in name") where plug-in name stands for the name of the plug-in without the extension.

Sourcing Tcl Procedure

A Nuke script or gizmo is in fact a Tcl procedure (script). Thus, Nuke also allows you to hand code generic Tcl procedures to automate Nuke in various ways.

To Source a Generic Tcl Procedure

1.

Place the Tcl procedure file in the plug-in path directory. Its name should include a .tcl extension.

For more information on plug-in path directories, see Loading Gizmos, NDK Plug-ins, and Python and Tcl Scripts.

2.

Create a menu option referencing the plug-in file (see Defining Custom Menus and Toolbars).

Or instruct artists to invoke the Tcl script by opening the Script Editor and entering nuke.load ("procedure/script file name") where procedure/script file name stands for the name of the procedure of script file without the extension.

Tip:  For some code samples of useful Nuke Tcl procedures, look inside the [Nuke directory]/plugins directory.