Move callback wrapper code from Unity plugin up into Managed-OSVR about osvr-unity

[rpavlik]

The source code in question is InterfaceCallbacks.cs, I think. AFAICT, the whole generated section can be upstreamed in some form (probably have to swap the Unity vec3/quat/matrix types for something general), and I think some basic lifecycle methods would allow replacement of the remaining unity-specific code in that file, leaving a unity-specific class that contains a member of this upstream type, providing access to the clientkit context and calling lifecycle methods based on the frame loop callbacks.

I'm adding some comments that should assist with this. This could start with copying the code "up", then we could review and adapt the Unity code to re-use rather than duplicate, so that this could start without needing to do any Unity development.

[JeroMiya]

Are there interface types that produce more than one report type (per a single source path)? Like, maybe something that supports pose and button callbacks? Or would the different report types be exposed on different source paths?

The reason I ask is that it might be useful to separate the interface callbacks each into their own Interface class, with a single event to subscribe to for that event. Then all the callback classes could derive from a common generic class and/or implement a common interface.

Edit: answered my own question - there are certainly interfaces with more than one supported callback type. e.g. pose interfaces might also support orientation callbacks, and so on.

[JeroMiya]

This can be closed. It will be implemented as part of this issue:
OSVR/Managed-OSVR#7