6.0.0-alpha12
6/7/25

[#7507] proposed changes to imp compose UI
Summary proposed changes to imp compose UI
Queue IMP
Queue Version 4.3
Type Enhancement
State Rejected
Priority 1. Low
Owners
Requester matthew.dunham (at) gmail (dot) com
Created 10/15/2008 (6079 days ago)
Due
Updated 11/06/2008 (6057 days ago)
Assigned
Resolved 11/06/2008 (6057 days ago)
Milestone
Patch Yes

History
11/06/2008 04:43:20 AM Chuck Hagenbuch Comment #2
State ⇒ Rejected
Reply to this comment
I see this as similar to the attachment interface in DIMP (which I 
really like) in terms of the functionality lost, but not quite as 
streamlined UI-wise. I don't think it's worth the tradeoff. It 
actually applied with just some fuzzy offsets to HEAD, though, so nice 
work on that, and some people may well prefer it - you might want to 
put the patch on the wiki with other contributed modifications.
10/15/2008 08:39:12 PM matthew (dot) dunham (at) gmail (dot) com Comment #1
Priority ⇒ 1. Low
New Attachment: imp-compose-ui.patch Download
Patch ⇒ Yes
Milestone ⇒
Queue ⇒ IMP
Summary ⇒ proposed changes to imp compose UI
Type ⇒ Enhancement
State ⇒ New
Reply to this comment
Many of my customers were confused by the IMP attachment handling so

I've done some UI revisions to the message composition screen.



In the current UI, the attachment "button" in compose options doesn't

take any obvious action -- my end users were expecting a popup like the

"address book" or "special characters" options. And the esoteric

attachment options (e.g. "attachment" vs "inline" disposition and

attachment description) are confusing to users who have come from other

webmail services.



I simplified this by removing attachment button, relocating the message

attachment section just above the message body, and removing the

extraneous options to keep the UI clean. Also, I changed the units of

Max Attachment Size to MB -- bytes didn't make a lotta sense here. 
I've got a screenshot of the changes here:



   http://ic.ucsb.edu/~matthewdunham/misc/compose_screenshot.png



If these are acceptable I'd love to see them integrated into the trunk.

I've included patches (to 4.3), but these could maybe use a bit of

review to ensure they're properly Horde-ified.

Saved Queries