[KDE4] KNotification

Gary Cramblitt garycramblitt at comcast.net
Sat Sep 17 02:52:22 BST 2005


On Friday 16 September 2005 07:46 pm, Olivier Goffart wrote:
> But KTTSD could be included directly into KNotification
> I mean that add more actions in the the current notification config dialog.
> Note that this dialog will also be reworked in order to make it more
> usable.

That's fine for KTTSD, but what about any other application that wants to 
subscribe to notifications system-wide?  The idea first surfaced here:

http://lists.kde.org/?l=kde-core-devel&m=106198899127815&w=2

> > One way to solve this without having the KNotify daemon would be for the
> > client library to automatically put every notification on the dbus (with
> > appropriate type flags, etc.) or broadcast a dcop message.

Actually, I think I misspoke about dcop.  Without a common sender object, I 
don't think I can receive the dcop signals. ??  If I'm not mistaken, anyone 
can listen on the dbus and as long as all notifications have some sort of 
notification flag, I should be able to filter for them.

> Yes, but it will only handle passive popups.

Why just passive popups?  The fd.o spec calls for a server in order to 
coordinate notifications (so that apps don't stomp on each other's 
notifications).

"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."

-- 
Gary Cramblitt (aka PhantomsDad)
KDE Text-to-Speech Maintainer
http://accessibility.kde.org/developer/kttsd/index.php




More information about the kde-core-devel mailing list