3 ms·
If web-Qt goes widespread you'll be editing QML scripts (which is much more pleasant for applications than CSS scripts) and installing WebGL/WebVulkan hooks/sha
by de_watcher 8y ago
If web-Qt goes widespread you'll be editing QML scripts (which is much more pleasant for applications than CSS scripts) and installing WebGL/WebVulkan hooks/shaders.
So that's probably a question of familiarity.
- martin_ky 8y agoYes, this. The HTML language and DOM model is inadequate for implementing interactive user interfaces. It's a text document markup language after all. QML has its own DOM structure and a library of primitive visual elements called QtQuick. QML and HTML are very similar in fact. The main difference though is, that the QML language and its library of primitive elements was designed from the ground up as the language for building interactive, fluid, animated user interfaces. Consider something trivial as centering a user control within a parent control. Good luck getting it right with HTML and CSS in a way that works across browsers. With QML you just write: Rectangle { anchors.centerIn: parent } Now I don't say HTML can be replaced by this. I am advocating, that both technologies have their relevant use cases. They could coexist in a browser. I can imagine even mixing them together: QML for the layout, user controls and interactions with chunks of inline HTML for text formatting and document embedding, or vice-versa. There is some discussion on this from last year - https://news.ycombinator.com/item?id=14894937 https://news.ycombinator.com/item?id=14894937