News for hackers. Stuff that matters.
Re:Qt WebGL Streaming by billconan on Friday July 07, 2017 @12:48PM (#14719860)
I wanted to do the same before. the idea was a platform for software as service.

You see, not all software are ideal to be implemented with pure web technology, although the limitation is quickly going away.

One example is expensive 3D modelling tools, such as Maya and 3D studio max. they are still desktop apps. They suffer from high piracy rate due to their prices. this is a negative feedback loop. You price them higher, you will have more people pirating them.

So this streaming Qt thing is a solution for quickly making a conventional desktop app into a web service and you can charge people with subscription.

This is a combination of the power of server machine and the convenience of the web. As web is not as capable as desktop app on 3D rendering, threading and direct accessing to GPU hardware.

Streaming the software ui is a viable solution for SAAS already, for example, as I know, both office 365 and the online version of libreoffice use this approach.

What I wanted to do was making a platform to make this easy. But I eventually gave up, because I think the biggest developers who would adopt this are heavy 3D graphics companies, and that narrows down to Adobe and Autodesk, as computer graphics is very labor intensive and monopolized. They both are big enough to develop their own solutions.

Re:Qt WebGL Streaming by RussianCow on Friday July 07, 2017 @01:50PM (#14720444)
> This is a combination of the power of server machine and the convenience of the web.

Just to clarify, Qt WebGL Streaming is not a video streaming solution, so the rendering still happens in the browser via WebGL. The hardware requirements to run a graphics app with this feature would be no lower than they would be to just run the Qt app natively, so the only benefit is the portability and accessibility of the web.

Re:Qt WebGL Streaming by Crespyl on Friday July 07, 2017 @05:07PM (#14722116)
Though with applications not already designed to act as thin clients, it could potentially be useful.

It doesn't take much horsepower to just open an application like Blender, but it might be useful to run it on a powerful server and access it from a lighter more power-efficient laptop.

Re:Qt WebGL Streaming by billconan on Friday July 07, 2017 @02:01PM (#14720542)
I was talking about the software streaming use case, not implementation details.

If you search this page, you will find my other threads mentioning my approach, which was based on video streaming.

Re:Qt WebGL Streaming by malkia on Friday July 07, 2017 @05:24PM (#14722242)
To elaborate a bit more here: imagine a tool, which renders things in custom way (engine), but still can expose the rendering commands to WebGL.

This way you can present, preview, annotate, comment, etc. a model, texture, game level if you say to 3rd party contractor and create a field for communication changes, visual diffs, notes, etc.

2-3 years ago I had to retrofit an existing game engine tools into a small size (was able to do it down to 1GB), and had to package this to each contractor.

This might be better.

Re:Qt WebGL Streaming by throwaway2016a on Friday July 07, 2017 @12:54PM (#14719916)
Thank you. You just helped me see a use case I didn't see before.

To paraphrase. Hiding the bulk of the business logic from the client since with Javascript all your source is exposed.

Re:Qt WebGL Streaming by billconan on Friday July 07, 2017 @01:01PM (#14719962)
yes. This enables thin client also. You can purchase a very cheap hardware, a chrome book, for example, to use professional 3D software or other power hungry software that need performant hardware.
Re:Qt WebGL Streaming by RussianCow on Friday July 07, 2017 @01:45PM (#14720410)
I don't think this is true, as the browser is still executing the OpenGL calls via WebGL. This isn't a video streaming solution, it just allows WebGL rendering via the network, so you still need hardware capable of natively rendering the graphics.
Re:Qt WebGL Streaming by billconan on Friday July 07, 2017 @01:59PM (#14720524)
what you said is not necessarily correct. they could render the opengl scene into a texture and send it over to webGL.

they never mentioned that they don't support opengl 4.5 with this webgl backend, so I guess they achieved it by rendering the opengl 4.5 context into a texture map and send that texture map content to web.

but this is just a guess.

Re:Qt WebGL Streaming by izacus on Friday July 07, 2017 @01:17PM (#14720128)
So legitimate users that paid good money for their licenses will now be forced to use a blocky slow streaming video solution instead of fast responsive interface on their Xeon/64GB RAM equipped workstations... AND pay perpetual monthly subscription for something they owned before?

I see that going down well with your actually paying customers :)

Remember, you're not gaining money when you're screwing over paying customers to hunt people who aren't going to pay anyway.

Re:Qt WebGL Streaming by TomMarius on Friday July 07, 2017 @03:32PM (#14721360)
It's not video streaming.
Re:Qt WebGL Streaming by sqeaky on Friday July 07, 2017 @02:30PM (#14720814)
It doesn't have to be the extreme opposite as you described.

Plenty of apps benefit from some stuff being done on the client and the server.

Re:Qt WebGL Streaming by billconan on Friday July 07, 2017 @02:07PM (#14720607)
the experience isn't as bad as you imagined. for example, you can try this first https://www.paperspace.com/gaming and then judge.
Re:Qt WebGL Streaming by joezydeco on Friday July 07, 2017 @03:01PM (#14721099)
So this streaming Qt thing is a solution for quickly making a conventional desktop app into a web service...

With really shitty interaction latency.

Re:Qt WebGL Streaming by spynxic on Friday July 07, 2017 @01:47PM (#14720428)
> But I eventually gave up, because I think the biggest developers who would adopt this are heavy 3D graphics companies

Is lack of viable adoption by users the only reason you gave the project up?