News for hackers. Stuff that matters.
Re:Qt WebGL Streaming by DocSavage on Friday July 07, 2017 @11:51AM (#14719344)
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/

I assume only a subset of OpenGL calls can be sent and things like 3d volume textures would eventually require WebGL2?

Re:Qt WebGL Streaming by microcolonel on Friday July 07, 2017 @04:41PM (#14721895)
In 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.
Re:Qt WebGL Streaming by sctb on Friday July 07, 2017 @05:38PM (#14722336)
Re:Qt WebGL Streaming by oever on Friday July 07, 2017 @04:07PM (#14721625)
> You need a browser with WebGL support. Tested on IE11, Firefox, Chrome, Edge, Chromium."

Or the webgl polyfill created with mesa and emscripten.

Re:Qt WebGL Streaming by agumonkey on Friday July 07, 2017 @05:47PM (#14722411)
Oh I never got to use networked opengl (which existence I learned years after I learned about opengl), that's very nice.
Re:Qt WebGL Streaming by fulafel on Friday July 07, 2017 @03:02PM (#14721115)
I wonder if this is helped by the OpenGL X11 heritage - GLX used to work relatively well over the network.