6 ms·
Not sure what you're talking about. Qt 5 didn't remove anything that was there in Qt 4 [1], and added quite a few nice things like native Wayland support and mo
by majewsky 9y ago
Not sure what you're talking about. Qt 5 didn't remove anything that was there in Qt 4 [1], and added quite a few nice things like native Wayland support and more OpenGL integration.
Sure, the main development focus is on QML etc., but that's mostly because desktop is a more mature platform than mobile.
[1] Except for the QtWebkit to QtWebengine transition perhaps. I haven't followed that very closely.
- nikanj 9y agoThe main development focus is the very thing I was curious about. I remember Qt being slow to support new things eg. high dpi, unless you were using QML. Getting the "feel" of a company's priorities can be hard, if you're not actively using their platform. I was hoping someone on HN had a somewhat realistic picture of where Qt is going these days.
- casione 9y agoIt looks to me like they're very underfunded and have completely lost focus. The high DPI "debacle" is a good proof of it.
- shaan7 9y agoSure /s. We have a Qt app with GUI completely written in Qt. Scales pixel perfect on HiDPI out of the box as long as you make sure to not hardcode pixel values.
- seba_dos1 9y agoThings have definitely accelerated since Nokia regarding desktop platforms. High DPI support has gone through a few iterations and is working pretty well now. Also, Qt is now using open governance model. Qt Quick is still important, but I wouldn't say it's the single, most important thing it used to be anymore.
- carlos22 9y agoNow the focus of QML is mostly embedded where it really shines. Desktop and mobile is still possible with qml.
- jhasse 9y ago> native Wayland support It's still pretty unusable though :/ The default for Qt apps is via Xwayland in Fedora for example.
- majewsky 9y agoI'm using some KDE apps under Wayland (Sway, to be precise), and they're definitely not running under Xwayland (as confirmed by `xlsclients`). There is a lot of scaling confusion, but it's far from "unusable". Just not pretty.
- jhasse 9y agoMust have been some bug with my configuration then: There were scaling issues resulting in some buttons being unclickable.
- pjmlp 9y agoAll new APIs are done with focus of improving the QML experience. For embedded and mobile deployments, QML is the only option. If you try to use a common C++ widget dialog, you will get a tiny desktop like window, regardless of the platform.
- eql5 9y agoEver heard of QCoreApplication::setAttribute(Qt::AA_EnableHighDpiScaling); (to be set before creating the QApplication instance).
- pjmlp 9y agoHow does it help, when displaying a tiny file selection dialog on an Android device? https://bugreports.qt.io/browse/QTBUG-42491 https://bugreports.qt.io/browse/QTBUG-42491
- eql5 9y agoThese file dialogs are not for mobile! But it's easy to make your own ones, please see: https://gitlab.com/eql/EQL5-Android/blob/master/screenshots/REPL-file-dialog.png https://gitlab.com/eql/EQL5-Android/blob/master/screenshots/... The above is on an android tablet; but it displays perfectly fine on phones, too. Just see the sources of the above project for implementing such a dialog: https://gitlab.com/eql/EQL5-Android/blob/master/examples/my/qml/ext/FileBrowser.qml https://gitlab.com/eql/EQL5-Android/blob/master/examples/my/... https://gitlab.com/eql/EQL5-Android/blob/master/examples/my/qml/ext/FileDelegate.qml https://gitlab.com/eql/EQL5-Android/blob/master/examples/my/...
- joezydeco 9y agoQt5 dropped the QWindowing Server for embedded platforms.