QML or traditional gui?
-
Denis, it will be internal science app with an interface like adobe lightroom.
Won't it be painful to create such UI with qml? As I understand it intends to quick(it's even calls Qt Quick, huh;-) creation of apps.
And important question - won't qtgui be totally replaced with qml in future releases? Or they gonna exist together? -
Googled a bit for lightroom sreenshots (never used it). I think that a best approach for is using QML for most of UI and widgets where it is needed. But also you can try to write a mockup at QML and look will it work with needed performance or not.
Not aware about replacing qtgui with qml, I'm not troll :) -
"it won’t be ready for production usage for at least year"
Don't know the timespan, but yes, it's not yet production quality.
"it’s not intended to create anything but little apps just for fun"
It will be an essential part at least for mobile applications.
Right now, a lot of features are missing in QML, especially for desktop UIs. Unless you want a UI consisting of rectangles, go for a "classic" UI.
-
It might just end up as "Qml everywhere" :)
-
I hope Nokia isn't like Microsoft, where now WinForms is almost totally replaced with WPF. I think WinForms has many advantages over WPF, eg. loading time. I imagine that the classic QtGui has many advantages over QML (at least at this point). I hope that both will continue to be available.
-
My impression (Disclaimer: I never used Qt Quick so far for my work!) is that it is great for non-standard UIs, independent of where those run. It should make sense to check out Qt Quick for any highly styled application.
If you want "full platform integration" (widgets that behave like in other applications on the system) then I would at this time prefer the classic widgets.
Adobe lightroom looks like it would need a lot of customization and styling... so why not take a day or two to prototype something in Qt Quick? Styling is way simpler there!
About speed: Quick is meant to work great on mobile devices, so it should perform well on a desktop machine:-)
-
[quote author="Denis Kormalev" date="1288824473"]QML is something that you can use as a base of your UI and insert classic widgets where it will be needed (for example if you will want some controls like sliders or checkboxes or spinboxes).[/quote]
Are you sure? I saw many examples for use QML components into a classic app via QDevlarativeView, but none for use qt classic widgets in a QML app.
-
[quote author="Cochise" date="1290101202"]
Are you sure? I saw many examples for use QML components into a classic app via QDevlarativeView, but none for use qt classic widgets in a QML app.
[/quote]You can put your QWidgets inside QGraphicsProxyWidgets, then register them as QML components.
-
Cochise, yes, I'm sure. We are using QML in this way. Main part of GUI is in QML and sometimes there are injections of classic widgets via graphics proxy widgets.
UPD: anselmolsm, or simply insert them as children of root Object, it also works if you don't need a lot of work with them in qml.
-
[quote author="Denis Kormalev" date="1290105154"]
UPD: anselmolsm, or simply insert them as children of root Object, it also works if you don't need a lot of work with them in qml.[/quote]Yep, it also works. I think we should create a wiki page about it with examples, it is not the first time I see this question here in the DevNet Forum. (I won't put the example here because it is not the main subject of this topic :-) )
Cochise, parts of the KDE PIM Mobile use QWidgets in this way. It is not ideal, though.
-
There are some questions and answers to this topic. I added a section on the wiki page about QML:
"Qt Quick":http://developer.qt.nokia.com/wiki/Qt_Quick