[PATCH] Turn Powerdevil suspend notification into a dialog

David Nadlinger david.nadlinger at gmail.com
Wed Sep 23 10:45:12 BST 2009

I strongly support Aaron and Martin on this issue.

In my opinion, dialogs (modal or not) should only be opened directly
in response to an action the user took. I personally would be quite
confused if I were working in some arbitrary program and suddenly a
completely unrelated dialog opened, maybe even after I clicked some
button. In contrast to this, notifications are hardly caused by user
input and often do not belong to a specific application (from an
user's point of view), so it seems like a natural means to notify the
user of the critical battery level.

Furthermore, the battery level/suspension notification is not exactly
something _unexpected_ – the user was notified at least once about the
remaining battery power reaching a low level.

I am, however, strongly in favour of extending the timeout or making
the notification more »noticeable« (whatever this turns out to mean)
if this helps some users – it is just that it has never been a problem
for me.

As for the (K)Ubuntu issue: I must admit that I have never dealt with
the notification system from a developer point of view, and neither do
I know notify-osd, but I really don't understand the fuss about this:
If there is a (de facto-?)standard which covers actions in
notifications, frankly, why should we care about a downstream
application which does not adhere to this? If not, we probably should
really try to get others to support this useful feature, rather than
using it happily in our own applications, only to discover later that
the application therefore does not work in some environment X. But
that are just my two cents…


More information about the kde-core-devel mailing list