|Deletions are marked like this.||Additions are marked like this.|
|Line 2:||Line 2:|
|* '''Created''': 2009-05-25|
Launchpad Entry: dx-karmic-notify-osd
Contributors: Canonical "Desktop Experience"- and "User Interaction Design"-teams, numerous Ubuntu-community members
Packages affected: notify-osd, evolution, firefox, NetworkManager, gnome-settings-daemon, pidgin
For Karmic Koala (Ubuntu 9.10) we want to improve the capabilities and user-experience of the notification-daemon notify-osd and further its integration into the Ubuntu- and Kubuntu-desktop.
Rendering / performance aspects
- surface tweaks, blur cache
- non-composited fallback mode
- adapt better to the DPI settings
- improving the appearance and behavior (making composited bubbles more obviously unclickable, and non-composited bubbles classier, pause on hover, proximity hover, more subtle transitions)
- investigating whether we can use non-critical priorities for anything useful
- positioning on (multiple) screen(s), depending on the type of notification
- experimenting with better positioning for the notification bubbles
- implementing the duration rules, so that notifications with longer text are shown for longer
- better handling of long backlogs of notifications
- accessibility, e.g. sound theme compliance and maybe alt text for icons
Audio application enhancements
- consistent feedback for multimedia keys
- better DnD mode (Do-not-Disturb) for full-screen applications, adaptive timer
- suppressing bubbles when any window is full-screen
- (agateau and ScottK could provide the needed bullet points here)
Contribute our experience to FDO
Helping to get the FreeDesktop notifications specification to 1.0
- a test suite for the rendering layer.
The new included version of notify-osd x.y.z now provides increased rendering performance (and reduced CPU-usage) in general, notification-bubbles look nicer on non-composited desktops, non-critial notifications are now suppressed when using an application in fullscreen-mode or the screensaver is active (but e.g. notifications like "battery-low" still show up), on-screen time of notification now adapts to user behaviour (e.g. timing out is paused when a user hovers the mouse-pointer over a notification-bubble), notifications better adjust their positioning to users with multi-screen setups, old notifications (of exited or crashed applications) get removed from the notification queue, feedback-notifications for multi-media keys on keyboards are introduced again (e.g. Play/Pause, Stop, Forward, Backward).
The original specification to improve of the notification-system used in Ubuntu written for the Jaunty Jackalope (Ubuntu 9.04) was not fully implemented in time due to its complexity and interaction with so many external applications. Furthermore the gather feedback and bug-reports from users introduced rethinking some aspects of the original specification, which has been updated since.
You can have subsections that better describe specific parts of the issue.
The looks of notifications
- no non-composited case (designs still missing)
Mandatory (applications in main):
"Nice to have" (applications in universe):
Application developers need to be aware of NotificationDevelopmentGuidelines and NotificationDesignGuidelines if they want to make sure their applications notifications seamlessly integrate with notify-osd on the Ubuntu desktop.
It's important that we are able to test new features, and demonstrate them to users. Use this section to describe a short plan that anybody can follow that demonstrates the feature is working. This can then be used during testing, and to show off after release. Please add an entry to http://testcases.qa.ubuntu.com/Coverage/NewFeatures for tracking test coverage.
This need not be added or completed until the specification is nearing beta.
This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.
BoF agenda and discussion
Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what was discussed and note any options that were rejected.