This seems like a lot of work. Couldn't Microsoft just support the WebVR API interface in Edge or some other type of AR extension into Edge? That is all I would want. Then I can just use ThreeJS or Babylon.js with it from a normal website, and then there is no need to ship custom desktop applications with embedded. I guess I do not want to ship applications if I don't have to.
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.
HoloJS – A framework for creating UWP applications using JavaScript and WebGL
11–20 of 25 posts
Re: HoloJS – A framework for creating UWP applications using JavaScript and WebGL
#12Interesting. With a little hackery, it should be fairly easy to get this working with PlayCanvas. I'm not sure why it needs to use a new element type though (canvas3D).
Re: HoloJS – A framework for creating UWP applications using JavaScript and WebGL
#13But I'm really happy Microsoft has chosen to create something similar - I had hoped they would. Their implementation seems quite solid, I wonder if it supports libraries like Three.js yet.
If anyone is wondering why you might use this, the reason is pretty simple. Before this, there was only two ways to build HoloLens apps: Unity, or C++/DirectX. DX is great but slow to develop, Unity is fast to develop but requires a ton of prerequisite knowledge, and it consumes a ton of RAM. Baseline for this project will probably be similar to mine (around 15MB) whereas Unity's baseline in my experience is around 10x that at 150MB. This is substantial on HoloLens, because the maximum amount of RAM allotted to any application is 1GB.
I'm looking forward to seeing this bring web developers into the new world of MR. I'll be interested to see if this can be coupled with React VR for rapid prototyping.
Re: HoloJS – A framework for creating UWP applications using JavaScript and WebGL
#14This seems like a lot of work. Couldn't Microsoft just support the WebVR API interface in Edge or some other type of AR extension into Edge? That is all I would want. Then I can just use ThreeJS or Babylon.js with it from a normal website, and then there is no need to ship custom desktop applications with embedded. I guess I do not want to ship applications if I don't have to.
Re: HoloJS – A framework for creating UWP applications using JavaScript and WebGL
#15Earlier quoted context omitted.
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.
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.
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.
Re: HoloJS – A framework for creating UWP applications using JavaScript and WebGL
#16Earlier quoted context omitted.
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.
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 We…
They're provided at `window.getViewMatrix()` and `window.getCameraPositionVector()`. See here: 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 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.
Re: HoloJS – A framework for creating UWP applications using JavaScript and WebGL
#17This seems like a lot of work. Couldn't Microsoft just support the WebVR API interface in Edge or some other type of AR extension into Edge? That is all I would want. Then I can just use ThreeJS or Babylon.js with it from a normal website, and then there is no need to ship custom desktop applications with embedded. I guess I do not want to ship applications if I don't have to.
Re: HoloJS – A framework for creating UWP applications using JavaScript and WebGL
#18UWP = Universal Windows Platform, did not know that.
Re: HoloJS – A framework for creating UWP applications using JavaScript and WebGL
#19Interesting. With a little hackery, it should be fairly easy to get this working with PlayCanvas. I'm not sure why it needs to use a new element type though (canvas3D).
Re: HoloJS – A framework for creating UWP applications using JavaScript and WebGL
#20This seems like a lot of work. Couldn't Microsoft just support the WebVR API interface in Edge or some other type of AR extension into Edge? That is all I would want. Then I can just use ThreeJS or Babylon.js with it from a normal website, and then there is no need to ship custom desktop applications with embedded. I guess I do not want to ship applications if I don't have to.
To be honest, I don't want a webapp. Webapps may have a good thirty second use case, but adter that, i want something thatnis with all my other programs that I can pin to a menu/quick launch bar, that runs in a different process space so that a bug in a different program doesn't take down your program, etc. I want the same UI/UX as a native app, and that's something tat webapps still fail terribly at.
Also, UWP apps are full apps like any other windows app.