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

[Olivier Goffart]

Le Thursday 25 June 2009, Brian J. Tarricone a écrit :
> On 06/25/2009 06:35 AM, Lubos Lunak wrote:
> >   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.
>
> Why can't you do this today?  The org.freedesktop.Notifications.Notify()
> method has app_name as its first parameter.  Why can't you add support
> to your notifications server to remember app names it's seen and then
> present a GUI that allows the user to reject notifications based on app
> name, or throttle them, or something like that?

Because that would be incompatible and MUCH LESS powerfull with what KDE is 
doing today with KNotify.

> It also has the advantage that it has working implementations that a lot
> of people use.  You may find it easy to dismiss that over in KDE land
> (and I certainly understand why), but that dismissal does not sit well
> with me.

Well, the specification has been done dismissing the existing KDE 
requirements.   And then KDE is expected to regress to fit the spec.
No thanks.