On May 3, 2011, at 1:40 AM, ext Robin Burchell wrote: Hi Mikael,
On 02/05/11 23:37, Mikael Hermansson wrote: Den måndagen den 2:e maj 2011 skrev<[email protected]<mailto:[email protected]>>: ..... cut... Then you may ask that why there is different components for handset and tablet. One reason is that they are made by different companies ( Nokia / Intel ) and also that UX differs. I hope that in future we can get API's of all of them compatible. Intresting you say that, cause I guess there is many people like me who wonder what happened to the open development of qt-components for Meego Handset? See: http://labs.qt.nokia.com/2011/01/31/well-be-right-back/ It is very unfortunate that this closed development lasted much longer than initially expected. >From what I can gather of this, these "MeeGo" components are really for >Harmattan, so I don't know what real-world use they're going to be in a MeeGo >context, given that (as you note) MeeGo have written their own set. Yes, they are in Harmattan. Does they have "real-world use" just depends that do you like offer optimum user experience for certain class of devices. Intel components offers best match with Intel's tablet UX, Harmattan components offer best user experience for handset. I think that we should see our application development wider context than just MeeGo . Using Qt Quick components you can cover not only MeeGo tablets but also MeeGo handsets including Harmattan, non MeeGo handsets and normal common desktop Linux. If you would concentrate only for MeeGo tablets, it's your choice but least you have now freedom easilly cover other classes of devices and other user experiences easily. If you would like to make application for non touch screen devices, you should consider desktop Qt Quick components http://labs.qt.nokia.com/2011/03/10/qml-components-for-desktop/ Kate
_______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
