[Paraview-developers] paraview/web 4 pipeline

[Sebastien Jourdain]

Well the default available protocols have some UI that internally trigger
the session.call("vtk:...") or some method exposed on the viewport. But
ultimately a session.call("vtk:...") is achieved.

In case of extending what is available, none of the existing JavaScript
will be aware of your new stuff, hence won't use it.

So if you are building your own UI, you will need to make such call in your
custom UI to start using the new methods you've exposed.

Hope that make some sense,

Seb


On Tue, Nov 12, 2013 at 4:32 PM, kyr <akyrieleis at gmail.com> wrote:

> Hi Seb,
>
> the only thing still unclear: it seems several functions (such as
> resetCamera(), getPipeline(), updateDisplayproperty(), addSource(), ..)
> which are already defined (using @exportRpc) in the derived classes within
> protocol.py can be called without the need for the
> session.call(vtk:method..) construct.
>
> I would define a custom class in the same way. When do I need the
> session.call construct and when not ?
>
> Thanks
>
> k.
>
>
>
> --
> View this message in context:
> http://the-unofficial-paraview-developers-forum.34153.x6.nabble.com/paraview-web-4-pipeline-tp2618p2623.html
> Sent from the The Unofficial ParaView Developers Forum mailing list
> archive at Nabble.com.
> _______________________________________________
> Paraview-developers mailing list
> Paraview-developers at paraview.org
> http://public.kitware.com/mailman/listinfo/paraview-developers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20131112/aa6b553a/attachment.htm>