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...@kitware.com> 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 revisited or cleanup since their > inception. I would like to collect such feature requests so we can > take all such things into consideration when cleaning that up. > > Utkarsh > > On Fri, Jan 17, 2014 at 5:57 PM, Burlen Loring <blor...@lbl.gov> wrote: > > 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 are > distributed > > with PV, and enabled by deafult, Couldn't the server side load trigger > the > > client load automatically? That would be a nice improvement for the > static > > link case, where we'd still want to make use of some of the view/rep > > plugins. > > > > > > On 01/17/2014 02:15 PM, Utkarsh Ayachit wrote: > >> > >> 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. Anything else, shouldn't. > >> > >> Utkarsh > >> > >> On Fri, Jan 17, 2014 at 5:12 PM, Burlen Loring <blor...@lbl.gov> wrote: > >>> > >>> 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_ON_SERVER flag fix this? > in > >>> other words is it just for readers? or does it work with other plugins > as > >>> well? > >>> > >>> Burlen > >>> > >>> > >>> On 01/16/2014 09:37 AM, Utkarsh Ayachit wrote: > >>> > >>> 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 > >>> REQUIRED_ON_SERVER) > >>> > >>> That should do the trick. > >>> > >>> Utkarsh > >>> > >>> > >>> _______________________________________________ > >>> 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