Comment 141 for bug 390508
Revision history for this message
| Sebastien Bacher (seb128) wrote Re: notify-send ignores the expire timeout parameter | #141 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
> Decisions should be based on feedback. In this case from developers and users in terms of experience. At the moment developers are crying out for this feature. We don't know how users will be affected, because I would guess it's not been tried
That's not true, Canonical does organize user testing sessions and watch non technical users dealing with Ubuntu. We have been using the old notification-daemon which respects timeout settings for years before notify-osd. The complain there come from some technical users or softwares writers not so much from non technical users out there.
> With a notification app, you need to think how it's going to be used. We've defined plenty of use cases above. And from example use cases define an appropriate public interface.
No, the current design is that notifications are unintrusive and just used to get informational content displayed. They are not used to display questions. They are not used to display important informations. They are not displayed when interaction is required.
You can read those wikipages to understand the design principle for those choices:
https:/
https:/
The first document describes what other solutions Ubuntu recommends to softwares writers that need interactivity. You might think that using notifications and tweaking the way users interact with it is the only way but it's not. You might disagree on the design described there but give some credit to those who worked on it and read those, you will see that lot of efforts, thinking and real world usecases consideration has been in action and it not a decision made in an hurry to annoy users.