<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 8/14/2012 8:33 AM, Axel Grude wrote:<br>
</div>
<blockquote cite="mid:502A457D.9000308@gmail.com" type="cite">
<div id="smartTemplate4-template">
<h2>Proposed new List</h2>
<ul>
<li><font color="#3333ff">Contacts</font></li>
<li><span class=""><span class="">Folders </span>Management<br>
</span></li>
</ul>
</div>
</blockquote>
For clarity: are you talking about managing 10k messages in a folder
here, or managing 10k folders?<br>
<blockquote cite="mid:502A457D.9000308@gmail.com" type="cite">
<div id="smartTemplate4-template">
<ul>
<li><span class="">Message composing</span></li>
</ul>
</div>
</blockquote>
Message Composition is probably a better name.<br>
<blockquote cite="mid:502A457D.9000308@gmail.com" type="cite">
<div id="smartTemplate4-template">
<ul>
<li><span class=""><font color="#3333ff">Message Reading</font></span></li>
<li><span class=""><font color="#3333ff">News Reading<br>
</font></span></li>
</ul>
</div>
</blockquote>
I would combine these two for sure. The distinction isn't that great
(I believe the original intent was to separate NNTP-centric addons
from mail-centric, but particularly the fact that RSS was at one
point exposed in the UI as "News and Feeds" means that "News" is a
very poor name for classification).<br>
<blockquote cite="mid:502A457D.9000308@gmail.com" type="cite">
<div id="smartTemplate4-template">
<ul>
<li><span class="">Calendar & Date / Time related add-ons</span></li>
</ul>
</div>
</blockquote>
Very wordy title. "Calendar" or "Calendaring" is probably better,
since I don't think there's a lot of value in pulling some pure
date/time-related addons into the same category of what is
effectively addons to Lightning.<br>
<blockquote cite="mid:502A457D.9000308@gmail.com" type="cite">
<div id="smartTemplate4-template">
<ul>
<li><span class="">Signatures & Headers</span></li>
</ul>
</div>
</blockquote>
This strikes me as two very different things smashed into one
category, and I don't think it's entirely clear from a user
perspective what would go in here. "Signature" is overloaded to mean
both S/MIME-esque signatures as well as that little thing at the
bottom of every email, while I don't know how prevalent "headers" is
in use in the sense that it exists for email. If you look at things
from a workflow perspective, very likely everything here would go
into message composing or message reading anyways, so having a
specific section for them isn't very useful.<br>
<blockquote cite="mid:502A457D.9000308@gmail.com" type="cite">
<div id="smartTemplate4-template">
<ul>
<li><span class="">Filters</span></li>
<li><span class="">Search Tools</span></li>
</ul>
</div>
</blockquote>
Filtering and search go hand-in-hand; I don't think there's a lot of
reason to separate the two out<br>
<blockquote cite="mid:502A457D.9000308@gmail.com" type="cite">
<div id="smartTemplate4-template">
<ul>
<li><font color="#cc0000"><span class="">Tags</span></font></li>
</ul>
</div>
</blockquote>
Which kind of tags? Tags in the calendar? address book? folder tags?
tags as folders? tags on messages? Too much ambiguity here, and I
don't think it usefully breaks up any components.<br>
<blockquote cite="mid:502A457D.9000308@gmail.com" type="cite">
<div id="smartTemplate4-template">
<ul>
<li><span class="">Chat & IM</span></li>
<li><font color="#3333ff"><span class="">Dictionaries &
Language support</span></font></li>
<li><span class="">Backup & Archiving</span></li>
<li><a moz-do-not-send="true"
href="https://addons.mozilla.org/en-US/thunderbird/extensions/privacy-and-security/">Privacy
and Security</a></li>
<li><span class="">Toolbars</span></li>
<li><span class="">Appearance</span></li>
</ul>
</div>
</blockquote>
Appearance is a vague term, but I'm not quickly finding anything
better. I'm not certain there's any gain from splitting out Toolbars
from appearance, especially if we can come up for a name for
Appearance that would capture its intent better (AIUI, any UI
feature that's not directly controlled by or controlling anything
explicitly called out here).<br>
<blockquote cite="mid:502A457D.9000308@gmail.com" type="cite">
<div id="smartTemplate4-template">
<ul>
<li><span class="">Developer Tools</span></li>
</ul>
</div>
</blockquote>
I'm divided here. There is/will be definitely a sizeable set of
tools to include in here if we port a lot of the current devtools
work to Thunderbird. On the other hand, I am not sure making this an
explicit category is any more beneficial than publishing an add-on
collection (or set of collections) for things like "this is useful
for debugging Thunderbird!"<br>
<blockquote cite="mid:502A457D.9000308@gmail.com" type="cite">
<div id="smartTemplate4-template">
<ul>
<li><span class="">Folder pane customisation</span></li>
</ul>
</div>
</blockquote>
Customizing the folder pane is nothing more than another way to
manage a lot of folders/accounts.<br>
<blockquote cite="mid:502A457D.9000308@gmail.com" type="cite">
<div id="smartTemplate4-template">
<ul>
<li><span class="">Browsing</span></li>
</ul>
</div>
</blockquote>
Browsing what? Considering that web browsing is not a core feature
of Thunderbird, I'm not sure there's value from separating from
miscellaneous.<br>
<blockquote cite="mid:502A457D.9000308@gmail.com" type="cite">
<div id="smartTemplate4-template">
<ul>
<li><span class=""><font color="#3333ff">Miscellaneus</font><br>
</span></li>
</ul>
</div>
</blockquote>
<br>
Keep in mind that we do have search functionality for addons, and we
can build collections where it makes sense. With that in mind, it is
probably better to have very broad categories instead of narrow
definitions.<br>
<pre class="moz-signature" cols="72">--
Joshua Cranmer
News submodule owner
DXR coauthor</pre>
</body>
</html>