| Summary | Implement humanized messages in Horde |
| Queue | Horde Base |
| Queue Version | HEAD |
| Type | Enhancement |
| State | Accepted |
| Priority | 1. Low |
| Owners | |
| Requester | chuck (at) horde (dot) org |
| Created | 12/02/2007 (6373 days ago) |
| Due | |
| Updated | 03/09/2009 (5910 days ago) |
| Assigned | |
| Resolved | |
| Milestone | Horde 4.0 |
| Patch | No |
http://www.writebetterbits.com/2009/02/growl4rails-rails-growl4.html
State ⇒ Stalled
Milestone ⇒ Horde 4.0
Priority ⇒ 1. Low
Type ⇒ Enhancement
Summary ⇒ Implement humanized messages in Horde
Queue ⇒ Horde Base
State ⇒ Accepted
http://binarybonsai.com/misc/humanmsg/
From Filippo:
For the last few days I've been trying a number of different settings
on this and have found that in my experience, 3 seconds is the optimum
time for "positive messages" (success ones), 10 seconds for "negative
messages" (can't do something) and permanent for critical messages.
as for dismissing messages, I'd go for automatic for positive,
key/mouse click/close for negative and critical... mouse movement is
dangerous as it would dismiss critical messages even if a user just
bumps the table :)