On Tue, Mar 30, 2010 at 3:03 AM, Fred Fred <[email protected]> wrote: > Hmmm, what do you call .so plugins and .xml plugins actually? > To create a plugin, you need to specify its interface, that is the > components of its object inspector and where the new filter should appear in > the menus. > And then the linker generates a library, which extension is .so in the case > of a dynamic library on Linux. > So may be the plugin appears in the plugin manager with its extension but > there is only one plugin and the .xml should not appear as far as I know. > And the .xml file allows you to put your new filter in the filter list, or > even create a new submenu with your own plugins grouped into it, which would > avoir the need to go to the plugin inspector to launch them. > Hope it helps.
A .so plugin I have a .h, .cxx, and .xml file that I have compiled into a .so file. A .xml plugin I ONLY have a .xml file that is using existing vtk .cxx/.h files. In the plugin manager, when you load a new plugin, you have to change the file type drop down box to ".xml" to load an xml file directly. Sorry if that wasn't clear before. Thanks, David _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
