View Single Post
Posts: 356 | Thanked: 231 times | Joined on Oct 2007
#152
Originally Posted by Mark Wilcox View Post
My question now is, if the MeeGo UI framework is not the thing to use what is - really just QML? Where's the standard chrome (battery and signal etc) going to come from? Are there some QML components for that on the way. What will define the standard platform look and feel?

Just curious...
As far as I understand there will be QML, Qt Quick and Qt Mobile.

Also there will be no standard look and feel heavily enforced on developers. Look here:

http://labs.qt.nokia.com/2010/10/19/...shop-and-gimp/

Graphic designers can make any design and just export it to QML. On one hand this is usability problem but on the other massive incentive to all designers, corporations and institutions which prefer to make their own designs and not to bow to some external idea how things should like.

Not sure how guts of this system will be implemented but it offers easy way for corporate identity not only on telecom level but even on all small company phones it will be *cheap* way to create its own look&feel.

Also - not sure if such "forking" of efforts was essentially bad thing. Without trial&error you wouldn't know if things are good or bad. You have to go some distance with each path to know where you should eventually commit yourself. In Nokia and Qt case it was dramatically visible due to open source method of development.

Supposedly Apple was working on iPhone several years before it was released - do you think they were working from the day one on only one and true version? I don't think so.