kdeconnect-kde/plugins/notifications/CMakeLists.txt

set(debug_file_SRCS)
ecm_qt_declare_logging_category(
    debug_file_SRCS HEADER plugin_notification_debug.h
    IDENTIFIER KDECONNECT_PLUGIN_NOTIFICATION CATEGORY_NAME kdeconnect.plugin.notification
    DEFAULT_SEVERITY Warning
    EXPORT kdeconnect-kde DESCRIPTION "kdeconnect (plugin notification)")

set(kdeconnect_notifications_SRCS
    notification.cpp
    notificationsplugin.cpp
    sendreplydialog.cpp
    ${debug_file_SRCS}
)

ki18n_wrap_ui(kdeconnect_notifications_SRCS sendreplydialog.ui)

kdeconnect_add_plugin(kdeconnect_notifications SOURCES ${kdeconnect_notifications_SRCS})

target_link_libraries(kdeconnect_notifications
    kdeconnectcore
    Qt5::DBus
    KF5::Notifications
    KF5::I18n
    KF5::WindowSystem
)

if (UNIX AND NOT APPLE)
    target_link_libraries(kdeconnect_notifications
        Qt::X11Extras
    )
endif()
Use ecm_qt_declare_logging_category to declare the logging categories This automatizes the generation of logging categories so a kdeconnect-kde.categories is generated and installed to /usr/share/qlogging-categories5/ so kdebugsettings can use it. Also, sets the default logging level to Warning. So now the logs of users won't be filled with debug messages but they can modify the configuration easily with kdebugsettings. 2020-05-26 17:55:47 +01:00			`set(debug_file_SRCS)`
			`ecm_qt_declare_logging_category(`
			`debug_file_SRCS HEADER plugin_notification_debug.h`
			`IDENTIFIER KDECONNECT_PLUGIN_NOTIFICATION CATEGORY_NAME kdeconnect.plugin.notification`
			`DEFAULT_SEVERITY Warning`
			`EXPORT kdeconnect-kde DESCRIPTION "kdeconnect (plugin notification)")`

Added stubs for futurible plugins 2013-08-13 23:09:46 +01:00			`set(kdeconnect_notifications_SRCS`
Implemented notifications plugin It exports a dbus interface to manipulate notifications 2013-08-20 12:53:36 +01:00			`notification.cpp`
Added stubs for futurible plugins 2013-08-13 23:09:46 +01:00			`notificationsplugin.cpp`
These changes allow replying to any notifications that offer quick reply text fields Summary: These changes allow replying to any notifications that offer quick reply text fields Reviewers: #kde_connect, apol Reviewed By: #kde_connect, apol Subscribers: apol Maniphest Tasks: T4674 Differential Revision: https://phabricator.kde.org/D5993 2017-05-31 14:33:21 +01:00			`sendreplydialog.cpp`
Use ecm_qt_declare_logging_category to declare the logging categories This automatizes the generation of logging categories so a kdeconnect-kde.categories is generated and installed to /usr/share/qlogging-categories5/ so kdebugsettings can use it. Also, sets the default logging level to Warning. So now the logs of users won't be filled with debug messages but they can modify the configuration easily with kdebugsettings. 2020-05-26 17:55:47 +01:00			`${debug_file_SRCS}`
Added stubs for futurible plugins 2013-08-13 23:09:46 +01:00			`)`

Improvements on the SendReplyDialog Use a designer file for it Make sure the focus is on the reply widget Disable focus from the original text raise() the dialog when we show it to make sure it's over the other windows 2017-08-03 16:23:12 +01:00			`ki18n_wrap_ui(kdeconnect_notifications_SRCS sendreplydialog.ui)`

Clean up unneeded JSON parameter in kcoreaddons_add_plugin The moc process already rebuilds the plugin when the JSON file changes, consequently the additional parameter is not needed. Task: https://phabricator.kde.org/T14649 2021-06-28 19:33:52 +01:00			`kdeconnect_add_plugin(kdeconnect_notifications SOURCES ${kdeconnect_notifications_SRCS})`
Added stubs for futurible plugins 2013-08-13 23:09:46 +01:00
Port notifications away from KDELibs4Support 2014-09-22 09:17:44 +01:00			`target_link_libraries(kdeconnect_notifications`
			`kdeconnectcore`
			`Qt5::DBus`
			`KF5::Notifications`
notifications: allow to configure how to sync desktop notifications Added kcm ui with global and app-specific config options. Global options affect all notifications: - Persistent only? --> Sync only notifications with timeout == 0? - Include body? --> Add body string to summary when syncing? - Minimum urgency Per-application options affect notifications sent by a specific application: - Sync it at all? - If yes, allow to define a "blacklist" pattern (QRegularExpression) to define which notifications should not be synced. Applications are maintained in the per-device config and added when seen the first time by the notification listener. From that moment on they can be configured in the kcm ui. 2015-12-05 22:11:57 +00:00			`KF5::I18n`
Fix notification reply window activation and focus Ensures the reply window is raised using Qt::WindowActive state. This properly raises the window reliably (including from plasmoid, which didn't work at all before) and focuses the reply textbox. 2021-02-01 13:10:47 +00:00			`KF5::WindowSystem`
Port notifications away from KDELibs4Support 2014-09-22 09:17:44 +01:00			`)`
Fix notification reply window activation and focus Ensures the reply window is raised using Qt::WindowActive state. This properly raises the window reliably (including from plasmoid, which didn't work at all before) and focuses the reply textbox. 2021-02-01 13:10:47 +00:00
			`if (UNIX AND NOT APPLE)`
			`target_link_libraries(kdeconnect_notifications`
			`Qt::X11Extras`
			`)`
			`endif()`