Important: Please read the Qt Code of Conduct -

Hello QT

  • Hello,
    I am new to qt development and am just starting out and will be using it to build apps for meego as well as maemo systems
    I would like to ask for help as I am lost in the big world of qt and dont know where to start my journey as I am utterly confused between various things!!!and i am frightened now.
    It would be very kind of u all if u can help me figure out on what is what
    Thanks in advance.

  • Did you bother to check the forum at all? There are plenty of books, video tutorials, plus Qt comes with a ton of examples and extensive, easy to use documentation...

  • Yea,I checked it.I just wanted to know what is qt quick and what is simple qt?are they both same or different.and what is qml in all these

  • I would suggest clicking on the tag "qml vs widget" on the right of your screen.
    It will show some other threads about the same question you have.

  • With Qt alone you develop using imperative C++ and you produce fast native code. With Qt Quick you use QML, which is a JavaScript like declarative language, used directly in combination with JavaScript itself, in slower interpreted code. You can naturally mix both, create custom QML elements in C++, which is a good way to avoid the overhead of extensive use of JavaScript for logic.

    Advantages of C++:
    Native code
    Outstanding performance
    Good memory efficiency
    A wide range of ready to use components

    Disadvantages of C++:
    Harder and more complex than QML
    Slower development
    Not really optimized for touch

    Advantages of QML:
    Rapid development
    Simple syntax
    Optimized for animation and eye candy
    Same look across different platforms (Qt Gui in comparison uses platform native styling by default)
    Optimized for touch

    Disadvantages of QML:
    Slower performance due to interpreted code (avoidable by keeping JS code to bare minimum, but still requires using C++ under the hood)
    Limited number of stock components (with time this gets better, there are already some GUI components for QML)
    Uses more memory

    It all depends on what you are planning to do, C++ is the right tool for some scenarios, QML is the right tool for other, a combination of both is a win/win situation.

  • Oh cool,thanks for the explaination!!!
    I think i would better use only basic qt to make gui apps instead of qml as i am not familiar with javascript.I hope I am not losing in doing this way?

  • I happen to prefer C++ myself, it is the more powerful and efficient option albeit slower to develop in, the only downside is, at least to me it no longer seems to be a priority in the Qt development cycle. Judging from the last Qt Developer Days QML gets like 80% of the attention and my one apprehension is eventually the C++ framework will lag behind, hopefully thou it will never come to it.

    My problem with the C++ API is the GUI part uses native styling by default, which forces me to use very little of the stock components, instead subclassing the deeper abstract base classes, overloading events and so I get a GUI that looks and \behaves a bit more modern and identical across different platforms, working adequately with multi-touch and so on. If the Qt development team decides to step up and do the same to the stock GUI components this will certainly breathe more life into the C++ API, but for now, sadly, it is Qt Quick that has the priority.

    JavaScript is not that hard BTW, and you can easily get away with only using it for property binding and some minimal logic, while still keeping heavy duty logic in C++.

Log in to reply