Hi Yumin,<br><br>Compiling my XML to expose VTK native filters produces a so/dll library that can be autoloaded in ParaView. However, I would take advantage on the fact that this XML may be shared to somebodyelse without the need to own "ParaView from source". The wiki says: "Alternatively, we can simply load the XML from the <b>Plugins Manager</b> (just select the file type to be *.xml in the file open dialog)". I want this because of deployment issues see thread "<font size="2"><span id=":1ng" class="hP">About on-line available binaries for next release</span></font>" )<br>
<br>- What have I to add in the XML to give him the same behaviour than its corresponding compiled library?<br><br>Furthermore, I thought that my Autostart plugin (called "PVCustomizer") was unable to autoload because it depends on my ParaviewVTK XML plugin. But that is not the case: Even if I load the native VTK filters description with the compiled version, my PVCustomizer is loadable through the GUI, but it shows the message "Loaded, but .....\PVCustomizer.dll, is not a server manager plugin!" and no version is displayed although my CMakeLists contains the following lines:<br>
<br>##################################################<br># AUTOSTART PLUGIN --------------------------------------------------<br> QT4_WRAP_CPP(MOC_SRCS PVCustomizer.h)<br> <br># Macro for auto-start plugins. We specify the class name<br>
# and the methods to call on startup and shutdown on an instance of that class.<br># It fills IFACES and IFACE_SRCS with proper values as needed by ADD_PARAVIEW_PLUGIN macro.<br> ADD_PARAVIEW_AUTO_START(IFACES IFACE_SRCS <br>
CLASS_NAME PVCustomizer # the class name for our class<br> STARTUP onStartup # specify the method to call on startup<br> SHUTDOWN onShutdown # specify the method to call on shutdown<br> )<br> <br># Create a plugin for this starter <br>
ADD_PARAVIEW_PLUGIN(PVCustomizer "1.0"<br> REQUIRED_ON_CLIENT <br> GUI_INTERFACES ${IFACES} <br> SOURCES PVCustomizer.cxx ${MOC_SRCS} ${IFACE_SRCS}<br> REQUIRED_PLUGINS ParaviewVTK)<br> <br> TARGET_LINK_LIBRARIES( PVCustomizer VesselExtractionVTK )<br>
######################################################################<br><br>I checked "Autoload", having no effect when I restart ParaView...<br><br>I looked at the sources, but I cannot understand now why this message is displayed. I will give a try with a step-by-step procedure.<br>
<br>Thanks a lot for your time, Yumin, and sorry for disturbing...<br>
<br>Best regards,<br>Jerome<br><br><br><div class="gmail_quote">2009/10/26 Yumin Yuan <span dir="ltr"><<a href="mailto:yumin.yuan@kitware.com" target="_blank">yumin.yuan@kitware.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Jerome,<br>
<br>
You can try to compile your xml into a plugin, which will also solve<br>
your the Version problem<br>
<br>
Check "Enabling a filter in VTK" section on the wiki:<br>
<a href="http://paraview.org/Wiki/Plugin_HowTo" target="_blank">http://paraview.org/Wiki/Plugin_HowTo</a><br>
<font color="#888888"><br>
Yumin<br>
</font><div><div></div><div><br>
On Mon, Oct 26, 2009 at 11:39 AM, Jérôme <<a href="mailto:jerome.velut@gmail.com" target="_blank">jerome.velut@gmail.com</a>> wrote:<br>
> Hi Yumin,<br>
><br>
> Thanks a lot for your interest !! However...<br>
><br>
>><br>
>> I assume once you load your xml plugin from the plugin_loader, and<br>
>> check the "Auto Load" checkbox, the next time you start paraview, your<br>
>> xml plugin is loaded automatically, no?<br>
><br>
><br>
> That's my problem: it is not loaded even in this case... Attached is a<br>
> minimal xml that exposes vtkImageMathematics to paraview filter list. I<br>
> cannot auto-load it.<br>
><br>
>><br>
>> Now regarding the warning message, I believe it is due to the new<br>
>> addition to ADD_PARAVIEW_PLUGIN macro in ParaViewPlugins.cmake (see<br>
>> below), and the version shown in the plugin_loader_GUI refers to<br>
>> plugin "Version" you set when calling ADD_PARAVIEW_PLUGIN in<br>
>> CMakeLists.txt<br>
><br>
> Yes, my CMakeLists contains the version specification for the cxx plugins.<br>
> But thank you for the update about REQUIRED_PLUGINS, I was hoping that it<br>
> will solve my problem. So I set the PVCustomizer (cxx plugin, version "1.0"<br>
> in the CMakeLists) requiring the XML "ParaviewVTK". But I cannot load<br>
> "ParaviewVTK", so making the former depending on the latter is quite<br>
> awkward... Finally, you made me progressing and I have a more precise<br>
> question :<br>
> - How to set the version of a plugin that is only an XML description of<br>
> VTK filters? -ie I don't have a CMakeLists for this...-<br>
><br>
> Thanks again Yumin!<br>
><br>
> Jerome<br>
><br>
>><br>
>> On Fri, Oct 23, 2009 at 4:34 AM, Jérôme <<a href="mailto:jerome.velut@gmail.com" target="_blank">jerome.velut@gmail.com</a>> wrote:<br>
>> > Hi,<br>
>> ><br>
>> > ParaView-CVS brought a good surprise for me a few days ago. The plugin<br>
>> > loader has been rewrote and is now offering an auto-load option that is<br>
>> > very<br>
>> > useful.<br>
>> > However, I have an XML description of a lot of VTK native filters that<br>
>> > cannot be opened automatically. I have to "Load new" each time. Then, no<br>
>> > problem, the filters are exposed in the menu. But the plugin loader<br>
>> > gives a<br>
>> > warning message (see screenshot attached) and no "Version" (effectively,<br>
>> > the<br>
>> > XML doesn't have a "version=" element)...<br>
>> ><br>
>> > Second, I have an AutoStartPlugin that shows exactly the same problem<br>
>> > (PVCustomizer). The reason, I think, is that this plugin depends on VTK<br>
>> > filters (SplineFilter) that is described in the previous XML...<br>
>> ><br>
>> > Can someone tell me how to make the XML plugin 'autoloadeable' ? I<br>
>> > wonder if<br>
>> > it will solve the second problem...<br>
>> ><br>
>> > Thanks a lot!<br>
>> ><br>
>> > Jerome<br>
>> ><br>
>> > _______________________________________________<br>
>> > Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
>> ><br>
>> > Visit other Kitware open-source projects at<br>
>> > <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
>> ><br>
>> > Please keep messages on-topic and check the ParaView Wiki at:<br>
>> > <a href="http://paraview.org/Wiki/ParaView" target="_blank">http://paraview.org/Wiki/ParaView</a><br>
>> ><br>
>> > Follow this link to subscribe/unsubscribe:<br>
>> > <a href="http://www.paraview.org/mailman/listinfo/paraview" target="_blank">http://www.paraview.org/mailman/listinfo/paraview</a><br>
>> ><br>
>> ><br>
>><br>
>><br>
>><br>
>> --<br>
>> ~~~~~~~~~~~~~~~~<br>
>> Yumin Yuan<br>
>> R&D Engineer<br>
>> Kitware Inc.<br>
>> <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
>> Phone : (518) 881-4936<br>
>> email : <a href="mailto:yumin.yuan@kitware.com" target="_blank">yumin.yuan@kitware.com</a><br>
>> ~~~~~~~~~~~~~~~~<br>
><br>
><br>
<br>
<br>
<br>
</div></div>--<br>
<div><div></div><div>~~~~~~~~~~~~~~~~<br>
Yumin Yuan<br>
R&D Engineer<br>
Kitware Inc.<br>
<a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
Phone : (518) 881-4936<br>
email : <a href="mailto:yumin.yuan@kitware.com" target="_blank">yumin.yuan@kitware.com</a><br>
~~~~~~~~~~~~~~~~<br>
</div></div></blockquote></div><br>