On Tue, 05 Nov 2013 09:48:15 +0200, Denis Zalevskiy wrote: > On 11/04/2013 07:58 PM, Javier wrote: >> I am trying to figure out if there any alternatives to monitor >> notifications from an application in Nemo/SailfishOS. My goal is to >> port my MetaWatch app over to SailfishOS, or even do something more >> standard such as implementing the Bluetooth 'Alert Notification >> Profile' or Apple's equivalent ('Apple Notification Center Service') >> which allow forwarding of notifications to watches and other companion >> devices. >> >> So far, I've considered a few options:
> Also statefs can be used for this purpose, the easiest way is to create > inout configuration file, so lipstick can just update an input file and > all clients polling output file are be notified. > > * configuration file example: > https://github.com/nemomobile/statefs/blob/master/examples/config/inout- example.conf > * currently existing inout "providers" used for emulation of the system > state provided by standard nemomobile providers: > https://github.com/nemomobile/statefs-providers/tree/master/inout > * nemo version of timed is using it to publish Alarm.* properties I've been reading statefs examples and it seems it may be hard to expose a collection of objects (aka the notifications). Virtually the only way I can think of is having a single property -- "notifications" -- which contains a number of strings with some adhoc text based format. E.g. <pending notification 1 title> <description> <alarm|calendar|other program> \n <notification #2 title> <description> <..> \n And this does not look too clean. As for the problem of actually capturing the notifications without changing lipstick, I suspect that monitoring D-Bus will be the least-bad option for now. Will see how the lipstick split develops. Javier.