<div dir="ltr">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.<div>
<br></div><div>In case of extending what is available, none of the existing JavaScript will be aware of your new stuff, hence won't use it.</div><div><br></div><div><div>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.</div>
</div><div><br></div><div>Hope that make some sense,</div><div><br></div><div>Seb</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Nov 12, 2013 at 4:32 PM, kyr <span dir="ltr"><<a href="mailto:akyrieleis@gmail.com" target="_blank">akyrieleis@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Seb,<br>
<br>
the only thing still unclear: it seems several functions (such as<br>
resetCamera(), getPipeline(), updateDisplayproperty(), addSource(), ..)<br>
which are already defined (using @exportRpc) in the derived classes within<br>
protocol.py can be called without the need for the<br>
session.call(vtk:method..) construct.<br>
<br>
I would define a custom class in the same way. When do I need the<br>
session.call construct and when not ?<br>
<br>
Thanks<br>
<br>
k.<br>
<br>
<br>
<br>
--<br>
View this message in context: <a href="http://the-unofficial-paraview-developers-forum.34153.x6.nabble.com/paraview-web-4-pipeline-tp2618p2623.html" target="_blank">http://the-unofficial-paraview-developers-forum.34153.x6.nabble.com/paraview-web-4-pipeline-tp2618p2623.html</a><br>
<div class="HOEnZb"><div class="h5">Sent from the The Unofficial ParaView Developers Forum mailing list archive at Nabble.com.<br>
_______________________________________________<br>
Paraview-developers mailing list<br>
<a href="mailto:Paraview-developers@paraview.org">Paraview-developers@paraview.org</a><br>
<a href="http://public.kitware.com/mailman/listinfo/paraview-developers" target="_blank">http://public.kitware.com/mailman/listinfo/paraview-developers</a><br>
</div></div></blockquote></div><br></div>