On Aug 30, 2011, at 8:44 AM, ext Attila Csipa wrote: > > The mantra I hear is 'check for features', and in that vein you have > mobility's QSysInfo for hardware (i.e. check for keyboard), and for software > you could do something like
> > > And it starts with a QWidgets UI to maintain compatibility with Qt4.6, then > switches to declarative if it is run on Qt4.7 and finally to a components > based > UI. That's not so easy. Let's take three MeeGo alternatives. MeeGo 1.2 Harmattan Handset with swipe UI, MeeGo 1.2 Handset UI and MeeGo tablet UI. All these have components based UI but different UX As example, in Harmattan you have toolbar on bottom and you don't need display home and close buttons. In 1.2 Handset you have toolbar on top and need to have these buttons. Handset also has MeeGoUX components but their UX is different and confusing compared to device Native UX MeeGo Tablet has MeeGoUX components and MeeGoTouch UX. There is also question, is there system level iPhone-style home button or does application need to display it. Then comes question of different screen sizes. You can get screen size and resolution from latest QtMobility and your UI layout should be different in 10" and 3.8" display. So, least the basic requirement is to detect is device - Harmattan - 1.2 Handset - Tablet - Screen Size and resolution Kate > > Best regards, > Attila Csipa > _______________________________________________ > MeeGo-dev mailing list > MeeGo-dev@meego.com > http://lists.meego.com/listinfo/meego-dev > http://wiki.meego.com/Mailing_list_guidelines _______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
