Notification spec issue: Ability to assign an icon *and* an image to a notification

Lubos Lunak l.lunak at
Thu Jun 25 06:35:22 PDT 2009

On Thursday 25 of June 2009, Aurélien Gâteau wrote:
> Olivier Goffart wrote:
> > The visual notifications is not suposed to do that. KNotify does.
> >
> > That's why it is very important not to use org.fd.Norifications.  So
> > developer does get confused.
> In the case of KDE, KNotify takes care of non visual notifications and
> delegates visual notifications to Plasma, which implements the spec
> (after my patch). This does not mean other implementations can't do
> things differently.
> I see nothing wrong having the KDE implementation showing notifications
> as Plasma bubbles, while another implementation instead logs them to a
> file or plays them back with a text-to-speech engine.

 I do. I see it as wrong that I would not be able to tell the KDE 
implementation that I'm not interested in any bubbles from FooApp that 
happens to annoy me with them all the time. I myself would even see it as 
wrong not to be able to use bubbles for some events and some other way of 
notifying for other events. All the stuff it's been always quite easy to do 
with KNotify and next to impossible with Galago. It's really rather sad to 
see all this discussion about a spec which is younger, inferior and less 
flexible and its only advantage is that its developers simply bluntly took 
the name :(. That alone should be a good reason to rename it, 
just so that this doesn't repeat again.

> > It is not a big deal.  Modifications need to be done anyways, and
> > changing the name is one line of code of change.
> Suppose you are using a library which provides a class named Foo. This
> library has been in use for 5 years, but you think the class really
> should have been named FooBar. Would you ask the library maintainers to
> break binary compatibility to get the class renamed?

 This is such a bad analogy in practice that I even don't know where to start.

> KDE developers use the KNotification class, other developers use
> libnotify. They don't care about the DBus name. Why change just for the
> sake of change, especially since not all parties consider this change to
> go in the right direction?

 If they don't care about the name, the question then should be 'Why do we 
need this discussion at all?'.

Lubos Lunak
KDE developer
SUSE LINUX, s.r.o.   e-mail: l.lunak at , l.lunak at
Lihovarska 1060/12   tel: +420 284 084 672
190 00 Prague 9      fax: +420 284 028 951
Czech Republic

More information about the xdg mailing list