Re: About KPassivePopup

Le mercredi 28 mars 2007, Krzysztof Lichota a écrit :
> Kevin Krammer napisał(a):
> > On Thursday 22 March 2007 07:03 +0100, Kelly
wrote:
> >> I was somewhat curious; I was reading about
the project related to
> >> KPassivePopup, and the first thing I wondered
is, wouldn't it be better
> >> off as a DBus-registered daemon?  Or am I
totally off base?
> >
> > My guess is that KNotify has (or will have) a
D-Bus interface just like
> > it had a DCOP interface.
>
> Will this interface be compatible with libnotify
interface used in
> Gnome? This would make writing interoperable apps
easier 

No.

KNotify doesn't serve the same purpose as libnotify.

KNotify does powerfull and configurable notification to
application event. 
(including passive popup and sound,  but also everything
else)

"Gnome"'s libnotify is basically just used to
display passive popups.
(no per-event configuration, no others actions)

There is no link between KNotify and KPassivePopup (excepted
the fact that 
KNotify uses KPassivePopup internally when it displays a
popup)

So having an another dbus daemon for displaying
KPassivePopup would make sens 
only to be compatible with freedesktop's libnotify  (and
KNotify would use 
it)

There is a confusion because there is the "notify"
string in both name, but 
theses daemons have few things in commons.


 
>> Visit 
http://mail.kde.org/mailman/listinfo/kde-devel#unsub to
unsubscribe <<

On Wednesday 28 March 2007, Olivier Goffart wrote:
> Le mercredi 28 mars 2007, Krzysztof Lichota a
écrit :
> > Kevin Krammer napisał(a):
> > > My guess is that KNotify has (or will have) a
D-Bus interface just like
> > > it had a DCOP interface.
> >
> > Will this interface be compatible with libnotify
interface used in
> > Gnome? This would make writing interoperable apps
easier 
>
> No.
...
> So having an another dbus daemon for displaying
KPassivePopup would make
> sens only to be compatible with freedesktop's libnotify
 (and KNotify would
> use it)

another daemon isn't necessary at all. knotify can simply
create the 
interfaces on the session bus itself and deal with the calls
made to it by 
apps that use the more anemic libnotify api.

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

Full time KDE developer sponsored by Trolltech (http://www.trolltech.com
)

 
>> Visit 
http://mail.kde.org/mailman/listinfo/kde-devel#unsub to
unsubscribe <<