Qt quick for beginner

[navieh]

Hi,
I have some experiences in traditional Qt Widgets (C++) and would like to learn Qt Quick. I have some doubts to clarify:

• Will qt quick be good for desktop app?
• in which language the logic of the program is written, Javascript or C++?
• will it use qt model-view architecture just like traditional qt widgets?

Many thanks.

[wysota]

Will qt quick be good for desktop app?

It depends on the application. For some it will be useful, for others it will not be.

in which language the logic of the program is written, Javascript or C++?

You can use a mix of the two.

will it use qt model-view architecture just like traditional qt widgets?

It has its own architecture but it can make use of QAbstractItemModel based models.

[navieh]

Hi wysota,
Thank you for your answer.

Could you elaborate in which case it is useful for desktop app?
And what is the architecture of a common qt quick app? I find qt apps adapt Qt Model-View architecture, does a qt quick app stick with a particular architecture too?

[wysota]

Could you elaborate in which case it is useful for desktop app?

If you're wondering whether it is useful for your particular app then probably it's not

And seriously, if your app is mostly about processing data and little about presenting it or presentation needs to be very complex then QtQuick probably won't be much of help. If your app is mostly about (simple) user interaction then using QtQuick can reduce time-to-market significantly.

And what is the architecture of a common qt quick app? I find qt apps adapt Qt Model-View architecture, does a qt quick app stick with a particular architecture too?

Qt apps can adapt model-view architecture but they don't have to. It's exactly the same with QtQuick apps -- they can follow model-view-delegate architecture but they don't have to if your system is not about handling data. Usually for a complex app you would write the data backend in C++ and expose it to QtQuick where you could implement the frontend with QML.

[anda_skoa]

And seriously, if your app is mostly about processing data and little about presenting it or presentation needs to be very complex then QtQuick probably won't be much of help. If your app is mostly about (simple) user interaction then using QtQuick can reduce time-to-market significantly.

It is probably more a question of the target device's capabilities.
If it does not have a GPU with good OpenGL/ES support than QtQuick2 is most likely the wrong choice due to its use of an GL scene graph.

QtQuick controls have mostly closed the gap to Qt Widgets.

Cheers,
_

[wysota]

QtQuick controls have mostly closed the gap to QtWidgets.

I wouldn't agree but it's a topic for a separate discussion.