kdeconnect-kde/plugins/notifications
l10n daemon script cda092d2bb SVN_SILENT made messages (.desktop file) - always resolve ours
In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"
2015-03-31 13:16:15 +00:00
..
CMakeLists.txt Remove KNotifications dependency from libkdeconnectcore 2015-03-24 12:26:37 +01:00
kdeconnect_notifications.json SVN_SILENT made messages (.desktop file) - always resolve ours 2015-03-31 13:16:15 +00:00
notification.cpp Merge branch 'master' into frameworks 2015-01-20 22:44:31 -08:00
notification.h Move the plugins into a different top-ĺevel directory 2014-06-14 16:34:11 +02:00
notification_debug.h Port Notifications from kDebug to qCDebug 2014-09-22 00:45:06 +02:00
notificationsdbusinterface.cpp Merge branch 'master' into frameworks 2015-01-20 22:57:10 -08:00
notificationsdbusinterface.h Fixed notifications not being appearing in the model nor in the plasmoid 2014-07-01 01:26:07 +02:00
notificationsplugin.cpp Port away from KServiceTrader 2015-03-19 16:36:53 +01:00
notificationsplugin.h Move the plugins into a different top-ĺevel directory 2014-06-14 16:34:11 +02: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.