Proposed renaming of plugins related to virtual reality
Goal
ParaView currently provides two plugins related to immersive environments or virtual reality. To make it more clear what each one does, and to better reflect the nature of each, we would like to rename them both.
VRPlugin
Rename The VRPlugin
plugin is used in CAVE environments, but beyond what ParaView provides "out of the box", really only adds support for interaction/devices. Still, CAVE
has come up as a suggested replacement for VRPlugin
. Some ideas to consider:
- CAVE (pv-cave, pv2cave, ...)
- immersive interaction
OpenVR
Rename The OpenVR
plugin exposes functionality of the VTK module Rendering/OpenVR
, but is currently being extended (!5319 (merged)) to provide support for OpenXR
as well, allowing the user to build either or both backends and choose at runtime which one ParaView should use. This plugin allows ParaView to work with supported head mounted displays (HMDs) and controllers. Since it will no longer support only OpenVR
, the name needs to be changed to reflect the more general nature of the plugin. At first we wanted to steal the name VRPlugin
, but have moved away from that idea for two reasons: 1) We don't want to create confusion by using a name currently in use, and 2) we don't want "plugin" in the name. Some ideas to choose from or mix/match/combine:
- VR (XR?)
- Immersion
- HMD (pv-hmd, pv2hmd, ...)
I would like to rename the OpenVR plugin as a part of !5319 (merged).
Thoughts/suggestions from the community
Suggestion: the name would express the idea that the plugin is a connector or interface from ParaView to a wide range of other software/systems. For example: pv2xr or pv-xr where xr is the entire field of VR,AR, etc.
No one especially liked xr, but the concept seems generally acceptable.
Suggestion: pv-cave, pv-hmd
There was general agreement that "plugin" should not be included in the name.
Renaming progress
-
VRPlugin -> CAVEInteraction -
OpenVR -> XRInterface