For latency constraints, VR need to deal with rendering locally on a good GPU. ParaViewGlance rely on vtk.js which allow WebVR. For ParaViewWeb, we have 2 mode of operation, remote and local rendering.
When doing remote rendering, we just send images which won’t work for VR. In local rendering mode, we send a geometry extract to vtk.js which does support VR in the same fashion as Glance but we did not exposed the control to switch to VR graphically.
ParaViewWeb rely on a full feature ParaView which has many readers and filters.
ParaViewGlance on the other hand just rely on vtk.js for some readers and all its rendering along with itk.js for more medical oriented readers. The readers from itk.js are in fact the C++ version compiled to WebAssembly. This would be the way to go for vtk.js to add mode VTK/C++ readers to Glance. But that part is still WIP.
Regarding your questions:
- ParaViewWeb could be used to do VR but the main driver should be where is the data and how do you want to deploy your web application? Those will actually tell you if any solution is indeed viable.
- Yes via WebAssembly and @thewtex might be able to talk more about this.
- I would need more informations as the key points that should drive your decision are missing here.
HTH,
Seb