2 ms·
There is no way for any toolkit that's doing its rendering in WebAssembly to match font rendering with your operating system. Keep in mind though that editor de
by seba_dos1 8y ago
There is no way for any toolkit that's doing its rendering in WebAssembly to match font rendering with your operating system. Keep in mind though that editor demo is just one of already existing Qt's examples shown working inside the browser. I don't think any author of Qt based text editor will get excited that it will now be able to run inside the browser. However, there are plenty of other use cases that can actually get one very excited - for me personally the biggest deal is having Qt Quick working in the browser.
- Tehdasi 8y ago> There is no way for any toolkit that's doing its rendering in WebAssembly to match font rendering with your operating system. It's just pixels. Barring patents a wasm program can text any goddamn way it wants to.
- seba_dos1 8y agoOf course. It just has no way to know how the system would do it, as the system can also do it any goddamn way its user wants it to.
- danShumway 8y ago> There is no way for any toolkit that's doing its rendering in WebAssembly to match font rendering with your operating system. Sure there is - put the text in the DOM. WebAssembly is just a runtime, it has nothing to do with whether you display your stuff in Canvas or via the DOM. If you were writing an app in Javascript, you wouldn't bundle a text engine into it and then bypass the DOM for all of your rendering. Why is WebAssembly different?
- johncolanduoni 8y agoThen it wouldn't be "doing its rendering in WebAssembly". Even if you use that term very broadly, at the moment WebAssembly can't even interact with the DOM without going through JavaScript.
- TimTheTinker 8y ago> at the moment WebAssembly can't even interact with the DOM without going through JavaScript. Sounds like a good proposal for the WHATWG.
- pjmlp 8y agoThat is already being done as part of WebAssembly roadmap.