[Paraview-developers] Writing a plugin : questions

[Nikhil Shetty]

Hi Jean,

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.

However the even stream does not replace the window interactor but instead
we define new interactor styles which work alongside the current style.

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.

If you decide to do the latter then you will have to do the following

1. Add a connection client for OSC (VRPN and VRUI are just connection
clients).
2. Extend the internal event structure to include OSC data.
3. Write an Interactor style to handle OSC events.

All the best

Regards
Nikhil

On Tue, Apr 24, 2012 at 9:13 AM, Jean-Noël Chiganne <
jean-noel.chiganne at limsi.fr> wrote:

> Hi all,
>
> I'm trying to develop a plugin in Paraview and I have some questions.
> I found a wiki page "PlugIn How To" speaking a little about plugin
> implementation but it's still confuse to me.
>
> 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.
>
> 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.
>
> I hope my message is understandable ^^
>
> Thank you for reading  :)
>
> Jean-Noël Chiganne
>
> _______________________________________________
> 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/20120424/68b6750e/attachment.htm>