Re: [Paraview] ParaView 4.1.0 server-side reader plugin

2014-01-27 Thread Burlen Loring
here it is, assigned to you. http://paraview.org/Bug/view.php?id=14542 On 01/20/2014 06:51 AM, Utkarsh Ayachit wrote: Burlen, That's a good point. Mind reporing a bug for this? Upgrading the ParaViewPlugins.cmake file has been on my wish list for a while now. They macros have never been revis

Re: [Paraview] ParaView 4.1.0 server-side reader plugin

2014-01-20 Thread Andy Bauer
I thought I fixed all of the reader and writer plugins in the ParaView/Plugins directory to be server side only, unless they needed to modify the GUI (maybe the SLAC reader did). I didn't check on any of the other plugins though. On Mon, Jan 20, 2014 at 9:51 AM, Utkarsh Ayachit < utkarsh.ayac...@

Re: [Paraview] ParaView 4.1.0 server-side reader plugin

2014-01-20 Thread Utkarsh Ayachit
Burlen, That's a good point. Mind reporing a bug for this? Upgrading the ParaViewPlugins.cmake file has been on my wish list for a while now. They macros have never been revisited or cleanup since their inception. I would like to collect such feature requests so we can take all such things into c

Re: [Paraview] ParaView 4.1.0 server-side reader plugin

2014-01-17 Thread Burlen Loring
Thanks for the clarification. It'd be helpful if all of the builtin plugins that supported server only were setup that way. If they're not already that is. Could the representations and view plugins also be supported seamlessly with out user intervention in a static link? Re: the plugins that

Re: [Paraview] ParaView 4.1.0 server-side reader plugin

2014-01-17 Thread Utkarsh Ayachit
Burlen, It would work for everything, but for plugins that really need client-side plugin to be loaded e.g. representation plugins, view plugins, you should not do this. In other words, any plugin that only is needed on the data processing side should indeed always use REQUIRED_ON_SERVER flag. Any

Re: [Paraview] ParaView 4.1.0 server-side reader plugin

2014-01-17 Thread Burlen Loring
Hi Utkarsh and Andy, static linking *really* improves performance on Hopper. One issue though is that plugins are automatically "loaded", so when connecting to a statically linked server the plugin manager immediately pops up and requests that the user load all the plugins. Does the REQUIRED_O

Re: [Paraview] ParaView 4.1.0 server-side reader plugin

2014-01-16 Thread Utkarsh Ayachit
By default plugins are treated as "REQUIRED_ON_SERVER" and "REQUIRED_ON_CLIENT". Simply add a REQUIRED_ON_SERVER flag in your add_paraview_plugin(...) call. For example: ADD_PARAVIEW_PLUGIN(MyReader "1.0" SERVER_MANAGER_XML MyPNGReader.xml SERVER_MANAGER_SOURCES vtkMyPNGReader.cxx REQU

Re: [Paraview] ParaView 4.1.0 server-side reader plugin

2014-01-16 Thread Paul Edwards
I get the same error message for reader plugins with linux server and client. Regards, Paul On 16 January 2014 16:40, Favre Jean wrote: > > Nice work on releasing 4.1! Thanks to all. > > I read with interest the discussion about server-side plugins, and > modified my custom plugins according

[Paraview] ParaView 4.1.0 server-side reader plugin

2014-01-16 Thread Favre Jean
Nice work on releasing 4.1! Thanks to all. I read with interest the discussion about server-side plugins, and modified my custom plugins accordingly. http://www.kitware.com/blog/home/post/594 installed a windows 64-bit pre-compiled, connected to my server, and indeed, I can visualize custom d