The UI Components will have native look and feel for the desktop platforms that Qt supports. But it is also possible to implement ones own style.
...
This is because the components rely on certain widget-specific classes such as QStyle to do native rendering.
It appears QWidget styles may well be followed by QML based desktop applications.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2014-03-05
I hope there'll be something. Some of my apps are written in qt5 already and look ugly.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2014-05-16
Are there any changes to this position now that a number of applications seem to be using Qt5 with QWidgets (KF 5 stuff, leapmotion gui, etc).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
None.
If i'll do in a Qt5 style (reg. time and also QWidget/QML gravity), it'll capture some elements of the present bespin, but change several other.
New Qt, new look ;-)
Sorry, i was sure i had responded to this before.
Regarding QWidget vs QML, based on Qt Project Wiki: QtDesktopComponent, and in particular:
It appears QWidget styles may well be followed by QML based desktop applications.
I hope there'll be something. Some of my apps are written in qt5 already and look ugly.
Are there any changes to this position now that a number of applications seem to be using Qt5 with QWidgets (KF 5 stuff, leapmotion gui, etc).
Nope, Bespin is now EOL - sorry.
I won't maintain two GUI styles (that's unrealistic)
Does that mean you are making a new style for Qt5 (or already have, and I haven't noticed), or are you no longer maintaining qt styles at all?
Last edit: beojan 2014-05-16
http://kde-look.org/content/show.php/Virtuality?content=165086
No gradients, no shadows - certainly no glosses ;-)