[MeeGo-touch-dev] One question about MTF and Qt Quick

[Caluori, Vince]

Hi Jonni, Ville, and touch-dev,

I have a similar question regarding MTF and QT/QT quick.  Will QT adopt
any of the cool application lifecycle

stuff that MTF provides?  Or maybe QT quick already has similar
features.  If so, can you tell me what those are?

Specifically, I'm wondering about things like:

-          SetPrestartMode(and other prestart related apis)

-          Lazy shutdown concepts in MTF

-          MWindow items like "SwitcherEntered" and "SwitcherExited"

-          Boostable apps

-          "Applifed" for prestarting core apps at boot time

 

Will these (or do they already) exist in QT / QT quick?  Any thoughts
and recommendations are highly appreciated.

 

Thanks, Vince

 

 

 

From: meego-touch-dev-bounces at meego.com
[mailto:meego-touch-dev-bounces at meego.com] On Behalf Of
Jonni.Rainisto at nokia.com
Sent: Tuesday, November 30, 2010 4:05 AM
To: apolloxue at gmail.com; meego-touch-dev at meego.com
Subject: Re: [MeeGo-touch-dev] One question about MTF and Qt Quick

 

 

My five cents is that you should use Qt Quick for the reasons that you
mentioned already - future compatibility.

 

Regards, Jonni

 

From: meego-touch-dev-bounces at meego.com
[mailto:meego-touch-dev-bounces at meego.com] On Behalf Of ext Apollo Xue
Sent: 30 November, 2010 12:38
To: meego-touch-dev at meego.com
Subject: [MeeGo-touch-dev] One question about MTF and Qt Quick

 

Hi All,
    I am a new developer working on MeeGo handset platform, but I am
struggling about which UI framework I should use, MTF or Qt Qiuck? Could
you please give me some advice?
 
    From my point of view, MTF provides convenient functionality to
build good touch UX for phone applications, some extra efforts are need
to achieve the same result if using Qt Quick, Qt Quick maybe is the
glorious way, but at this time point, it cannot provide what the MTF can
provide.
    But in the API doc of MeeGo 1.1, we are notified that the platform
API including MTF are not recommended for general use and not guaranteed
for future compatibility.
    MTF looks good for MeeGo handset development, but now I have some
concern since it is not recommended.
    Then here come my questions:
    1. What is the future of MTF? Will it be deprecated or merged back
to Qt?
    2. If we use MTF for MeeGo handset development, what is the risk? 
 
 
Best Regards 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.meego.com/pipermail/meego-touch-dev/attachments/20101130/d3aa8239/attachment.html>