<div class="gmail_extra">Hi Jean,<br><br><div class="gmail_quote">On Wed, Apr 25, 2012 at 3:09 AM, Jean-Noël Chiganne <span dir="ltr"><<a href="mailto:jean-noel.chiganne@limsi.fr" target="_blank">jean-noel.chiganne@limsi.fr</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="gmail_extra">Hi Nikhil,</div><div class="gmail_extra"><br></div><div class="gmail_extra">Thanks for your answer !</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">So I'll continue my investigations in the VR plugin and do what you suggest about extending it.</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">When you say "<span style="border-collapse:collapse;color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px">Extend the internal event structure to include OSC data.", do you mean the internal event structure of ParaView or of the VR plugin ?</span></div>
<div class="gmail_extra"><font color="#222222" face="arial, sans-serif"><span style="border-collapse:collapse"><br></span></font></div></blockquote><div><br></div><div>Its just the VR-Plugins internal structure.</div><div>
<br></div><div>-Nikhil.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="gmail_extra"><font color="#222222" face="arial, sans-serif"><span style="border-collapse:collapse"></span></font></div>
<div class="gmail_extra"><font color="#222222" face="arial, sans-serif"><span style="border-collapse:collapse">If someone has a link, I'm still looking for a doc about the XML ServerManager syntax. =)<br>
</span></font></div><div class="gmail_extra"><font color="#222222" face="arial, sans-serif"><span style="border-collapse:collapse"><br></span></font></div><div class="gmail_extra">
<font color="#222222" face="arial, sans-serif"><span style="border-collapse:collapse">Have a good day,<br></span></font></div><div class="gmail_extra"><div class="gmail_quote">
<br></div><div class="gmail_quote">Jean-Noël</div><div><div class="h5"><div class="gmail_quote"><br></div><div class="gmail_quote">2012/4/24 Nikhil Shetty <span dir="ltr"><<a href="mailto:nikhil.shetty@kitware.com" target="_blank">nikhil.shetty@kitware.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="gmail_extra">Hi Jean,</div><div class="gmail_extra"><br></div><div class="gmail_extra">The VRPlugin simply provides a framework to pass alternative event streams. It currently takes VRPN and/or VRUI streams and converts it into an internal event structure. There is a dispatcher which takes these event streams and dispatches to various VRInteractor styles. </div>
<div class="gmail_extra"><br></div><div class="gmail_extra">However the even stream does not replace the window interactor but instead we define new interactor styles which work alongside the current style. </div><div class="gmail_extra">
<br></div><div class="gmail_extra">You could start writing the plugin from scratch by copying the VRPlugin over and deleting unnecessary classes. Alternatively you could extend the plugin cause it has most of the framework to forward (non native) events to the system. </div>
<div class="gmail_extra"><br></div><div class="gmail_extra">If you decide to do the latter then you will have to do the following</div><div class="gmail_extra"><br></div><div class="gmail_extra">1. Add a connection client for OSC (VRPN and VRUI are just connection clients).</div>
<div class="gmail_extra">2. Extend the internal event structure to include OSC data.</div><div class="gmail_extra">3. Write an Interactor style to handle OSC events.</div><div class="gmail_extra"><br></div><div class="gmail_extra">
All the best</div><div class="gmail_extra"><br></div><div class="gmail_extra">Regards</div><div class="gmail_extra">Nikhil</div><div class="gmail_extra"><br><div class="gmail_quote"><div><div>On Tue, Apr 24, 2012 at 9:13 AM, Jean-Noël Chiganne <span dir="ltr"><<a href="mailto:jean-noel.chiganne@limsi.fr" target="_blank">jean-noel.chiganne@limsi.fr</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div>Hi all,<div><br></div><div>I'm trying to develop a plugin in Paraview and I have some questions.</div>
<div>I found a wiki page "PlugIn How To" speaking a little about plugin implementation but it's still confuse to me.</div>
<div><br></div><div>Is there a page explaining all the XML syntax of the ServerManager and ClientManager files ? For instance I tried to compile and use the plugin "MyView" as shown on the wiki page, but I've got an error message when loading it in Paraview "Failed to create a proxy for the requested view type...". As I don't know the XML syntax it's hard to find where the mistake could be.</div>
<div><br></div><div>I have an other question. My goal is to develop a plugin which would make paraview reactive to OSC messages (or VRPN messages, I've seen there is a VR plugin but it's another problem ^^) but I don't know if it's possible ? Actually I don't understand where is the entry point for paraview in the C++ source code of a plugin, and how I can get back Paraview objects instances (as the render windows to get the camera and control it with OSC messages etc). To sum up, I think the final goal is to replace WindowInteractor by an Interactor reacting to OSC events instead of keyboard/mouse events.</div>
<div><br></div><div>I hope my message is understandable ^^</div><div><br></div><div>Thank you for reading :)</div><span><font color="#888888"><div><br></div><div>Jean-Noël Chiganne</div>
</font></span><br></div></div>_______________________________________________<br>
Paraview-developers mailing list<br>
<a href="mailto:Paraview-developers@paraview.org" target="_blank">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>
<br></blockquote></div><br></div>
</blockquote></div><br></div></div></div>
</blockquote></div><br></div>