I'm planning to write a program that is especially designed for tablets, the main platform is MeeGo (because I'm taking a contest).
Edited:
My program has following needs:
and I found Qt Quick has the following shortcomings:
So can Qt Quick meet my needs?
This is especially true for a language as powerful and nuanced as C++. We've found throughout our years of training developers from diverse backgrounds that Qt tends to tame the complexity of C++ and provides an excellent framework for programmers of many levels to be productive.
Yes, Qt is still used for desktop, mobile, and even embedded (and medical!) programs in 2020. On the “embedded” front, I am currently working on medical software to control a microscope using Qt. Several automotive companies are using it for dashboards and infotainment systems.
QML code is simpler to write, as it is less verbose than C++, and is not strongly typed. This also results in it being an excellent language to prototype in, a quality that is vital when collaborating with designers, for example. JavaScript can easily be used in QML to respond to events.
Qt is a cross-platform application development framework widely used for developing applications that can run on a wide range of hardware platforms with little to no change in the underlying codebase.
You have a prefect question to ask. QtQuick was originally developed for Qt on mobile devices, and now Qt devs are bringing it to the desktop also. The process is not yet complete however with Qt5 (lets hope), QtQuick will be, de jure, used to write Qt GUI.
I don't have specific expertise in QtQuick, though I was evaluating it for our app last year. It's come on a long way since then and in particular it's much easier to embed QtQuick widgets within a native app or native widgets within a QtQuick app. Whether it's worth adopting will depend on the requirements of your app -- if it's a very GUI-rich app with clean encapsulations to the underlying logic then it may be worthwhile. If the UI is closely coupled to the program logic then maybe a native app is better, perhaps using QtQuick components for the more dynamic parts of the interface.
I would suggest building a simple prototype to see if it does meet your requirements before making the final decision either way.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With