Nemo/Porting

= Introduction =

This guide attempts to document the ideal situation for porting Nemo to new hardware targets.

= Architecture =

Generally speaking, like Mer and Nemo in general, we need a layered approach to portability.


 * At the bottom, we need hardware dependent daemon(s) which read data for that specific hardware target.
 * This daemon then exposes this information to MW via contextkit properties
 * The mw monitors/consumes these contextkit properties as required

= Properties = http://maemo.gitorious.org/maemo-af/contextkit/blobs/master/spec/core.context

Interesting properties that should be provided by a hardware adaptation daemon:


 * Screen.TopEdge (device orientation)
 * Screen.IsCovered
 * Screen.Blanked (TODO: is this "screen is turned off"?)


 * Position.Stable
 * Position.Shaky
 * Position.IsFlat


 * Battery.ChargePercentage
 * Battery.ChargeBars
 * Battery.OnBattery
 * Battery.LowBattery
 * Battery.IsCharging
 * Battery.TimeUntilLow
 * Battery.TimeUntilFull


 * Environment.IsDark
 * Environment.IsBright

= Implementation plan =

On the hardware side:


 * Nokia devices first, as they're an easy target, and most things already work.
 * A good idea would be to look into mce/dsme, and turning them into our Nokia "adaptation daemons".
 * ExoPC is probably a good target next
 * upower for charger info
 * orientation info is available somewhere in Qt Mobility afaik, but currently nonfunctional
 * Accelerometer data may be trickier, at least in Lenovo S10-3t that doesn't work
 * Brightness sensor is present, and somehow already controls screen brightness (and never turns it up...)

On the middleware side:


 * Neuter qmsystem/Mobility into talking to our contextkit properties only

= TODO =

Things yet to cover.


 * Can contextkit provide subscription notifications, so e.g. we can turn expensive sensors off? (assuming we have any...) - fairly sure it can
 * Connman portability: modem drivers, properties, etc?
 * Bluetooth info: does it belong to our hardware abstraction?
 * Screen lock: how does that factor into things? mce tells sysuid (soon lipstick) to turn lock on, but should it?