4 ms·

This isn't aimed at regular desktop applications it's aimed creating applications for the Hololens, Microsoft's Mixed Reality platform. You could use this to ma

This isn't aimed at regular desktop applications it's aimed creating applications for the Hololens, Microsoft's Mixed Reality platform. You could use this to make desktop apps but I'm not sure the point of a holographic desktop app or what the really means.

iLoch 10y ago
They're referring to Edge on HoloLens, and it's something I've thought a lot about to. Something like `canvas.getContext('webgl-holographic')` to harness holographic space rendering from the browser.
- moron4hire 10y ago
  One thing that is not clear with HoloJS: how do you aquire the head position and orientation on the JS side to be able to do gaze-centered selection (or, more accurately, nose-pointer selection, but people tend to call that gaze)? It seems to pass the view and projection matrices directly to the shader code. I haven't seen where it is available in a scriptable API. It would be better to include an extension to the WebVR API to provide the environment geometry. There is a lot of work going into WebVR applications and frameworks. It'd be a shame if that work couldn't be leveraged for AR. Also, I feel pretty strongly that automatically applying the stereo rendering is a mistake. This prevents being able to do any sort of changes between eyes, as is necessary for displaying stereo photos, photoshperes, or cubemaps. They can be a huge visual fidelity cheat on limited systems.
  - iLoch 10y ago
    > I haven't seen where it is available in a scriptable API. They're provided at `window.getViewMatrix()` and `window.getCameraPositionVector()`. See here: https://github.com/Microsoft/HoloJS/blob/master/HoloJS/HoloJsHost/ScriptingFramework/Window.js https://github.com/Microsoft/HoloJS/blob/master/HoloJS/HoloJ... > It would be better to include an extension to the WebVR API to provide the environment geometry. This is on their radar by the looks of it: https://github.com/Microsoft/HoloJS/issues/4 https://github.com/Microsoft/HoloJS/issues/4 I've also thought about this.. Could be a bit tricky. The meshes are quite large and getting them over the bridge could be a bottleneck. > Also, I feel pretty strongly that automatically applying the stereo rendering is a mistake. This happens to be a limitation that (I believe) is specific to their ANGLE fork, which may change at some point.

iLoch 10y ago

They're referring to Edge on HoloLens, and it's something I've thought a lot about to. Something like `canvas.getContext('webgl-holographic')` to harness holographic space rendering from the browser.

moron4hire 10y ago
One thing that is not clear with HoloJS: how do you aquire the head position and orientation on the JS side to be able to do gaze-centered selection (or, more accurately, nose-pointer selection, but people tend to call that gaze)? It seems to pass the view and projection matrices directly to the shader code. I haven't seen where it is available in a scriptable API. It would be better to include an extension to the WebVR API to provide the environment geometry. There is a lot of work going into WebVR applications and frameworks. It'd be a shame if that work couldn't be leveraged for AR. Also, I feel pretty strongly that automatically applying the stereo rendering is a mistake. This prevents being able to do any sort of changes between eyes, as is necessary for displaying stereo photos, photoshperes, or cubemaps. They can be a huge visual fidelity cheat on limited systems.
- iLoch 10y ago
  > I haven't seen where it is available in a scriptable API. They're provided at `window.getViewMatrix()` and `window.getCameraPositionVector()`. See here: https://github.com/Microsoft/HoloJS/blob/master/HoloJS/HoloJsHost/ScriptingFramework/Window.js https://github.com/Microsoft/HoloJS/blob/master/HoloJS/HoloJ... > It would be better to include an extension to the WebVR API to provide the environment geometry. This is on their radar by the looks of it: https://github.com/Microsoft/HoloJS/issues/4 https://github.com/Microsoft/HoloJS/issues/4 I've also thought about this.. Could be a bit tricky. The meshes are quite large and getting them over the bridge could be a bottleneck. > Also, I feel pretty strongly that automatically applying the stereo rendering is a mistake. This happens to be a limitation that (I believe) is specific to their ANGLE fork, which may change at some point.