4 ms·
In my experience: - Qt Widgets worked fine, but looked like a piece of software made in 2013; - QML looks stylish and is a very nice language, but had a lot o
by vovavili 7mo ago
In my experience:
- Qt Widgets worked fine, but looked like a piece of software made in 2013;
- QML looks stylish and is a very nice language, but had a lot of weird bugs.
Neither of these are issues I'd run with if I were to make a web app.
- irishcoffee 7mo agoWidgets looks like whatever you want them to look like, if the feel like they're from the 2010s its because the implementer made that choice, not because of a limitation in qtwidgets.
- vovavili 7mo agoCould be, but I am mostly speaking about the fact that making a web app looks stylish feels infinitely easier to me.
- irishcoffee 7mo agoQt uses css. Its no different than what you’re describing.
- throwaway2037 7mo agoAs I understand the philosophy of Qt, it does not (for the most part) use native widgets. They seek to draw widgets that match native widgets on a pixel-by-pixel basis. You can also change the look-and-feel (similar to Java Swing widgets) by using what Qt calls "styles". Ref: https://doc.qt.io/qt-6/style-reference.html https://doc.qt.io/qt-6/style-reference.html
- radiator 7mo ago> - Qt Widgets worked fine, but looked like a piece of software made in 2013; That's too bad, because I prefer software which looks like it was made in 1999.
- TeMPOraL 7mo agoAh, the magic times when screen resolutions were large enough to display lots of information, in proper 4:3 aspect ratio, just before they got flattened and the industry started treating them as short view distance TVs.