Stage 1 of tool plug-ins is complete. That means that loadable modules can be used as tools. An example plug-in (just the color picker hacked to be a plug-in instead of a builtin) is available at http://students.cs.byu.edu/~rockwlrs/testmodule.tgz That file should be untarred in your app/tools directory. Now comes the more difficult part -- writing an out-of-process componant that uses the gimpwire protocol and can load these modules and run them. This means that the internal api has to have the same function names as the plug-in api, or the adapter plug-in needs to have functions in it that translate the internal api to the plug-in api. Sven, Mitch, what do you think? Rockwalrus