21 ms·
From an earlier discussion of it: "The OpenGL calls are sent over the network and transformed into WebGL calls in the browser. It’s not video-streaming. The bro
by DocSavage 9y ago
From an earlier discussion of it:
"The OpenGL calls are sent over the network and transformed into WebGL calls in the browser. It’s not video-streaming. The browser is executing WebGL in a canvas. Textures, buffers, glyphs, etc. are sent as well.
You need a browser with WebGL support. Tested on IE11, Firefox, Chrome, Edge, Chromium."
http://blog.qt.io/blog/2017/02/22/qt-quick-webgl-streaming/ http://blog.qt.io/blog/2017/02/22/qt-quick-webgl-streaming/
I assume only a subset of OpenGL calls can be sent and things like 3d volume textures would eventually require WebGL2?
- fulafel 9y agoI wonder if this is helped by the OpenGL X11 heritage - GLX used to work relatively well over the network.
- oever 9y ago> You need a browser with WebGL support. Tested on IE11, Firefox, Chrome, Edge, Chromium." Or the webgl polyfill created with mesa and emscripten.
- microcolonel 9y agoIn this case, they are building the OpenGL ES 2.0 version of Qt, and WebGL is basically fully compatible with OpenGL ES 2.0. It's accelerating the toolkit itself. If you wanted to use GL directly I think you would have the same restrictions.
- sctb 9y agoHN discussion here: https://news.ycombinator.com/item?id=13744631 https://news.ycombinator.com/item?id=13744631
- agumonkey 9y agoOh I never got to use networked opengl (which existence I learned years after I learned about opengl), that's very nice.