Shared OSD Service for KDE

[Aaron J. Seigo]

On May 11, 2010, Lubos Lunak wrote:
>  And I actually think this should be an addition to KNotification (with the
> obvious requirement of adding a way to send the numeric value) rather than
> something separate. Why should an app decide whether to do a notification
> about something using OSD or something else instead of simply sending it to
> KNotification to deal with it?

really good idea imho; KNotification would require adding a numeric value, as 
you note, and we'd need a new category in KNotify for OSD, but that would be 
about it.

what do you think about putting the OSD display directly in KNotify as well 
(instead of a kded module)? it would probably still need to expose a dbus 
interface if/when we wanted to make this an fd.o specification, though. but 
KNotify could easily just register that service itself and it would be 
"talking to itself" (which avoids hitting the bus at all with QtDBus iirc) so 
should be reasonable.

-- 
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

KDE core developer sponsored by Qt Development Frameworks
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20100511/5e491b6b/attachment.sig>