kdeconnect-kde/plugins/notifications
Nicolas Fella 74e7a90cd8 Simplify notification handling
Summary:
Use QPointer for KNotification
Use ready signal for signalling updates

BUG: 400010

Test Plan: Spawned some notifications

Reviewers: #kde_connect, broulik, albertvaka

Reviewed By: #kde_connect, albertvaka

Subscribers: albertvaka, kdeconnect

Tags: #kde_connect

Differential Revision: https://phabricator.kde.org/D18354
2019-01-24 09:19:14 +01:00
..
CMakeLists.txt Clean-up requirements: cmake 3.0, qt 5.7, use min versions, deduplicate KF5 2018-03-17 23:34:33 +01:00
kdeconnect_notifications.json SVN_SILENT made messages (.desktop file) - always resolve ours 2019-01-09 05:31:18 +01:00
notification.cpp Simplify notification handling 2019-01-24 09:19:14 +01:00
notification.h Simplify notification handling 2019-01-24 09:19:14 +01:00
notification_debug.h Fix various krazy2 warnings 2015-08-21 22:38:54 +06:00
notificationsdbusinterface.cpp Simplify notification handling 2019-01-24 09:19:14 +01:00
notificationsdbusinterface.h Fix minor typos 2018-12-11 19:23:06 +02:00
notificationsplugin.cpp Rename NetworkPackage -> NetworkPacket 2018-03-05 20:03:23 +01:00
notificationsplugin.h Add a method for creating simple notifications 2018-03-18 12:52:22 +01:00
README Improve notificationsplugin README 2018-06-30 23:05:38 +02:00
sendreplydialog.cpp Merge branch 'master' into 1.x 2017-09-03 22:05:54 +02:00
sendreplydialog.h Merge branch 'master' into 1.x 2017-09-03 22:05:54 +02:00
sendreplydialog.ui Improvements on the SendReplyDialog 2017-08-03 17:26:29 +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, for compatibility with older Android versions.
"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.
"title" (string): The title of the notification.
"text" (string): The text/content of the notification.
"requestReplyId" (string): Used to reply to messages.
"silent" (bool): Handle this notification silent, i.e. don't show a notification, but show it in the plasmoid.

Additionally the package can contain a payload with the icon of the notification
in PNG format. If there another field will be present:

"payloadHash" (string): MD5 hash of the payload. Used as a filename to store the payload.

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", the existing notification is updated.

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.