Thunderbird:Compact Message Header:Use Cases: Difference between revisions

← Older edit

Thunderbird:Compact Message Header:Use Cases (view source)

Revision as of 14:40, 15 August 2009

1,200 bytes added , 15 August 2009

→‎Use Cases

BradleyBaetz

2

edits

@@ Line 1: / Line 1: @@
-In Thunderbird 3, {{Bug|480623}} moves compact header view to an extension. Please list use cases where compact header is helpful and/or normal message header gets in the way. A use case in this context should ideally include a '''specific''' type of user, a '''specific''' type of mail, and circumstances or work flow implications.  The purpose is to collect information which will later be organized, discussed, and used toward the end goal of a) improving how compact header view is supported, and b) helping specific use cases where improving compact header is not sufficient to significantly improve the use case.
+In Thunderbird 3, {{Bug|480623}} moves compact header view to an extension. Please list specific use cases where compact header is helpful and/or normal message header gets in the way. A use case in this context must include a '''specific''' type of mail and/or a '''specific''' type of user, plus the circumstances of how work flow is impacted.  The purpose is to collect information which will later be organized, discussed, and used toward the end goal of a) improving how compact header view is supported, and b) helping specific use cases where improving compact header is not sufficient to significantly improve the use case.
-The "need" for vertical space and your passion for the need are of course assumed, and so should be omitted from the use case (see [[#Notes_and_Assumptions]]).  Discussion and promoting one's position beyond the specifics is a non-goal. A short one or two sentence description limited to '''how''' the message pane is used in a specific case will be most helpful.
+The "need for vertical space" and your passion for the need are of course assumed, and so should be omitted from the use case (see [[#Notes_and_Assumptions]]). Discussion and promoting one's position beyond the basic details is a non-goal. Generic use cases are not helpful. A short one or two sentence description limited to '''how''' the message pane is used in a specific case will be most helpful. Link to screen shot may be helpful.
 = Use Cases =
-* Generally, being able to see as much of a message's body as possible without being forced to scroll! Vertical space should be of primary importance!
-* Very many (most?) users read their e-mails in the preview pane. Giving them a non-sucky experience should be a priority.
-* Reading e-mails, which are typically taller than the preview pane. Showing as much as possible and minimizing scrolling is critical.
 * Viewing photos from family & friends, which are typically taller than the preview pane. Users should be able to see at least one *full* photo without scrolling.
@@ Line 23: / Line 17: @@
 * Newsgroups graphics (stationery) posts that assume a larger viewing window. As compared to OE, we offer an 8% reduction in size.
-* Users of previously composed Templates will have to adjust for the new smaller viewing window.
+* Chain-letter e-mails with long texts that extend beyond the view-port.
+* e-mails with (many) attachments where the additional attachments pane (on the bottom) further reduces the size of the view-port.
+* e-mail conversations where the participants use interspersed quoting (like in newsgroups).
+* e-mails with long texts (e.g., a "letter" from Mom).
+* e-mails with very large fonts (e.g., from elderly AOL users).
+* e-mails where the sender used bottom-quoting (Thunderbird's default setting - unfortunately).
+* Business e-mails, which often have vertically long signatures (to see the contact info).
+* Reading e-mails on smaller screens (e.g., the very popular netbooks) is very painful with the huge header.
+* Reading the vast majority of emails where most header information is superfluous and displaying it in an expanded method is a waste of screen real estate. (e.g. content-transfer-encoding)
+* Reading the vast majority of emails/newsgroup postings where redundant information is presented - e.g. date header, references header in threaded mode
-* The problem pertains to standalone window as well as the preview pane. I think that there are more users using the standalone model as opposed to the preview pane, as is commonly understood.
+* Older computers, often used in developing countries, require simpler user interfaces. All that extra drawing takes a huge toll on the speed of the computer.
-* Implementing Bug # 499516 IMO would be the best of both worlds. Showing the header pane where appropriate and helpful, and hiding it when not needed.
+* When scanning a folder/newsgroup only for 'interesting' threads, need to be able to view the content and also easily scan the thread titles, rather than having a third of my vertical screen space taken up with the headers (see [[http://members.optusnet.com.au/~bbaetz/wasted-thunderbird-space.png]])
 = Notes and Assumptions =
-* Compact header view would be less needed if the normal header were kept to a minimum or if it scrolled with the message.
+* Compact header view would be less needed if the normal header were kept to a minimum <s>or if it scrolled with the message</s>.
+* Scrolling is not an alternative as the action buttons would scroll out of reach &rarr; conflict of {{bug|325144}}/{{bug|464309}} vs. {{bug|474523}}.
+* Having action buttons in the message area, as well as in the tool bar, is something people actually want (not always the case).
 = References =
 * [API doc] (not yet available)
 * {{Bug|480623}} - move compact message header view to an extension
+* {{Bug|499516}} - provide fullscreen (content only) viewing option
+* workarounds:
+** [http://compactheader.mozdev.org/index.html compactheader extension]