Adding meego-architecture to the Cc list... Regarding the use of contextkit in MeeGo, someone should define what properties the "OS" publishes through contextkit (if any). This set of properties would then become the set that all MeeGo instances would need to support. Depending on other MeeGo architectural issues, the providers for these OS properties could be generic (i.e. part of the OS) or part of HW adaptation.
Regards, Jari From: [email protected] [mailto:[email protected]] On Behalf Of ext Jia-Chi Lai Sent: 28. tammikuuta 2011 04:51 To: Kevron Rees Cc: [email protected] Subject: Re: [MeeGo-dev] contextkit of battery, media,cellular... > > hi~~ > > remember that you mention in this letter: > http://lists.meego.com/pipermail/meego-dev/2010-September/006305.html > you said : contextkit-maemo is for maemo. contextkit-meego is for > meego. > > If contextkit-maemo not work in meego, the provider of bluetooth > contextkit will implement as an new plugin? or in bluetooth package?? > > Or the contextkit-maemo will work in meego?? if yes, when the > contextkit-maemo will work in meego?? > Right, like I said in that message, "most" of the maemo ones aren't useful to meego. I think the bluetooth context provider may be the only one we use from the project. The "Session" and "Profile" plugin of contextkit-maemo will used in meego?? > > I could find the contextkit of Cellular in contextkit-meego , but the > Cellular contextkit are not work now, The message is shown: > Cellular.SignalStrength =>"CellularProvider First subscriber > appeared, connecting to ofono" > Cellular.RegistrationStatus=>"CellularProvider First > subscriber appeared, connecting to ofono" > Cellular.CellName=>"key not provided" > Cellular.Technology=>"key not provided" > Cellular.NetworkName=>"key not provided" > Looks like the Cellular provider isn't providing all the properties. >From the code: #define SignalStrength "Cellular.SignalStrength" #define DataTechnology "Cellular.DataTechnology" #define RegistrationStatus "Cellular.RegistrationStatus" It shouldn't be too difficult to add these other properties. Patches accepted if you have the time. > And Battery.ChargeBars is a necessary key for systemmui to develope > statusindicator. > Does contextkit would provide the key provider implement?? > >From my understanding of system-ui, it may have relied on the charge percentage in the past. It appears now it uses ChargeBars so we will need to update the Battery provider as well. -Kevron thanks, there is also a contextkit "System.PowerSaveMode" is use by system-ui for statusindicator. This contextkit would be implement a provider in meego or how to provide the information for system-ui ?? Thanks.
_______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
