3 ms·
WebAssembly is pretty orthogonal to rendering. The way this would be "fixed" is for WASM to have its own DOM APIs; then, WASM apps could render to the DOM like
by RussianCow 8y ago
WebAssembly is pretty orthogonal to rendering. The way this would be "fixed" is for WASM to have its own DOM APIs; then, WASM apps could render to the DOM like any other web app, so they would inherit all of its benefits (like native font rendering, OS-native input elements, accessibility, etc).
- amelius 8y agoThis would only work if DOM rendering is compatible with Qt's internal API. For example, if rendering in Qt is like drawing on a canvas, where you can later read out pixel-values, then this isn't going to work through the DOM. And it could require a lot of tricks to bring the two APIs together.
- seba_dos1 8y agoIt is "like drawing on a canvas", in some cases like QtQuick it's even working with OpenGL directly.
- joezydeco 8y agoYeah, Qt is not a DOM-based GUI. Both widgets and QML expect an underlying scene graph to be rendered out to a framebuffer or GL texture.
- RussianCow 8y agoSorry, yeah, I wasn't talking about Qt specifically, but WASM in general.