Hi, Excerpts from Arjan van de Ven's message of Tue Sep 21 17:20:34 +0300 2010: > On 9/21/2010 6:42 AM, Kasi Viswanath wrote: > > Hi, > > > > First, apologies if it is the not the right place for this question. I > > tried to put this question in the meego forums today but for some > > reason it didn't allow me to log-in even. Said access denied. > > > > My question was does MeeGo (specially for Handset) allow different > > modes of operation? > > > > There could be times when the user might only need essential features > > like Phone, SMS, Contacts and Alarm. This could be probably to save > > battery when he is on a budget. > > The idea here is to have a smart-phone (regular/default) mode and a > > basic-phone mode (only Phone, SMS, Contacts, Alarm and any other > > necessary/dependent processes). > > > > When the user opts for the basic-phone mode, the device should be > > running only modules/processes related to Phone, SMS, Contacts, Alarm, > > Cell Radio, Battery, Desktop, etc. If a process is not needed to run > > for any of the basic-mode specified features, that process should > > clearly not run at all. > > This probably (hoping) would result in battery saving and also faster > > response times for the specified features in that mode. > > how is this different from the user just not starting any apps ? > the user already has the ability to not starting any apps and get this > behavior...
Well, not quite. As per: http://apidocs.meego.com/mtf/prestart.html - MTF applications at least can be prestarted, meaning they'll be running in the background with no UI present, without user intervention. (Whether or not this is used in MeeGo at present I have no idea.) I do think it's probably added usability/UI complexity for little gain, though - with no UI to draw, there really is very little chance of misbehaviour I'd think. -- Robin Burchell http://rburchell.com _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
