Tiny edits

parent 5aa82e85
......@@ -61,7 +61,7 @@ Naturally, instead of a device (<i>Raspberry Pi in this case</i>) there could be
Let's now highlight a couple of points we've just learnt about the feature:
<ul>
<li>The application itself <b>doesn't not</b> run inside a web-browser. Web-browser <b>only renders</b> its GUI;</li>
<li>The application itself <b>does not</b> run inside a web-browser. Web-browser <b>only renders</b> its GUI;</li>
<li>So it is <b>neither</b> video-streaming, <b>nor</b> mirroring. It is about "decoupling" application's GUI and showing it in a web-browser;</li>
<li>Since it's for OpenGL (ES) things only, WebGL streaming does not work with Widgets or any other non-OpenGL stuff.</li>
</ul>
......@@ -289,11 +289,11 @@ Another noticeable aspect of WebGL streaming is so-called "zero install" concept
Some of you might ask, what is the point of relying on WebGL streaming in the first place? Since it's all about web-browser, one can just take a regular web-server and create a web-application - result will be almost the same: backend is hosted on the remote device and HTML-based GUI is rendered in the web-browser.
That is a very good an fair question. I actually have some experience in web-development, so I asked this question myself. So let's try to answer it, hopefully without starting yet another holy war.
That is a very good and fair question. I actually have some experience in web-development, so I asked this question myself. Let's try to answer it, hopefully without starting yet another holy war.
Indeed, in some cases it is enough just to have a simple REST API, especially if you only need to get some plain text data values. So it is likely that Qt-based application with WebGL streaming would be an overkill for such purpose.
However, in more sophisticated scenarios (<i>for example, when you need to control some hardware</i>) Qt-based application with WebGL-streamed GUI might fit better. I would also mention that creating a complex, appealing and performant frontend is (considerably) easier with Qt Quick rather than with HTML/CSS/JS, but this statement does look like a beginning of yet another holy war, so I'll keep that as my personal opinion.
However, in more sophisticated scenarios (<i>for example, when you need to control some hardware</i>) Qt-based application with WebGL-streamed GUI might fit better, because that way you'll get a powerful backend (<i>C++/Qt</i>), and I would also mention that creating a complex, appealing and performant frontend is (<i>considerably</i>) easier with Qt Quick rather than with HTML/CSS/JS, but this statement does look like a beginning of yet another holy war, so I'll keep that as my personal opinion.
And the last thing worth to mention here - if you already have a Qt-based application, then WebGL streaming is an obvious option, because it will cost you nothing to have a remote GUI for it.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment