From 3778e468b0a62976f3a85c95ca348405acbe3c36 Mon Sep 17 00:00:00 2001 From: Alf Gaida Date: Wed, 4 Nov 2015 00:57:59 +0100 Subject: [PATCH] Cherry-picking upstream version 0.10.0. Set minimum version for liblxqt and libqtxdg --- .gitignore | 1 + COPYING => LICENSE | 41 +- README.md | 11 + .../translations/lxqt-config-notificationd.ts | 6 +- .../lxqt-config-notificationd_de.ts | 6 +- .../lxqt-config-notificationd_el.ts | 6 +- .../lxqt-config-notificationd_hr.ts | 77 ++- .../lxqt-config-notificationd_hu.ts | 39 +- .../lxqt-config-notificationd_it.ts | 86 ++- .../lxqt-config-notificationd_pt.ts | 88 ++- .../lxqt-config-notificationd_ru.ts | 39 +- .../lxqt-config-notificationd_ru_RU.ts | 39 +- debian/changelog | 7 + debian/control | 2 +- docs/notification-spec-latest.html | 538 ------------------ src/translations/lxqt-notificationd.ts | 4 +- src/translations/lxqt-notificationd_de.ts | 2 + src/translations/lxqt-notificationd_el.ts | 2 + src/translations/lxqt-notificationd_hu.ts | 2 + src/translations/lxqt-notificationd_pt.ts | 4 +- src/translations/lxqt-notificationd_ru.ts | 2 +- src/translations/lxqt-notificationd_ru_RU.ts | 2 +- 22 files changed, 331 insertions(+), 673 deletions(-) create mode 100644 .gitignore rename COPYING => LICENSE (96%) create mode 100644 README.md delete mode 100644 docs/notification-spec-latest.html diff --git a/.gitignore b/.gitignore new file mode 100644 index 0000000..378eac2 --- /dev/null +++ b/.gitignore @@ -0,0 +1 @@ +build diff --git a/COPYING b/LICENSE similarity index 96% rename from COPYING rename to LICENSE index a8dd823..20fb9c7 100644 --- a/COPYING +++ b/LICENSE @@ -1,9 +1,8 @@ - GNU LESSER GENERAL PUBLIC LICENSE Version 2.1, February 1999 Copyright (C) 1991, 1999 Free Software Foundation, Inc. - 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA + 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. @@ -23,8 +22,7 @@ specially designated software packages--typically libraries--of the Free Software Foundation and other authors who decide to use it. You can use it too, but we suggest you first think carefully about whether this license or the ordinary General Public License is the better -strategy to use in any particular case, based on the explanations -below. +strategy to use in any particular case, based on the explanations below. When we speak of free software, we are referring to freedom of use, not price. Our General Public Licenses are designed to make sure that @@ -89,9 +87,9 @@ libraries. However, the Lesser license provides advantages in certain special circumstances. For example, on rare occasions, there may be a special need to -encourage the widest possible use of a certain library, so that it -becomes a de-facto standard. To achieve this, non-free programs must -be allowed to use the library. A more frequent case is that a free +encourage the widest possible use of a certain library, so that it becomes +a de-facto standard. To achieve this, non-free programs must be +allowed to use the library. A more frequent case is that a free library does the same job as widely used non-free libraries. In this case, there is little to gain by limiting the free library to free software only, so we use the Lesser General Public License. @@ -138,8 +136,8 @@ included without limitation in the term "modification".) "Source code" for a work means the preferred form of the work for making modifications to it. For a library, complete source code means all the source code for all modules it contains, plus any associated -interface definition files, plus the scripts used to control -compilation and installation of the library. +interface definition files, plus the scripts used to control compilation +and installation of the library. Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of @@ -305,10 +303,10 @@ of these things: the user installs one, as long as the modified version is interface-compatible with the version that the work was made with. - c) Accompany the work with a written offer, valid for at least - three years, to give the same user the materials specified in - Subsection 6a, above, for a charge no more than the cost of - performing this distribution. + c) Accompany the work with a written offer, valid for at + least three years, to give the same user the materials + specified in Subsection 6a, above, for a charge no more + than the cost of performing this distribution. d) If distribution of the work is made by offering access to copy from a designated place, offer equivalent access to copy the above @@ -386,10 +384,9 @@ all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Library. -If any portion of this section is held invalid or unenforceable under -any particular circumstance, the balance of the section is intended to -apply, and the section as a whole is intended to apply in other -circumstances. +If any portion of this section is held invalid or unenforceable under any +particular circumstance, the balance of the section is intended to apply, +and the section as a whole is intended to apply in other circumstances. It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any @@ -407,11 +404,11 @@ be a consequence of the rest of this License. 12. If the distribution and/or use of the Library is restricted in certain countries either by patents or by copyrighted interfaces, the -original copyright holder who places the Library under this License -may add an explicit geographical distribution limitation excluding those -countries, so that distribution is permitted only in or among -countries not thus excluded. In such case, this License incorporates -the limitation as if written in the body of this License. +original copyright holder who places the Library under this License may add +an explicit geographical distribution limitation excluding those countries, +so that distribution is permitted only in or among countries not thus +excluded. In such case, this License incorporates the limitation as if +written in the body of this License. 13. The Free Software Foundation may publish revised and/or new versions of the Lesser General Public License from time to time. diff --git a/README.md b/README.md new file mode 100644 index 0000000..ddcd8a6 --- /dev/null +++ b/README.md @@ -0,0 +1,11 @@ +# lxqt-notificationd + +The LXQt Notification daemon + +## Spec + +lxqt-notificationd follows the Desktop Notifications Specification version 1.2. + +It can be found here: + +* https://people.gnome.org/~mccann/docs/notification-spec/notification-spec-latest.html diff --git a/config/translations/lxqt-config-notificationd.ts b/config/translations/lxqt-config-notificationd.ts index 7639f62..b8a565d 100644 --- a/config/translations/lxqt-config-notificationd.ts +++ b/config/translations/lxqt-config-notificationd.ts @@ -30,17 +30,17 @@ - + Some notifications set their own on-screen duration. - + Default duration: - + sec diff --git a/config/translations/lxqt-config-notificationd_de.ts b/config/translations/lxqt-config-notificationd_de.ts index 9cc4b18..bf2007b 100644 --- a/config/translations/lxqt-config-notificationd_de.ts +++ b/config/translations/lxqt-config-notificationd_de.ts @@ -30,17 +30,17 @@ Dauer - + Some notifications set their own on-screen duration. Einige Benachrichtigungen setzen ihre eigene Anzeigedauer. - + Default duration: Standarddauer: - + sec s diff --git a/config/translations/lxqt-config-notificationd_el.ts b/config/translations/lxqt-config-notificationd_el.ts index ca82527..ee52b23 100644 --- a/config/translations/lxqt-config-notificationd_el.ts +++ b/config/translations/lxqt-config-notificationd_el.ts @@ -30,17 +30,17 @@ Διάρκεια - + Some notifications set their own on-screen duration. Μερικές ειδοποιήσεις καθορίζουν τη δική τους διάρκεια εμφάνισης. - + Default duration: Διάρκεια εξ ορισμού: - + sec δευτ diff --git a/config/translations/lxqt-config-notificationd_hr.ts b/config/translations/lxqt-config-notificationd_hr.ts index b0eec30..3ea72b9 100644 --- a/config/translations/lxqt-config-notificationd_hr.ts +++ b/config/translations/lxqt-config-notificationd_hr.ts @@ -1,105 +1,148 @@ - + AdvancedSettings Menu Configuration - Konfiguracija izbornika + Konfiguracija izbornika Notification Duration - Trajanje obavijesti + Trajanje obavijesti For some the notification's expiration time is dependent on the notification server's settings. - Za neke obavijesti's vrijeme istjecanja ovisi o postavkama poslužitelja's obavijesti + Za neke obavijesti's vrijeme istjecanja ovisi o postavkama poslužitelja's obavijesti - "Server Decides" Time: + + Width: + + Spacing: + + + + + Duration + + + + + Some notifications set their own on-screen duration. + + + + + Default duration: + + + + sec sek + Sizes Veličine Notification Spacing: - Razmak obavijesti + Razmak obavijesti + + px px Notification Width: - Širina obavijesti + Širina obavijesti BasicSettings + Basic Settings Osnovne postavke + + + Position on screen + + Display Notifications - Prikaži obavijesti + Prikaži obavijesti Top/Left - Gore/lijevo + Gore/lijevo Top/Right - Gore/desno + Gore/desno Bottom/Left - Dolje/lijevo + Dolje/lijevo Bottom/Right - Dolje/desno + Dolje/desno Test Notification - Isprobaj obavijesti + Isprobaj obavijesti + <b>Warning:</b> No notifications daemon is running. A fallback will be used. + <b>Warning:</b> A third-party notifications daemon (%1) is running. -These settings won't have an effect on it! +These settings won't have any effect on it! - Notification Summary - Sažetak obavijesti + + Notification demo + - Notification Body + + This is a test notification. + All notifications will now appear here on LXQt. + + Notification Summary + Sažetak obavijesti + MainWindow + Desktop Notifications Obavijesti radne površine + Basic Settings Osnovne postavke + Advanced Settings Napredne postavke diff --git a/config/translations/lxqt-config-notificationd_hu.ts b/config/translations/lxqt-config-notificationd_hu.ts index 933817b..353401b 100644 --- a/config/translations/lxqt-config-notificationd_hu.ts +++ b/config/translations/lxqt-config-notificationd_hu.ts @@ -30,17 +30,17 @@ Tartam - + Some notifications set their own on-screen duration. Egyes értesítések megjelenési ideje - + Default duration: Alapértelmezett tartam: - + sec mp @@ -58,49 +58,54 @@ Hely - Top/Left - Balra fenn + Balra fenn - Top/Right - Jobbra fenn + Jobbra fenn - Bottom/Left - Balra lenn + Balra lenn - Bottom/Right - Jobbra lenn + Jobbra lenn - + <b>Warning:</b> No notifications daemon is running. A fallback will be used. <b>Figyelem:</b> Értesítő démon nem fut. A vésztartalék használatos. - + <b>Warning:</b> A third-party notifications daemon (%1) is running. These settings won't have any effect on it! <b>Figyelem:</b> A (%1) démont már valaki futtatja. Ezek a beállítások arra már hatástalanok! - + + Notification demo + + + + + This is a test notification. + All notifications will now appear here on LXQt. + + + Notification demo - Értesítési bemutató + Értesítési bemutató - This is a test notification. All notifications will now appear here on LXQt. - Az értesítés tesztje + Az értesítés tesztje Minden értesítést megjelenít az LXQt. diff --git a/config/translations/lxqt-config-notificationd_it.ts b/config/translations/lxqt-config-notificationd_it.ts index 40c4b68..98f87b8 100644 --- a/config/translations/lxqt-config-notificationd_it.ts +++ b/config/translations/lxqt-config-notificationd_it.ts @@ -5,104 +5,160 @@ AdvancedSettings Menu Configuration - Configurazione del menu + Configurazione del menu Notification Duration - Durata delle notifiche + Durata delle notifiche For some the notification's expiration time is dependent on the notification server's settings. - Per alcune notifiche il tempo dipende dalle impostazioni del server delle notifiche. + Per alcune notifiche il tempo dipende dalle impostazioni del server delle notifiche. "Server Decides" Time: - Tempo di decisioni del server: + Tempo di decisioni del server: + + Width: + + + + + Spacing: + + + + + Duration + + + + + Some notifications set their own on-screen duration. + + + + + Default duration: + + + + sec sec + Sizes Dimensione Notification Spacing: a cosa si riferisce?? - Spazing: + Spazing: + + px Notification Width: - Larghezza: + Larghezza: BasicSettings + Basic Settings Impostazioni base + + + Position on screen + + Display Notifications - Mostra notifiche + Mostra notifiche Top/Left - Alto a sinistra + Alto a sinistra Top/Right - Alto a destra + Alto a destra Bottom/Left - Fondo a sinistra + Fondo a sinistra Bottom/Right - Fondo a destra + Fondo a destra Test Notification - Notifica di prova + Notifica di prova + <b>Warning:</b> No notifications daemon is running. A fallback will be used. <b>Attenzione:</b> Nessun demone di notifiche è in esecuzione. Sarà usato un sistema di riserva. + + + <b>Warning:</b> A third-party notifications daemon (%1) is running. +These settings won't have any effect on it! + + + + + Notification demo + + + + + This is a test notification. + All notifications will now appear here on LXQt. + + <b>Warning:</b> A third-party notifications daemon (%1) is running. These settings won't have an effect on it! - <b>Attenzione:</b> Un altro demone di notifiche (%1) è in esecuzione. + <b>Attenzione:</b> Un altro demone di notifiche (%1) è in esecuzione. Queste impostazioni non avranno effetto su quello! Notification Summary - Sommario della notifica + Sommario della notifica Notification Body - Corpo della notifica + Corpo della notifica MainWindow + Desktop Notifications Notificazioni Desktop + Basic Settings Impostazioni base + Advanced Settings Impostazioni avanzate diff --git a/config/translations/lxqt-config-notificationd_pt.ts b/config/translations/lxqt-config-notificationd_pt.ts index a685818..2a0530d 100644 --- a/config/translations/lxqt-config-notificationd_pt.ts +++ b/config/translations/lxqt-config-notificationd_pt.ts @@ -1,107 +1,163 @@ - + AdvancedSettings Menu Configuration - Configuração do menu + Configuração do menu Notification Duration - Duração da notificação + Duração da notificação For some the notification's expiration time is dependent on the notification server's settings. - Para algumas notificações, o tempo limite depende das definições das notificações do servidor. + Para algumas notificações, o tempo limite depende das definições das notificações do servidor. "Server Decides" Time: - Tempo para "Decisão do servidor": + Tempo para "Decisão do servidor": + + Width: + + + + + Spacing: + + + + + Duration + + + + + Some notifications set their own on-screen duration. + + + + + Default duration: + + + + sec seg + Sizes Tamanhos Notification Spacing: - Espaçamento da notificação: + Espaçamento da notificação: + + px px Notification Width: - Largura da notificaçao: + Largura da notificaçao: BasicSettings + Basic Settings Definições básicas + + + Position on screen + + Display Notifications - Mostrar notificações + Mostrar notificações Top/Left - Cima/Esquerda + Cima/Esquerda Top/Right - Cima/Direita + Cima/Direita Bottom/Left - Baixo/Esquerda + Baixo/Esquerda Bottom/Right - Baixo/Direita + Baixo/Direita Test Notification - Testar notificação + Testar notificação + <b>Warning:</b> No notifications daemon is running. A fallback will be used. <b>Aviso:</b> o serviço de notificaçoes não está em execução. Será utilizada uma solução alternativa. + + + <b>Warning:</b> A third-party notifications daemon (%1) is running. +These settings won't have any effect on it! + + + + + Notification demo + + + + + This is a test notification. + All notifications will now appear here on LXQt. + + <b>Warning:</b> A third-party notifications daemon (%1) is running. These settings won't have an effect on it! - <b>Aviso:</b> já está a ser executado um serviço de notificações (%1). + <b>Aviso:</b> já está a ser executado um serviço de notificações (%1). Estas definições não produzirão qualquer efeito! Notification Summary - Resumo da notificação + Resumo da notificação Notification Body - Corpo da notificação + Corpo da notificação MainWindow + Desktop Notifications Notificações do ambiente de trabalho + Basic Settings Definições básicas + Advanced Settings Definições avançadas diff --git a/config/translations/lxqt-config-notificationd_ru.ts b/config/translations/lxqt-config-notificationd_ru.ts index 022a2ca..1a7aca2 100644 --- a/config/translations/lxqt-config-notificationd_ru.ts +++ b/config/translations/lxqt-config-notificationd_ru.ts @@ -30,17 +30,17 @@ Длительность - + Some notifications set their own on-screen duration. Некоторые уведомления сами устанавливают свою длительность на экране. - + Default duration: Длительность по умолчанию: - + sec сек @@ -58,49 +58,54 @@ Расположение на экране - Top/Left - Вверху слева + Вверху слева - Top/Right - Вверху справа + Вверху справа - Bottom/Left - Внизу слева + Внизу слева - Bottom/Right - Внизу справа + Внизу справа - + <b>Warning:</b> No notifications daemon is running. A fallback will be used. <b>Внимание:</b> Демон уведомлений не запущен. Будет использован резервный вариант. - + <b>Warning:</b> A third-party notifications daemon (%1) is running. These settings won't have any effect on it! <b>Внимание:</b> Демон уведомлений третьей сторон (%1) запущен. Эти настройки не будут иметь никакого эффекта для него! - + + Notification demo + + + + + This is a test notification. + All notifications will now appear here on LXQt. + + + Notification demo - Демонстрация уведомления + Демонстрация уведомления - This is a test notification. All notifications will now appear here on LXQt. - Это тестовое уведомление. + Это тестовое уведомление. Все уведомления на LXQt будут появляться здесь. diff --git a/config/translations/lxqt-config-notificationd_ru_RU.ts b/config/translations/lxqt-config-notificationd_ru_RU.ts index 7e05fb6..cf9e127 100644 --- a/config/translations/lxqt-config-notificationd_ru_RU.ts +++ b/config/translations/lxqt-config-notificationd_ru_RU.ts @@ -30,17 +30,17 @@ Длительность - + Some notifications set their own on-screen duration. Некоторые уведомления сами устанавливают свою длительность на экране. - + Default duration: Длительность по умолчанию: - + sec сек @@ -58,49 +58,54 @@ Расположение на экране - Top/Left - Вверху слева + Вверху слева - Top/Right - Вверху справа + Вверху справа - Bottom/Left - Внизу слева + Внизу слева - Bottom/Right - Внизу справа + Внизу справа - + <b>Warning:</b> No notifications daemon is running. A fallback will be used. <b>Внимание:</b> Демон уведомлений не запущен. Будет использован резервный вариант. - + <b>Warning:</b> A third-party notifications daemon (%1) is running. These settings won't have any effect on it! <b>Внимание:</b> Демон уведомлений третьей сторон (%1) запущен. Эти настройки не будут иметь никакого эффекта для него! - + + Notification demo + + + + + This is a test notification. + All notifications will now appear here on LXQt. + + + Notification demo - Демонстрация уведомления + Демонстрация уведомления - This is a test notification. All notifications will now appear here on LXQt. - Это тестовое уведомление. + Это тестовое уведомление. Все уведомления на LXQt будут появляться здесь. diff --git a/debian/changelog b/debian/changelog index a4eb59b..3a3a12a 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +lxqt-notificationd (0.10.0-1) unstable; urgency=medium + + * Cherry-picking upstream version 0.10.0. + * Set minimum versions for libqtxdg and liblxqt + + -- Alf Gaida Tue, 03 Nov 2015 01:57:30 +0100 + lxqt-notificationd (0.9.0+20151028-2) experimental; urgency=medium * set minimum versions for libqtxdg and liblxqt diff --git a/debian/control b/debian/control index f5861fe..34fd233 100644 --- a/debian/control +++ b/debian/control @@ -8,7 +8,7 @@ Priority: optional Build-Depends: cmake (>= 3.0.2), debhelper (>= 9), libkf5windowsystem-dev, - liblxqt0-dev (>= 0.9.0+20151026), + liblxqt0-dev (>= 0.10.0), libqt5x11extras5-dev, libqt5xdg-dev (>= 1.3.0), libx11-dev, diff --git a/docs/notification-spec-latest.html b/docs/notification-spec-latest.html deleted file mode 100644 index 23073f9..0000000 --- a/docs/notification-spec-latest.html +++ /dev/null @@ -1,538 +0,0 @@ - - -Desktop Notifications Specification

Desktop Notifications Specification

Mike Hearn


-      
-     

Christian Hammond


-      
-     

William Jon McCann


-      
-     

Version 1.2

Table of Contents

Introduction
Basic Design
Backwards Compatibility
Markup
Hyperlinks
Images
Icons and Images
Priorities
Formats
Categories
Urgency Levels
Hints
D-BUS Protocol
Message commands
Signals

Introduction

- This is a draft standard for a desktop notifications service, - through which applications can generate passive popups to notify - the user in an asynchronous manner of events. -

- This specification explicitly does not include other types of - notification presentation such as modal message boxes, window manager - decorations or window list annotations. -

- Example use cases include: -

  • Messages from chat programs

  • Scheduled alarm

  • Completed file transfer

  • New mail notification

  • Low disk space/battery warnings

Basic Design

- In order to ensure that multiple notifications can easily be - displayed at once, and to provide a convenient implementation, all - notifications are controlled by a single session-scoped service which - exposes a D-BUS interface. -

- On startup, a conforming implementation should take the - org.freedesktop.Notifications service on - the session bus. This service will be referred to as the "notification - server" or just "the server" in this document. It can optionally be - activated automatically by the bus process, however this is not required - and notification server clients must not assume that it is available. -

- The server should implement the - org.freedesktop.Notifications interface on - an object with the path "/org/freedesktop/Notifications". - This is the only interface required by this version of the specification. -

- A notification has the following components: -

Table 1. Notification Components

ComponentDescription
Application Name - This is the optional name of the application sending the notification. - This should be the application's formal name, rather than some sort - of ID. An example would be "FredApp E-Mail Client," rather than - "fredapp-email-client." -
Replaces ID - An optional ID of an existing notification that this - notification is intended to replace. -
Notification Icon - The notification icon. See Icons and Images Formats. -
Summary - This is a single line overview of the notification. For instance, - "You have mail" or "A friend has come online". It should generally - not be longer than 40 characters, though this is not a requirement, - and server implementations should word wrap if necessary. The summary - must be encoded using UTF-8. -
Body -

- This is a multi-line body of text. Each line is a paragraph, server - implementations are free to word wrap them as they see fit. -

-

- The body may contain simple markup as specified in - Markup. It must be encoded using UTF-8. -

-

- If the body is omitted, just the summary is displayed. -

-
Actions -

- The actions send a request message back to the notification client - when invoked. This functionality may not be implemented by the - notification server, conforming clients should check if it is available - before using it (see the GetCapabilities message in - Protocol). An implementation is free to ignore any - requested by the client. As an example one possible rendering of - actions would be as buttons in the notification popup. -

-

- Actions are sent over as a list of pairs. Each even element in the - list (starting at index 0) represents the identifier for the action. - Each odd element in the list is the localized string that will be - displayed to the user. -

-

- The default action (usually invoked my clicking the notification) - should have a key named "default". The name can - be anything, though implementations are free not to display it. -

-
Hints -

- Hints are a way to provide extra data to a notification server that - the server may be able to make use of. -

-

See Hints for a list of available hints.

-
Expiration Timeout -

- The timeout time in milliseconds since the display of the notification - at which the notification should automatically close. -

-

- If -1, the notification's expiration time is dependent on the - notification server's settings, and may vary for the type of - notification. -

-

- If 0, the notification never expires. -

-

- Each notification displayed is allocated a unique ID by the server. - This is unique within the session. While the notification server is - running, the ID will not be recycled unless the capacity of a uint32 is - exceeded. -

- This can be used to hide the notification before the expiration timeout - is reached. It can also be used to atomically replace the notification - with another. This allows you to (for instance) modify the contents of - a notification while it's on-screen. -

Backwards Compatibility

- Clients should try and avoid making assumptions about the presentation and - abilities of the notification server. The message content is the most - important thing. -

- Clients can check with the server what capabilities are supported - using the GetCapabilities message. See - Protocol. -

- If a client requires a response from a passive popup, it should be - coded such that a non-focus-stealing message box can be used in the - case that the notification server does not support this feature. -

Markup

- Body text may contain markup. The markup is XML-based, and consists - of a small subset of HTML along with a few additional tags. -

- The following tags should be supported by the notification server. - Though it is optional, it is recommended. Notification servers that do - not support these tags should filter them out. -

- <b> ... - </b> - Bold
- <i> ... - </i> - Italic
- <u> ... - </u> - Underline
- <a href="..."> ... - </a> - Hyperlink
- <img src="..." alt="..."/> - Image

- A full-blown HTML implementation is not required of this spec, and - notifications should never take advantage of tags that are not listed - above. As notifications are not a substitute for web browsers or complex - dialogs, advanced layout is not necessary, and may in fact limit the - number of systems that notification services can run on, due to memory - usage and screen space. Such examples are PDAs, certain cell phones, and - slow PCs or laptops with little memory. -

- For the same reason, a full XML or XHTML implementation using XSLT or - CSS stylesheets is not part of this specification. Information that - must be presented in a more complex form should use an application-specific - dialog, a web browser, or some other display mechanism. -

- The tags specified above mark up the content in a way that allows them - to be stripped out on some implementations without impacting the actual - content. -

Hyperlinks

- Hyperlinks allow for linking one or more words to a URI. There is no - requirement to allow for images to be linked, and it is highly suggested - that implementations do not allow this, as there is no clean-looking, - standard visual indicator for a hyperlinked image. -

- Hyperlinked text should appear in the standard blue underline format. -

- Hyperlinks cannot function as a replacement for actions. They are - used to link to local directories or remote sites using standard URI - schemes. -

- Implementations are not required to support hyperlinks. -

Images

- Images may be placed in the notification, but this should be done with - caution. The image should never exceed 200x100, but this should be thought - of as a maximum size. Images should always have alternative text - provided through the alt="..." attribute. -

- Image data cannot be embedded in the message itself. Images referenced - must always be local files. -

- Implementations are not required to support images. -

Icons and Images

- A notification can optionally have an associated icon and/or image. -

- The icon is defined by the "app_icon" parameter. - The image can be defined by the "image-path", the "image-data" hint or the - deprecated "icon_data" hint. -

Priorities

- An implementation which only displays one image or icon must choose which one - to display using the following order: -

  1. "image-data"

  2. "image-path"

  3. app_icon parameter

  4. for compatibility reason, "icon_data"

-

- An implementation which can display both the image and icon must show the - icon from the "app_icon" parameter and choose which image to display using - the following order: -

  1. "image-data"

  2. "image-path"

  3. for compatibility reason, "icon_data"

-

Formats

- The "image-data" and "icon_data" hints should be a raw image data structure - of signature (iiibiiay) which describes the width, height, rowstride, has - alpha, bits per sample, channels and image data respectively. -

- The "app_icon" parameter and "image-path" hint should be either an URI - (file:// is the only URI schema supported right now) or a name in a - freedesktop.org-compliant icon theme (not a GTK+ stock ID). -

Categories

- Notifications can optionally have a type indicator. Although neither - client or nor server must support this, some may choose to. Those servers - implementing categories may use them to intelligently display - the notification in a certain way, or group notifications of similar - types. -

- Categories are in - class.specific form. - class specifies the generic type of notification, and - specific specifies the more specific type of - notification. -

- If a specific type of notification does not exist for your notification, - but the generic kind does, a notification of type - class is acceptable. -

- Third parties, when defining their own categories, should discuss - the possibility of standardizing on the hint with other parties, preferably - in a place such as the - xdg - mailing list at - freedesktop.org. If it - warrants a standard, it will be added to the table above. If no - consensus is reached, the category should be in the form of - "x-vendor.class.name." -

- The following table lists standard notifications as defined by this spec. - More will be added in time. -

Table 2. Categories

TypeDescription
"device" - A generic device-related notification that doesn't fit into - any other category. -
"device.added"A device, such as a USB device, was added to the system.
"device.error"A device had some kind of error.
"device.removed" - A device, such as a USB device, was removed from the system. -
"email" - A generic e-mail-related notification that doesn't fit into any - other category. -
"email.arrived"A new e-mail notification.
"email.bounced"A notification stating that an e-mail has bounced.
"im" - A generic instant message-related notification that doesn't fit - into any other category. -
"im.error"An instant message error notification.
"im.received"A received instant message notification.
"network" - A generic network notification that doesn't fit into any other - category. -
"network.connected" - A network connection notification, such as successful sign-on to a - network service. This should not be confused with - device.added for new network devices. -
"network.disconnected" - A network disconnected notification. This should not be confused with - device.removed for disconnected network devices. -
"network.error" - A network-related or connection-related error. -
"presence" - A generic presence change notification that doesn't fit into - any other category, such as going away or idle. -
"presence.offline"An offline presence change notification.
"presence.online"An online presence change notification.
"transfer" - A generic file transfer or download notification that doesn't fit - into any other category. -
"transfer.complete"A file transfer or download complete notification.
"transfer.error"A file transfer or download error.

Urgency Levels

- Notifications have an urgency level associated with them. This defines - the importance of the notification. For example, "Joe Bob signed on" - would be a low urgency. "You have new mail" or "A USB device was unplugged" - would be a normal urgency. "Your computer is on fire" would be a critical - urgency. -

Urgency levels are defined as follows:

Table 3. Urgency Levels

TypeDescription
0Low
1Normal
2Critical

- Developers must use their own judgement when deciding the urgency of a - notification. Typically, if the majority of programs are using the same - level for a specific type of urgency, other applications should follow - them. -

- For low and normal urgencies, server implementations may display the - notifications how they choose. They should, however, have a sane - expiration timeout dependent on the urgency level. -

- Critical notifications should not automatically expire, as they are - things that the user will most likely want to know about. They should - only be closed when the user dismisses them, for example, by clicking on - the notification. -

Hints

- Hints are a way to provide extra data to a notification server that - the server may be able to make use of. -

- Neither clients nor notification servers are required to support any - hints. Both sides should assume that hints are not passed, and should - ignore any hints they do not understand. -

- Third parties, when defining their own hints, should discuss the - possibility of standardizing on the hint with other parties, preferably - in a place such as the - xdg - mailing list at - freedesktop.org. If it - warrants a standard, it will be added to the table above. If no - consensus is reached, the hint name should be in the form of - "x-vendor-name." -

- The value type for the hint dictionary in D-BUS is of the - DBUS_TYPE_VARIANT container type. This allows different - data types (string, integer, boolean, etc.) to be used for hints. When - adding a dictionary of hints, this type must be used, rather than putting - the actual hint value in as the dictionary value. -

- The following table lists the standard hints as defined by this - specification. Future hints may be proposed and added to this list - over time. Once again, implementations are not required to support these. -

Table 4. Standard Hints

NameValue TypeDescriptionSpec Version
"action-icons"boolean - When set, a server that has the "action-icons" capability will - attempt to interpret any action identifier as a named icon. - The localized display name will be used to annotate the icon - for accessibility purposes. The icon name should be compliant - with the Freedesktop.org Icon Naming Specification. - >= 1.2
"category"string - The type of notification this is. -  
"desktop-entry"string - This specifies the name of the desktop filename representing the - calling program. This should be the same as the prefix used for the - application's .desktop file. An example would be "rhythmbox" from - "rhythmbox.desktop". This can be used by the daemon to retrieve the - correct icon for the application, for logging purposes, etc. -  
"image-data"(iiibiiay) - This is a raw data image format which describes the width, height, - rowstride, has alpha, bits per sample, channels and image data - respectively. - >= 1.2
"image_data"(iiibiiay) - Deprecated. Use image-data instead. - = 1.1
"image-path"string - Alternative way to define the notification image. See Icons and Images. - >= 1.2
"image_path"string - Deprecated. Use image-path instead. - = 1.1
"icon_data"(iiibiiay) - Deprecated. Use image-data instead. - < 1.1
"resident"boolean - When set the server will not automatically remove the - notification when an action has been invoked. The notification - will remain resident in the server until it is explicitly - removed by the user or by the sender. This hint is likely only - useful when the server has the "persistence" capability. - >= 1.2
"sound-file"string - The path to a sound file to play when the notification pops up. -  
"sound-name"string - A themeable named sound from the freedesktop.org - sound naming specification - to play when the notification pops up. Similar to icon-name, only for - sounds. An example would be "message-new-instant". -  
"suppress-sound"boolean - Causes the server to suppress playing any sounds, if it has that - ability. This is usually set when the client itself is going to - play its own sound. -  
"transient"boolean - When set the server will treat the notification as transient - and by-pass the server's persistence capability, if it should - exist. - >= 1.2
"x"int - Specifies the X location on the screen that the notification should - point to. The "y" hint must also be specified. -  
"y"int - Specifies the Y location on the screen that the notification should - point to. The "x" hint must also be specified. -  
"urgency"byte - The urgency level. -  

D-BUS Protocol

- The following messages must be supported by all - implementations. -

Message commands

org.freedesktop.Notifications.GetCapabilities

STRING_ARRAY - org.freedesktop.Notifications.GetCapabilities - (); 
 

- This message takes no parameters. -

- It returns an array of strings. Each string describes an optional - capability implemented by the server. The following values are - defined by this spec: -

Table 5. Server Capabilities

"action-icons" - Supports using icons instead of text for displaying actions. - Using icons for actions must be enabled on a per-notification - basis using the "action-icons" hint. -
"actions" - The server will provide the specified actions to the user. Even if - this cap is missing, actions may still be specified by the client, - however the server is free to ignore them. -
"body" - Supports body text. Some implementations may only show the - summary (for instance, onscreen displays, marquee/scrollers) -
"body-hyperlinks" - The server supports hyperlinks in the notifications. -
"body-images" - The server supports images in the notifications. -
"body-markup" - Supports markup in the body text. If marked up text is sent - to a server that does not give this cap, the markup will show - through as regular text so must be stripped clientside. -
"icon-multi" - The server will render an animation of all the frames in a given - image array. The client may still specify multiple frames even if - this cap and/or "icon-static" is missing, however - the server is free to ignore them and use only the primary frame. -
"icon-static" - Supports display of exactly 1 frame of any given image array. - This value is mutually exclusive with - "icon-multi", it is a protocol error for the - server to specify both. -
"persistence" - The server supports persistence of notifications. - Notifications will be retained until they are acknowledged or - removed by the user or recalled by the sender. The presence - of this capability allows clients to depend on the server to - ensure a notification is seen and eliminate the need for - the client to display a reminding function (such as a status - icon) of its own. -
"sound" - The server supports sounds on notifications. If returned, the - server must support the "sound-file" and - "suppress-sound" hints. -

- New vendor-specific caps may be specified as long as they start with - "x-vendor". For instance, - "x-gnome-foo-cap". Capability names must not - contain spaces. They are limited to alpha-numeric characters and dashes - ("-"). -

org.freedesktop.Notifications.Notify

UINT32 - org.freedesktop.Notifications.Notify - (app_name,  
 replaces_id,  
 app_icon,  
 summary,  
 body,  
 actions,  
 hints,  
 expire_timeout); 
STRING app_name;
UINT32 replaces_id;
STRING app_icon;
STRING summary;
STRING body;
ARRAY actions;
DICT hints;
INT32 expire_timeout;
 

- Sends a notification to the notification server. -

Table 6. Notify Parameters

NameTypeDescription
app_nameSTRING - The optional name of the application sending the notification. - Can be blank. -
replaces_idUINT32 - The optional notification ID that this notification replaces. The - server must atomically (ie with no flicker or other visual cues) - replace the given notification with this one. This allows clients to - effectively modify the notification while it's active. A value of - value of 0 means that this notification won't replace any - existing notifications. -
app_iconSTRING - The optional program icon of the calling application. See Icons and Images. - Can be an empty string, indicating no icon. -
summarySTRINGThe summary text briefly describing the notification.
bodySTRINGThe optional detailed body text. Can be empty.
actionsARRAY - Actions are sent over as a list of pairs. Each even element in - the list (starting at index 0) represents the identifier for the - action. Each odd element in the list is the localized string - that will be displayed to the user. -
hintsDICT - Optional hints that can be passed to the server from the client - program. Although clients and servers should never assume each other - supports any specific hints, they can be used to pass along - information, such as the process PID or window ID, that the server - may be able to make use of. See Hints. Can be - empty. -
expire_timeoutINT32 -

- The timeout time in milliseconds since the display of the notification at - which the notification should automatically close. -

-

- If -1, the notification's expiration time is dependent on the - notification server's settings, and may vary for the type of - notification. - - If 0, never expire. -

-

- If replaces_id is 0, the return value is a - UINT32 that represent the notification. It is unique, and will not be - reused unless a MAXINT number of notifications - have been generated. An acceptable implementation may just use an - incrementing counter for the ID. The returned ID is always greater than - zero. Servers must make sure not to return zero as an ID. -

- If replaces_id is not 0, the returned value - is the same value as replaces_id. -

org.freedesktop.Notifications.CloseNotification

void - org.freedesktop.Notifications.CloseNotification - (); 
UINT32 id;
 

- Causes a notification to be forcefully closed and removed from the user's - view. It can be used, for example, in the event that what the - notification pertains to is no longer relevant, or to cancel a - notification with no expiration time. -

- The NotificationClosed signal is emitted by this - method. -

- If the notification no longer exists, an empty D-BUS Error message is - sent back. -

org.freedesktop.Notifications.GetServerInformation

- void - org.freedesktop.Notifications.GetServerInformation - (name,  
 vendor,  
 version,  
 spec_version); 
out STRING name;
out STRING vendor;
out STRING version;
out STRING spec_version;
 

- This message returns the information on the server. Specifically, - the server name, vendor, and version number. -

Table 7. GetServerInformation Return Values

NameTypeDescription
nameSTRINGThe product name of the server.
vendorSTRING - The vendor name. For example, "KDE," "GNOME," - "freedesktop.org," or "Microsoft." -
versionSTRINGThe server's version number.
spec_versionSTRINGThe specification version the server is compliant with.

Signals

org.freedesktop.Notifications.NotificationClosed

- org.freedesktop.Notifications.NotificationClosed - (id,  
 reason); 
UINT32 id;
UINT32 reason;
 

- A completed notification is one that has timed out, or has been - dismissed by the user. -

Table 8. NotificationClosed Parameters

NameTypeDescription
idUINT32The ID of the notification that was closed.
reasonUINT32 -

The reason the notification was closed.

-

1 - The notification expired.

-

2 - The notification was dismissed by the user.

-

3 - The notification was closed by a call to - CloseNotification.

-

4 - Undefined/reserved reasons.

-

- The ID specified in the signal is invalidated - before the signal is sent and may not be used - in any further communications with the server. -

org.freedesktop.Notifications.ActionInvoked

- org.freedesktop.Notifications.ActionInvoked - (id,  
 action_key); 
UINT32 id;
STRING action_key;
 

- This signal is emitted when one of the following occurs: -

  • - The user performs some global "invoking" action upon a notification. - For instance, clicking somewhere on the notification itself. -

  • - The user invokes a specific action as specified in the original - Notify request. For example, clicking on an action button. -

Table 9. ActionInvoked Parameters

NameTypeDescription
idUINT32 - The ID of the notification emitting the ActionInvoked signal. -
action_keySTRING - The key of the action invoked. These match the keys sent over - in the list of actions. -

Note

- Clients should not assume the server will generate this signal. Some - servers may not support user interaction at all, or may not support - the concept of being able to "invoke" a notification. -

diff --git a/src/translations/lxqt-notificationd.ts b/src/translations/lxqt-notificationd.ts index 93eb244..4a8c633 100644 --- a/src/translations/lxqt-notificationd.ts +++ b/src/translations/lxqt-notificationd.ts @@ -1,13 +1,15 @@ - + NotificationActionsComboWidget + Actions: + OK diff --git a/src/translations/lxqt-notificationd_de.ts b/src/translations/lxqt-notificationd_de.ts index d0fc59d..801bf0e 100644 --- a/src/translations/lxqt-notificationd_de.ts +++ b/src/translations/lxqt-notificationd_de.ts @@ -4,10 +4,12 @@ NotificationActionsComboWidget + Actions: Aktionen: + OK OK diff --git a/src/translations/lxqt-notificationd_el.ts b/src/translations/lxqt-notificationd_el.ts index 2769dd0..9aed81f 100644 --- a/src/translations/lxqt-notificationd_el.ts +++ b/src/translations/lxqt-notificationd_el.ts @@ -4,10 +4,12 @@ NotificationActionsComboWidget + Actions: Ενέργειες: + OK Εντάξει diff --git a/src/translations/lxqt-notificationd_hu.ts b/src/translations/lxqt-notificationd_hu.ts index a168107..cc5df05 100644 --- a/src/translations/lxqt-notificationd_hu.ts +++ b/src/translations/lxqt-notificationd_hu.ts @@ -4,10 +4,12 @@ NotificationActionsComboWidget + Actions: Akciók: + OK diff --git a/src/translations/lxqt-notificationd_pt.ts b/src/translations/lxqt-notificationd_pt.ts index 75103ec..89b322a 100644 --- a/src/translations/lxqt-notificationd_pt.ts +++ b/src/translations/lxqt-notificationd_pt.ts @@ -1,13 +1,15 @@ - + NotificationActionsComboWidget + Actions: Ações: + OK OK diff --git a/src/translations/lxqt-notificationd_ru.ts b/src/translations/lxqt-notificationd_ru.ts index 855e405..0834093 100644 --- a/src/translations/lxqt-notificationd_ru.ts +++ b/src/translations/lxqt-notificationd_ru.ts @@ -4,7 +4,7 @@ NotificationActionsComboWidget - + Actions: Действия: diff --git a/src/translations/lxqt-notificationd_ru_RU.ts b/src/translations/lxqt-notificationd_ru_RU.ts index 4fd718d..541c5a7 100644 --- a/src/translations/lxqt-notificationd_ru_RU.ts +++ b/src/translations/lxqt-notificationd_ru_RU.ts @@ -4,7 +4,7 @@ NotificationActionsComboWidget - + Actions: Действия: