[Paraview] paraview web architecture

[Scott Wittenburg]

On Tue, Aug 30, 2016 at 10:29 AM, Daniel Zuidinga <info at seoaachen.de> wrote:

> Hi once again,
>
> what's a good way to learn paraview web?


All the guides we have written are located here:
http://kitware.github.io/paraviewweb/docs/


> I am still struggling a a bit with it's architecture. Protocol.py is the
> entry point?


Not sure what you mean by "entry point".  However, that file has many of
the rpc methods that are available to be called from the web client.  You
can also learn a lot by reading through the methods in there to see how we
use Python to control/manage ParaView.


> When I want for example to change the default background color for all
> renderers where do I have to look? Is this set once or for each renderer?
>

I am not sure whether or not this is something you can set for all
renderers, but you can use the properties panel in the "Visualizer"
application to set the background color.  This a property you will find
under the "View" section.


>
> Another thing I would like to change is that I can open a file from client
> inside a running pv web session so that I can load pv web upfront and load
> files without this long wait time.
>
>
Not exactly sure what you're asking here, but you can have the client load
a file as soon as the connection is established, as Sebastien mentioned in
a previous thread.

Hope this helps,
Scott


> best regards
> Daniel
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/opensou
> rce/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160830/a1f3541a/attachment.html>