(Sorry about posting at meego-dev - it appears almost nobody is on-topic on this mailing list, so one more won't hurt).
2010/12/28 Benoît HERVIER <[email protected]>: > Currently it s look like a new technology, require to reconstruct many > things, isn't ready, and many push for using it. It s look like we are > doing the same errors again. The amount of confidence put in Qt Quick is in a totally different ballpark from other UI technologies we've had around recently. QWidgets were not good enough for anybody, Orbit was not good enough for MeeGo, MTF was not good enough for Symbian. To say nothing about Avkon and Gtk+, that is ;-). Qt Quick is the first technology to have the whole Nokia machine behind it, for the long haul. Even if you feel some initial objection to the technology, it may be a good idea to give it a second chance - perhaps after we get a good amount of high quality training material published in a centralized way (for one reason or another, the good stuff has been Nokia internal for now). Tackling the QML learning curve is rewarded by power and quickly doing something you thought to be "not worth the trouble" before. > no respect of the plateform look and feel, etc ...). I ll probably > look for an other plateform/framework (do not me ask which one, as i > ll answer that Qt (QWidget) + Python is perfect (for my use.) ). I'm afraid there is not much choice, unless you consider Objective C or Dalvik as preferable to QML + [Python|C++] ;-) -- Ville M. Vainio @@ Forum Nokia _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
