On Fri, Mar 6, 2015 at 1:13 AM, Olivier CHURLAUD <oliv...@churlaud.com> wrote: > Hi, > > I saw that one of the great feature of Qt was QtQuick, and that KDE chose to > use this a lot. I went lately from fully written widgets to QtDesigner.... > > What are the real advantages of QtQuick over the old fashion Qt (I don't > know how to call it)? Are there drawbacks? (The real question is Why should > I write my app with QtQuick instead of old fashion Qt?)
From my point of view, a reason to use QtQuick over QtWidgets is that you can essentially do more things. QtWidgets is designed to integrate properly on desktop environments, that wasn't even part of the plan in QtQuick not so long ago (also not the case anymore). So I wouldn't go for QtWidgets if you want it to be touch-friendly, if you want any animations or if you want to think about how information will be presented specifically. On the other hand, there's a set of use-cases that QtWidgets covers very well, then it's fine to use it just as well. > > Another question is: are there resources (on KDE or somewhere else) to > see/learn the power of QtQuick? Be cause when I read this for instance This pops to mind, I haven't read it personally. I usually use the official Qt documentation. http://qmlbook.github.io/ > https://techbase.kde.org/Development/Tutorials/Plasma4/QML/GettingStarted it > doesnt seems to be well designed for handling contents comming from a > database (or very dynamic content) The way to integrate these big chunks of contents is through models. Keep in mind that the views in QtQuick and QtQuick Controls are very different than those in QtWidgets, so the ways you'd approach the problems are slightly different. HTH, Aleix >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
