kdeconnect-kde/plugins/notifications
Holger Kaelberer 2a74eb68f8 notifications: add initial support for desktop-to-xxx notifications
Eavesdrop on the Notify call of the org.freedesktop.Notifications
dbus-interface, proxy all caught notifications to our peer device and
track them in the internal notifications-list.

Also fix "cancel" requests from peer devices, by cutting of
kdeconnect-android's id-prefix.
2015-12-05 23:23:22 +01:00
..
CMakeLists.txt notifications: add initial support for desktop-to-xxx notifications 2015-12-05 23:23:22 +01:00
kdeconnect_notifications.json SVN_SILENT made messages (.desktop file) - always resolve ours 2015-11-17 12:54:36 +00:00
notification.cpp Use id instead of a pointer in the dismissRequested signal and slot. 2015-10-17 15:32:13 -07:00
notification.h Use id instead of a pointer in the dismissRequested signal and slot. 2015-10-17 15:32:13 -07:00
notification_debug.h Fix various krazy2 warnings 2015-08-21 22:38:54 +06:00
notificationsdbusinterface.cpp notifications: add initial support for desktop-to-xxx notifications 2015-12-05 23:23:22 +01:00
notificationsdbusinterface.h notifications: add initial support for desktop-to-xxx notifications 2015-12-05 23:23:22 +01:00
notificationslistener.cpp notifications: add initial support for desktop-to-xxx notifications 2015-12-05 23:23:22 +01:00
notificationslistener.h notifications: add initial support for desktop-to-xxx notifications 2015-12-05 23:23:22 +01:00
notificationsplugin.cpp notifications: add initial support for desktop-to-xxx notifications 2015-12-05 23:23:22 +01:00
notificationsplugin.h notifications: add initial support for desktop-to-xxx notifications 2015-12-05 23:23:22 +01:00
README Move the plugins into a different top-ĺevel directory 2014-06-14 16:34:11 +02:00

This plugin listens to packages with type "kdeconnect.notification" that will
contain all the information of the other device notifications.

The other device will report us every notification that is created or dismissed,
so we can keep in sync a local list of notifications.

At the beginning we can request the already existing notifications by sending a
package with the boolean "request" set to true.

The received packages will contain the following fields:

"id" (string): A unique notification id.
"appName" (string): The app that generated the notification
"ticker" (string): The title or headline of the notification.
"isClearable" (boolean): True if we can request to dismiss the notification.
"isCancel" (boolean): True if the notification was dismissed in the peer device.
"requestAnswer" (boolean): True if this is an answer to a "request" package.

Additionally the package can contain a payload with the icon of the notification
in PNG format.

The content of these fields is used to display the notifications to the user.
Note that if we receive a second notification with the same "id", we should
update the existent notification instead of creating a new one.

If the user dismisses a notification from this device, we have to request the
other device to remove it. This is done by sending a package with the fields
"id" set to the id of the notification we want to dismiss and a boolean "cancel"
set to true. The other device will answer with a notification package with
"isCancel" set to true when it is dismissed.