News for hackers. Stuff that matters.
Re:Qt for WebAssembly by joezydeco on Tuesday June 19, 2018 @05:01PM (#17350265)
Qt has the option to use an internal font renderer (FreeType, Harfbuzz, or ?), or rely on the host system for one.

Unless Webassembly provides a common type rendering system or links to the Browser's host renderer, I'm not sure this can be fixed.

Re:Qt for WebAssembly by RussianCow on Tuesday June 19, 2018 @05:22PM (#17350383)
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).
Re:Qt for WebAssembly by amelius on Tuesday June 19, 2018 @05:29PM (#17350419)
This 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.
Re:Qt for WebAssembly by seba_dos1 on Tuesday June 19, 2018 @05:39PM (#17350480)
It is "like drawing on a canvas", in some cases like QtQuick it's even working with OpenGL directly.
Re:Qt for WebAssembly by joezydeco on Tuesday June 19, 2018 @06:11PM (#17350702)
Yeah, 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.
Re:Qt for WebAssembly by RussianCow on Tuesday June 19, 2018 @07:33PM (#17351172)
Sorry, yeah, I wasn't talking about Qt specifically, but WASM in general.