> ----- Original message ----- > From: "[email protected]" <[email protected]> > To: "Kevron Rees" <[email protected]> > cc: [email protected] > Subject: Re: [MeeGo-dev] Should I use MeeGo Touch Framework or Qt Framework > for MeeGo tablets > Date: Thu, 3 Mar 2011 00:08:31 +0200 > > >>> > 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. > >> > >> I have been already thinking of duicontrolpanel2 (maybe we can name it > >> now properly mxxxx). > > > > If you are thinking of creating a settings/control panel application, > > there is already one in the Tablet UX (that I understand will be open > > sourced in a 'couple weeks'). It supports loading 'applets' similarly > > to how duicontrolpanel did. > > > > That said, there's always need for individual settings applets that do > > various things ;). > > Sure there is, but I was just thinking of adding one more layer and separating > the UI. > <snip> > > With Qt Components being the UI abstraction, this would not come even > with any significant > complication, quite in contrary for the applet developers. I have not > yet finalize the idea, but > I have been just prototyping with the Qt components + C++ to get idea > how the api could work. > I agree Karoliina-- this makes the most sense for flexibility and maintainability. Should be the default approach IMO. Basically applet code ---> wrapper ---> control panel (or any other host, actually, including the desktop) Heck, Microsoft managed this with the Windows control panel, so... ; ) Randy -------------------------------------------------------------- Ovi Mail: Making email access easy http://mail.ovi.com _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
