On 12/28/2010 9:21 PM, Ville M. Vainio wrote:
2010/12/28 Till Harbaum / Lists<[email protected]>:

Am Dienstag 28 Dezember 2010 schrieb Ville M. Vainio:
QWidgets were not good enough for anybody
You are talking about these QWidgets that several tutorials on the meego 
conference were about?

Are you really wondering why developers are confused and loosing confidence in 
all this? Do you really wonder why so many people are hesitant to actually 
start doing things because they are expecting you to change your mind again, 
soon?
6 months ago, any sane developer would be confused because the UI
technology roadmap for third party developers was confidential.
Backend stuff like Qt Mobility was openly communicated, but UI
technology was not.

Right now, though, everything should be crystal clear: it's all about
Qt Quick, and the usual Qt C++ technologies on the back end. There are
no secret deprecation/obsolescence plans on the UI layer that have not
been openly communicated. Even the QSceneGraph stuff (something Nokia
could have as well kept as secret research project) is out there on
public blogs.

If someone is *still* confused, do let us know and we can make it more
explicit in the future.

I thought it was more than clear , it s written in the first page of Meego sdk1.1.... the sample located here http://meego.gitorious.org/meegotouch/libmeegotouch/trees/master/examples + the power of qt graphical view enable all possibilities and allow to implements superb custom widget depending your need. i was looking for an easy way to do it six month ago by using the qml scripting but get stuck with binding the model properly.In the end i am back to c++ as it is more easy for me and allow to use by a more readable manner the code. It enable to use proper UI design pattern without having to put reference of the model in the view witch is wrong from my point of view."Cocoa" design pattern(MVP as well ) are good also and fit QT quite well...



Best regards,
david

what else ?
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev

Reply via email to