Re: [PATCH] Rudimentary libnotify support

[Pawel Salek <pawsa theochem kth se>]

On 04/10/2007 08:50:05 PM, Albrecht Dreß wrote:
> [snip]
> Some more glitches:
>
> IMO, real errors should still be dialogues.  E.g. if sending an
> encrypted message fails due to a missing key, the "message could not  
> be sent" dialogue is still there, but the reason is in the  
> notification and disappears after a few seconds.  If the user is  
> somewhat inattentive, there is no clue what went wrong.

Agreed.

> Probably it is better to add "Notification" as configuration option  
> (also solving the previous point), so the user has the choice of  
> "Nothing", "Terminal", "Notification", "Status bar", etc.  E.g. I  
> configured information messages to be printed on the terminal, but  
> now I get tons of "signature with insufficient trust" notifications.   
> Clicking quickly through a mailbox I could build a pile of 6 or 7  
> /identical/ ones.  There is no relation any more to the actual action  
> of the user or to the message which triggered it.

Hm, I would rather try as hard as possible to make an intelligent guess  
so that users do not need to tweak it.

I would rather have notifications only used for events happening  
without user interaction, like messages arriving in the background etc.  
Otherwise, it can easily become distracting. I think rhythmbox uses  
notifications in a right way: if a new song is played, a notification  
is displayed - but not when the user himself clicks on another song.

Pawel