Notification spec issue: Ability to assign an icon *and* an image to a notification
William Jon McCann
william.jon.mccann at gmail.com
Wed Jun 24 12:22:02 PDT 2009
On Wed, Jun 24, 2009 at 1:18 PM, Aaron J. Seigo<aseigo at kde.org> wrote:
> this service name under the fd.o namespace was hijacked without consensus, and
> that's simply not on. the implications of "first come, first serve, no
> collaboration needed, forced it on the rest" is completely broken behavior and
> shows a complete disregard for the entire concept of using a shared namespace
> and working towards shared standards. anyone who implemented
> "org.freeesktop.Notifications" did so a their own risk as it was _not_ within
> their purview to simply claim that service name in what is a shared namespace.
> consider the ramifications of me going and registering
> org.freedesktop.SystemTray or even org.gnome.SystemTray just because i can.
> that simply doesn't work as a mechanism.
> using org.freedesktop.Notifications was a mistake, one that set up an
> absolutely horrible precedent. along with similar irresponsible actions we
> seen over the years here, it threatened fd.o's ability to legitimately be
> called shared and participatory. this is not theoretical: i've had to
> vigorously defend fd.o to certain people in KDE who cite such behaviour, this
> spec being one actual example of it, as proof that fd.o is _not_ collaborative
> and is _not_ in our best interests.
I haven't really followed the entire thread there so can't comment on
this use in particular. However, I'd like to point out that KDE
shouldn't be using org.freedesktop.ScreenSaver (it is currently) since
we never reached consensus on what that should be.
More information about the xdg