On Monday 22 February 2010 08:49:28 Quim Gil wrote: > fwiw I just answered at > http://lists.meego.com/pipermail/meego-community/2010-February/000014.html
Just to hear a few thoughts on this snippet: >The aim is to have only one official API based on Qt and Web Runtime. >Developers following that API should get their apps working in all kinds >of MeeGo compatible devices. You might want to do some UI tweaks across >UX references but the functionality should be in place. > >The UX references don't bring API differences per se. They offer >different system UI implementations focused on the specific types of >devices they are addressing. Where does this leave the Maemo 6 UI framework/DUI ? Is it considered as part of 'UI tweaks', or is it the reference MeeGo handheld UI we're talking about ? A more clear relation-mapping of UI terms between MeeGo and Maemo would be helpful. Also, not talking just about UI, the relation between QtMobility as available on Maemo and the Middleware in the MeeGo architecture is also something I would appreciate more information on. Regards, Attila _______________________________________________ maemo-community mailing list maemo-community@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-community