Hi, On Sun, Jul 4, 2010 at 10:40 PM, Nicola De Filippo <[email protected]> wrote: > Hi, > i have a question: why to create touch framework (other class, other widget) > when exist QML?
Not that I can give you a decisive answer, but two possible answers, and things to keep in mind: - QML didn't exist (or wasn't mature) at the time. It will first be released in 4.7, which still hasn't actually been released. - QML currently does not have a standardised widget set, meaning that if you want to do applications following a coherent style, you will have issues. This looks like it is being addressed in qt-components (http://gitorious.org/qt-components), but that will of course take more time. Not that I disagree that things could have perhaps been approached a little more coherently, as I (and a number of others) voiced concerns about at the time of the Harmattan UI toolkit release - the following thread contains some of that discussion: http://talk.maemo.org/showthread.php?t=34686 I do hope that the picture clears up a bit more than is the case so far, though. Having four separate ways to do UI, three of which are new (mtouch/QML/Orbit/Qt) is a bit of a trainwreck on the approach for application developers, and does not provide a consistent, clear path. For myself, and my own projects, I'll be sticking with plain Qt until the dust settles and there is a clear winner, if for no other reason than the Qt SDK makes this path a lot easier to follow. ;) > N. -- Robin Burchell http://rburchell.com _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
