Improvements for notifications (notify-osd) in Lucid
For the Lucid Lynx release there are a few evolutionary improvements planned. This is purely work within the scope of maintainance and polish.
Blueprint information
- Status:
- Not started
- Approver:
- David Barth
- Priority:
- Undefined
- Drafter:
- Mirco Müller
- Direction:
- Needs approval
- Assignee:
- Mirco Müller
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Whiteboard
* Have a "do-not-disturb" mode that individual applications can trigger. Popular applications that have a full-screen mode (Firefox, Totem, OpenOffice.org, Vino) should have a visible option for whether/when to inhibit non-critical notifications when a window of that application is full-screen and focused. We should decide the appropriate default for those applications, and we should provide guidelines on implementing this preference in other applications.
* As a trial during the Lucid development cycle, when an application inhibits notifications, we should display a notification: "Further notifications have been disabled."
* When an application that requested notification inhibition exits, notifications should always be uninhibited.
* During the Lucid developer cycle, notification bubbles should use color and label to show priority.
* Change in position: The top of any notification bubble should be positioned near the bottom right corner such that if the bubble grows to its maximum height, it is snug at the bottom right corner. Confirmation bubbles should use a slot immediately above that notification bubble slot.
* Extend the KDE notification API so that applications can tell whether the notification server allows actions.
* Use the API in KDE applications in Main and Universe
* Application review and compatibility fixes.
* Implement missing details, duration based on text length.
* Update and complete notification development guidelines.
