[Paraview] Reader plugin with separate server and client plugin

[Utkarsh Ayachit]

Michael,

You can still build the same plugin. On windows build, just disable
the parts that don't build on Windows.  SInce ParaView does indeed
load separate libraries for the same plugin on server and client, it
will load the linux plugin with reader on the server and the panel
code on Windows. Of course, if the plugin is loaded on Windows client
without connecting to a remote pvserver alone, you may want to provide
dummy reader implementation so that if the user creates that reader it
will fail more gracefully --reporting appropriate errors.

Hope that helps.
Utkarsh

On Tue, Jun 17, 2014 at 7:14 AM, Michael Wild <themiwi at gmail.com> wrote:
> Dear all
>
> I am wondering whether (and if, how) it is possible to develop a
> reader plugin where the server-side plugin is distinct from the
> client-side one. I.e. the server-side plugin would handle the reading
> and processing, while the client-side plugin would mainly deal with
> the properties pane.
>
> The reason I ask for this is that due to portability restrictions, the
> reader only works on Linux, which for us is not a problem. However, we
> would also like to connect with Windows clients, and if the
> client-plugin is dependent on the reader implementation, we can't.
>
> Any hints as to where I can find more information on such a setup
> would be highly appreciated.
>
> Michael
> _______________________________________________
> 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://public.kitware.com/mailman/listinfo/paraview