Qt for WebAssembly widget example gone
-
@lorn-potter
Thank you for your comments.There are also these examples offering the full range of Qt examples.
https://s3.eu-west-2.amazonaws.com/wasm-qt-examples/last/index.htmlThat is useful.
But, now at least, that redirects to the generic https://www.qt.io/qt-examples-for-webassembly. And I see no sign there of a text edit, nor any widgets. Anyone know where or why this has gone?
They are still there, at the bottom of the page under the heading 'Demos & Examples'
There are half a dozen examples there, but as I said the textedit/widgets one is not among those. Have a look --- maybe text edit or a widgets example should be added there.
1.I understand about limitations like no local files, no sub-processes. What about MySQL database access via the Qt classes? Do I assume you cannot have your code access SQL db from browser?
Not at this point. Although someone has now ported sqlite to wasm, which would be the first step.
That is a showstopper for me (no MySQL), but I will watch for future expansions.
I see from your strap-line that you are a senior developer on QtWebAssembly. Thank you for your efforts! It is an interesting technology. For my sins I have spent many years writing using HTML + CSS + JS. Not always as simple as the desktop-type approach. The web assembly client-side approach looks a radical alternative, though the no-server-side and no HTML etc. brings a different set of limitations. I believe I am correct in saying that WASM implements all the (widget) examples via HTML canvas instead of HTML page elements, which is understandable but possibly problematic. I gather than the big boys like Google are supposed to be putting their weight behind WASM, it will be intriguing to see whether future stuff moves over to it....
@jonb
To answer your original question, the textedit example was probably removed from the wasm examples page, because it used an outdated and obsolete version of the pre-release webassembly platform (5.11), which has more issues.Yes, I think webassembly is going to be big. There are issues that need to be worked out - like pthread (relies on SharedArrayBuffer) support is still experimental.
