If the plugin is composed of C++ code (ui or processing code), what need to be loaded is the compiled library (.dll/.so/.dylib) not the xml. The XML is just when you want to expose some VTK classes to the ParaView GUI with auto generated panel.
To build the ParaView examples you will need to create a new build tree like as follow. mkdir build-examples cd build-examples ccmake ../src-paraview/Examples make And then load the generated library inside build-examples/Plugings/ HelixSource Seb On Fri, Jan 11, 2013 at 4:29 AM, Nico Kruithof <n...@nghk.nl> wrote: > Hello, > > I'm trying to get the HelixSource plugin loaded > (Examples/Plugings/HelixSource). In paraview I added the plugin: > Tools->Manage plugins->add helix.xml. The plugin is loaded as I can create > a helix, however the modified user interface (HelixSource.ui) is not used. > For example, the python code and the output data type are still shown. Are > there other things that I need to set up? > > Nico Kruithof > Visualisation expert, SURFsara.nl > > > _______________________________________________ > 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 > >
_______________________________________________ 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
