Details
-
Suggestion
-
Resolution: Unresolved
-
P4: Low
-
None
-
None
-
None
Description
The key to this entire suggestion is the word "native".
I think it would be a welcome addition to Qt if we had a modern, native, hardware-accelerated GUI API.
QWidgets is showing it's age and doesn't cleanly/properly separate backend from frontend. QML is non-native and doesn't cleanly/properly separate backend from frontend either (allows/encourages you to write backend logic in the frontend, via js).
Qt has it's roots in being a native software development framework. That's what attracted me to Qt in the first place, and I think many others came to Qt for that same reason.
Edit: Software-renderer fallback and compile-time syntax/etc verification of the UI definition (whether it's C++ or not) both also seem necessary. I don't recommend a "Turing complete" UI definition format, because then strict compile-time verification becomes extremely difficult, if not impossible (like QML today).
Edit #2: By "Native" I mean native CODE, ie not interpreted at runtime and not requiring a Virtual Machine to execute. I don't mean "native STYLE" relative to the OS/Platform.