<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=windows-1252">
</head>
<body smarttemplateinserted="true" bgcolor="#FFFFFF" text="#000000">
<div id="smartTemplate4-template"><img style="margin-top: 1em;
float: right; box-shadow: 1px 1px 2px rgba(20, 20, 20, 0.4);"
moz-do-not-send="false" class="myLogo"
src="cid:part1.D8ACA26F.FC790511@gmail.com" alt="Get
Thunderbird!" height="15" width="94">
</div>
<div id="smartTemplate4-quoteHeader">
<style type="text/css" scoped="">
#newHeaderAG1 b { font-weight:bold; color: #990033; min-width: 4.5em; max-width:none; display:inline-block;}
</style>
<blockquote type="cite" style="margin-bottom: -20px !important;
padding-bottom:20px !important;">
<div id="newHeaderAG1" style="font-size: x-small; padding:1em;
background-color:rgba(220,220,240,0.4); border-radius:3px;"> <b>Subject:</b>Re:
Sample Thunderbird UI redesign<br>
<b>From:</b>Disaster Master
<a class="moz-txt-link-rfc2396E" href="mailto:disasterlistmanager@gmail.com"><disasterlistmanager@gmail.com></a><br>
<b>To:</b>Tb-planning <br>
<b>Sent: </b>Monday, 12/12/2016 15:05:09 15:05 GMT ST +0000
[Week 50]<br>
</div>
</blockquote>
</div>
<blockquote class=" cite"
id="mid_a9015d82_af96_5268_9675_af0e0d86fbd2_gmail_com"
cite="mid:a9015d82-af96-5268-9675-af0e0d86fbd2@gmail.com"
type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<div class="moz-cite-prefix">On 12/12/2016 9:33 AM, Wayne Mery <a
moz-do-not-send="true" class="moz-txt-link-rfc2396E"
href="mailto:vseerror@lehigh.edu"><vseerror@lehigh.edu></a>
wrote:<br>
</div>
<blockquote class=" cite"
id="mid_74d10789_d195_52b0_3128_c7c05b6c1459_lehigh_edu"
cite="mid:74d10789-d195-52b0-3128-c7c05b6c1459@lehigh.edu"
type="cite">
<pre wrap="">On 12/12/2016 9:10 AM, Disaster Master wrote:
</pre>
<blockquote class=" cite" id="Cite_2473194" type="cite">
<pre wrap="">On 11/21/2016 9:35 AM, Disaster Master <a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="mailto:disasterlistmanager@gmail.com"><disasterlistmanager@gmail.com></a>
wrote:
</pre>
<blockquote class=" cite" id="Cite_8961963" type="cite">
<pre wrap="">On 11/18/2016 8:42 PM, R Kent James <a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="mailto:kent@caspia.com"><kent@caspia.com></a> wrote:
</pre>
<blockquote class=" cite" id="Cite_7516898" type="cite">
<pre wrap="">I think you can see from the responses that there never seems to be any
way to come to a common ground in user interface changes. I'll long
since given up trying to propose changes, as inevitably what I propose
gets shot down. I suspect that others have given up as well. I am also
guilty of being the shooter in many cases, after all we all have opinions.
The only answer that I think we have agreed with is to pick someone who
has a clear vision of a unified design to be the user interface czar,
and just do what they want.
</pre>
</blockquote>
<pre wrap="">The only answer? What may I ask is wrong with my proposal to simply
improve the underlying code to allow better access for Themes to be
able to change the UI?
In what way is this not a much better solution than a 'UI Czar' who,
as you clearly outlined, will inevitably upset a large number of people?
Better Theme support totally eliminates said controversy.
</pre>
</blockquote>
<pre wrap="">I would really like an answer to this Kent...
</pre>
</blockquote>
<pre wrap="">It seems you are suggesting that themes can facilitate the rearranging
of UI, or changing the logic/interaction of UI. That's not the purpose
of a theme. Themes are about skinning, which is changing the appearance
of *existing* UI.
</pre>
</blockquote>
<br>
Fair enough, thanks Wayne. In all honesty, I was struggling to
find a single word that expressed the ability to customize the UI,
so I settled on Theme. Guess that wasn't the best choice.<br>
<br>
My primary concern is maintaining the ability to customize the UI,
over and above any changes to the default GUI presented on a fresh
install.<br>
</blockquote>
<p>Well, in my experience that is provided by XUL. Of course to make
the GUI functional you also need to be able to inject code that
does something useful (especially in the realm then you also need
XPCOM which gives you access to the low level, scriptable parts of
the email front end code; this also includes access to GLODA (the
database behind the search engine in Thunderbird).</p>
<br>
<blockquote class=" cite"
id="mid_a9015d82_af96_5268_9675_af0e0d86fbd2_gmail_com"
cite="mid:a9015d82-af96-5268-9675-af0e0d86fbd2@gmail.com"
type="cite"> <br>
So, a question for you.<br>
<br>
Is there any reason that a Theme Addon (Themes are still Addons,
right?) couldn't do the same things as, say, Classic Theme
Restorer?<br>
</blockquote>
There are restrictions with Themes, normally they shouldn't contain
executable codes, but some full themes circumvent this restriction
by bundling an extension with the xpi.<br>
<br>
<blockquote class=" cite"
id="mid_a9015d82_af96_5268_9675_af0e0d86fbd2_gmail_com"
cite="mid:a9015d82-af96-5268-9675-af0e0d86fbd2@gmail.com"
type="cite"> <br>
Also, is it possible to write an Addon that makes changes like,
for example, moves/places toolbar elements (buttons, location bar,
search bar, etc) to a specific toolbar, in a certain order, then
hides certain other toolbars?<br>
<br>
</blockquote>
yes.<br>
<blockquote class=" cite"
id="mid_a9015d82_af96_5268_9675_af0e0d86fbd2_gmail_com"
cite="mid:a9015d82-af96-5268-9675-af0e0d86fbd2@gmail.com"
type="cite"> Regardless, upon reflection, I can see value in
Kent's suggestion for a GUI 'czar', as long as the ability to
customize the GUI provided as the default by said 'czar' remains
fully intact.<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
tb-planning mailing list
<a class="moz-txt-link-abbreviated" href="mailto:tb-planning@mozilla.org">tb-planning@mozilla.org</a>
<a class="moz-txt-link-freetext" href="https://mail.mozilla.org/listinfo/tb-planning">https://mail.mozilla.org/listinfo/tb-planning</a>
</pre>
</blockquote>
<br>
<br>
</body>
</html>