kdeconnect-kde

History

Alexander Lohnau 2e67f95017 Add explicit moc includes to cpp files The rationale is explained in https://planet.kde.org/friedrich-kossebau-2023-06-28-include-also-moc-files-of-headers/ In case of KDEConnect, it impressively speeds up compilation. Before it took 390 seconds on a clean build and with this change it took 330 seconds. This is due to the mocs_compilation having to include the header files and thus all their headers. Due to the lots of small plugins we have, this means that the same headers must be compiled plenty of times. When we include the moc files directly in the C++ file, they are already available.		2023-07-30 07:27:45 +00:00
..
CMakeLists.txt	Use target-centric CMake approach for declaring debug category	2023-07-22 20:51:19 +00:00
kdeconnect_notifications.json	SVN_SILENT made messages (.desktop file) - always resolve ours	2023-07-30 01:37:54 +00:00
notification.cpp	Add explicit moc includes to cpp files	2023-07-30 07:27:45 +00:00
notification.h	Use pragma once in plugins	2023-07-22 20:51:19 +00:00
notificationsplugin.cpp	Add explicit moc includes to cpp files	2023-07-30 07:27:45 +00:00
notificationsplugin.h	Use pragma once in plugins	2023-07-22 20:51:19 +00:00
README	Update readme	2023-03-31 21:00:48 +02:00
sendreplydialog.cpp	Add explicit moc includes to cpp files	2023-07-30 07:27:45 +00:00
sendreplydialog.h	Use pragma once in plugins	2023-07-22 20:51:19 +00:00
sendreplydialog.ui	[sendreplydialog] Move focus on tab	2021-09-26 17:27:42 +00:00

README

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.
"title" (string): The title of the notification.
"text" (string): The text/content of the notification.
"requestReplyId" (string): Used to reply to messages.
"silent" (bool): Don't show a notification popup for this notification.

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.