[PATCH] Turn Powerdevil suspend notification into a dialog

David Nolden zwabel at googlemail.com
Tue Sep 22 17:38:07 BST 2009


Am Dienstag 22 September 2009 16:09:51 schrieb Sebastian Kügler:
> On Tuesday 22 September 2009 14:19:57 Aurélien Gâteau wrote:
> > What do you think about this?
> 
> NAK. The notification comes from the system, the workspace (which is where
>  powerdevil lives) not from an application, it's also where other
>  notifications of system hardware state come from (network connected, power
>  connected, ...) that's where it should stay. Having it in a notification,
>  and thus always in the same location actually makes it a lot easier to
>  find the dialog, especially when you're in a hurry. Making it a dialog
>  would be a step back IMO as it looks less integrated and those small
>  dialog windows tend to get lost behind other windows. From my point of
>  view, a dialog is a no-go here. Besides, this is the exact use case why we
>  do have actions on notifications. We should not move it do dialogs at any
>  price only to not need actions on notifications (like the Ayatana spec
>  requires). I've shared my view on this particular piece of the Ayatana
>  spec more than once already, and I'd rather not repeat it over and over.
> 
> > The second patch increases the default timeout from 10 seconds to 30
> > seconds, giving the user more time to react.
> 
> OK from my POV, but probably 20 seconds is also enough. I've never missed
>  to cancel a suspend even with it being 10 seconds. (Maybe this part of the
>  patch is a sign that it now takes you longer to locate the cancel action?)
> 
The notification area was designed to get notifications _out of the way_ to 
not disturb the users workflow. And that's why this notification does not 
belong there. Suspending the machine breaks the users workflow anyway, and 
might even completely destroy it, there is no reason for this action to stay 
out of the users sight.

Furthermore, the notification area tends to be spammed with tens of 
notifications (a la requesting http://) so the important notification may 
easily get lost between such 'spam'.




More information about the kde-core-devel mailing list