On Sun, 28 Nov 2010 12:36:53 +0000 <[email protected]> wrote: > Hi, > > Is there a "umbrella" FEA or bug for this?
Maybe not directly, but a quick search on BMC reveals: Feature 6597 - [FEA] Promote meegotouch-prestartd 0.20.0 to Trunk:Testing http://bugs.meego.com/show_bug.cgi?id=6597 And... Bug 7074 - Incoming call can not be answered if dialer not open when call is received http://bugs.meego.com/show_bug.cgi?id=7074 Regards, Shane... > > Jukka > > >-----Original Message----- > >From: [email protected] [mailto:meego-handset- > >[email protected]] On Behalf Of ext Shane Bryan > >Sent: 24 November, 2010 21:34 > >To: Carsten Munk > >Cc: [email protected] > >Subject: Re: [Meego-handset] Booster/meegotouch-applauncherd usage in > >Handset UX > > > >On Wed, 24 Nov 2010 10:31:46 +0100 > >Carsten Munk <[email protected]> wrote: > > > >> Hi, > >> > >> One of the reasons we use so much RAM and have problems with app > >> starting time in Handset UX is the fact we're not using > >> meegotouch-applauncherd in duihome/reference applications/etc. > >> > >> Is there a timeline for when we start to have support for this in > >> the Handset UX? > > > >Timeline, no, not to my knowledge. > > > >Intention, yes... > > > >Sadly, applifed was introduced late into the 1.1 release cycle and > >retrofitting the apps fell below the bar since it was invasive to the > >apps and not part of the feature requirements being tested by QA. > > > >I played with it in a branch of the dialer quite a while back (when > >it was still DUI) and due to missing applifed and plain old > >ignorance (on my part) due to limited and conflicting docs at the > >time, I abandoned that work. > > > >I would like to get to in for 1.2, but the load of new features is > >putting pressure on this again :( > > > >Also, I can only speak for dialer, I do not know or manage the > >schedules or features for other handset apps. _______________________________________________ MeeGo-handset mailing list [email protected] http://lists.meego.com/listinfo/meego-handset
