>________________________________________ >From: [email protected] [[email protected]] on behalf of >ext Thiago >Macieira [[email protected]] >Sent: Wednesday, March 02, 2011 4:14 PM >To: [email protected] >Subject: Re: [MeeGo-dev] Should I use MeeGo Touch Framework or Qt Framework >for MeeGo tablets > >On Wednesday, 2 de March de 2011 06:52:34 Gabriel M. Beddingfield wrote: >> However, the MTF includes things like mcompositor, >> mdecorator, duicontrolpanel, etc... These are fundamental >> parts of the Handset UX, the IVI UX, and the Tablet UX. So, >> if the MTF is scheduled for termination... then I missed a >> memo somewhere. > >You're right: before it can be terminated, an alternative needs to come along.
Let's make difference, duicontrolpanel is just an application that is made with MtF UI toolkit ads is many other MeeGo application. Before MtF UI toolkit can be removed, all of them need to be rewritten with Qt Components. MtF and Qt Components can work side by side. Compositor is just compositor. MtF and Qt Components applications work as well even with N900 Clutter based compositor. >My guess (and it's a guess!) is that we'll see these things move away when >Wayland moves in. My Guess is that MtF is no longer needed for application programming when we get even Qt Components alpha out. There will be MtF UI toolkit applications so long that it takes re-write all of them with Qt Components. It is completely other question rewrite outside of application frameworks like compositor and system UI. Kate _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
