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.
> Date: Mon, 29 Mar 2010 18:49:57 -0400
> From: [email protected]
> To: [email protected]
> Subject: [Paraview] Loading xml plugins at startup
>
> I added some paths to my PV_PLUGIN_PATH. When I start Paraview, in the
> plugin manager I see the .so plugins in those paths, but not the .xml
> plugins. Is there a reason xml plugins must be loaded manually?
>
> 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
_________________________________________________________________
Consultez vos emails Orange, Gmail, Yahoo!, Free ... directement depuis HOTMAIL
!
http://www.windowslive.fr/hotmail/agregation/_______________________________________________
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
