________________________________ >From: [email protected] [[email protected]] on behalf of >ext Ville M. Vainio [[email protected]] >Sent: Tuesday, December 28, 2010 3:23 PM >To: Rohit Baravkar; meego-dev >Subject: Re: [MeeGo-dev] What are the advantages of developing QT apps without >libmeegotouch over MTF enabled application? >
>Disadvantage with both QWidgets (which is what I assume you mean by Qt w/o >meegotouch) and mtf is that neither is an officially supported solution, i.e. >you are on your own if you use them. If something >works today (e.g. >gestures), somebody may decide to break it tomorrow without prior warning. > >Go for Qt Quick if you've got a choice. Very big disadvantage to do QWidget application is that you can't get full MeeGo handset user experience, you don't have sliding stacked windows, portrait orientation / orientation switching support, animations etc and you can't do them at all with QWidgets ( without doing everything with proxywidget ). With Qt Quick you have all enablers for full MeeGo UX and in Qt Quick Components you have all UX components ready made. Kate -- Sent from my Nokia N900 ----- Original message ----- > What are the advantages of developing QT apps without libmeegotouch over > MTF (Meego touch framework) enabled application.? > > If we need to implement gestures for any given use case, will a > application based on libmeegotouch be more smoother than QT app without > libmeegotouch? > > Any touch testing results benchmark done on Meego? > > > -Rohit
_______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
