Should have builtin actions support
Bug #1107919 reported by
Bastien Nocera
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
notify-osd (Ubuntu) |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
(See also bug #542059)
notify-osd is the only notification-daemon around that doesn't support actions (I count KNotify, gnome-shell's implementation, notification-
Instead of making application developer's life painful (by requiring them to implement fallbacks for the sake of notify-osd), notify-osd should implement the fallback itself.
It should be fairly easy for notify-osd to create a GTK+ dialogue itself, and destroy it when the notification is dismissed.
This would solve problems with existing software, or cleanups done in the GNOME stack in recent versions.
Changed in notify-osd: | |
importance: | Undecided → Wishlist |
status: | New → Triaged |
affects: | notify-osd → notify-osd (Ubuntu) |
To post a comment you must log in.
This discussion pops up a lot. The fact is, the Notifications spec includes actions as an optional feature that the notifications server does not need to support. It is up to the client to handle that situation, and at this point most existing clients do. I agree, this is terrible from an ecosystem standpoint (nobody wants to devote 50+ lines of code and multiple translated strings to generate special notifications for servers with and without certain capabilities), but this also isn't really the sort of thing that can be approached as a concrete bug to fix. It's a design decision, made quite a while ago, and if we want to debate it I think that should be done in a suitable discussion forum. If you want a concrete bug, I think the bug is that the notifications spec is getting increasingly painful thanks to the proliferation of optional server capabilities. (I guess there's another issue that Notify OSD's existing fallback dialog is practically user-hostile at times, but that's also kind of separate from this).
Please do bring this up on Freedesktop.org, and the the Unity mailing list if you feel this affects Unity. Keep in mind you aren't the first to suggest this for Notify OSD, though, so you may want to check out past discussions as well. Some code or mockups based on the existing design at http:// wiki.ubuntu. com/NotifyOSD could go a long way, if you have the time.