On Tuesday 30 August 2011 10:27:52 you wrote: > > 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
I think this is a separate issue - we were just talking about detecting and using the proper UX tech. The difference *between* the particular UX-es (and corresponding UX guidelines) is a different story. To draw a parallel - if your application comes with both a Qt and a GTK UI, the right way to launch the proper front-end would be to check for KDE/Gnome and Qt/GTK availability, not whether the application was run on Ubuntu, Kubuntu, XUbuntu, etc, or, worse yet, if it was an eeePC or ExoPC or... you get the idea On a side note: QtInfo *does* go to extreme lengths to be able to run on anything that has Qt 4.6 (maybe even Qt 4.5) all the way to a components based UI *with the same package/binaries*. 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
