<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-CA link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US'>So, this diagram worries me, because it’s adding more layers of inheritance, and that’s been problematic in the past. It becomes an issue because it’s not clear what’s potentially layering on top when you’re making a change (i.e. in WinLin there’s four different places there could be a rule modifying what you’re changing).<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US'>I was hoping that this was closer to “one unified theme with different platform CSS only when absolutely necessary” (which feels like a huge win for developer sanity). That would mean shared + WinLin / OSX are the only layers in play, so it’d be much more obvious if the code is platform specific or shared.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US'>-- Mike<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> firefox-dev [mailto:firefox-dev-bounces@mozilla.org] <b>On Behalf Of </b>Mike de Boer<br><b>Sent:</b> March 26, 2014 10:44 AM<br><b>To:</b> Firefox Dev<br><b>Subject:</b> Re: Proposal: Introduce a WinLin theme<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>I was hoping my message would’ve been clear (hence my lengthy email, which I generally tend to avoid), but I see I didn’t succeed…<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Allow me to try with a little schematics:<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><span style='font-family:"Courier New"'> Themes</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-family:"Courier New"'> —> Shared</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-family:"Courier New"'> —> OSX</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-family:"Courier New"'> —> WinLin</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-family:"Courier New"'> —> Windows</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-family:"Courier New"'> —> Aero</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-family:"Courier New"'> —> XP</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-family:"Courier New"'> —> Linux</span><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>So we’d practically start with moving all styles and resources that are currently shared between Windows and Linux to WinLin. After that it’s possible to apply/ move even more Windows styles to WinLin, so that Linux will inherit more over time.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Thusly, having more styles common between Windows and Linux will be up to UX, of course. Right now, for example, the buttons placed in toolbars other than the nav-bar assume the GTK-look, which will most likely end up to inherit the (Windows) Australis style in the near future as bugs get filed by Linux users.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I hope this adds the necessary context to my message.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Mike.<o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On 26 Mar 2014, at 15:14, Mike Connor <<a href="mailto:mconnor@mozilla.com">mconnor@mozilla.com</a>> wrote:<o:p></o:p></p></div><p class=MsoNormal><br><br><o:p></o:p></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal><br>On Mar 26, 2014, at 8:19 AM, Mike de Boer <<a href="mailto:mdeboer@mozilla.com">mdeboer@mozilla.com</a>> wrote:<br><br><br><o:p></o:p></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal>My proposition is to create a shared theme for Linux and Windows, let’s call it WinLin for the time being, that collects all the styles and assets we can share for both OSes and start with the Windows (8) theme as the baseline. This has various benefits:<o:p></o:p></p></blockquote><p class=MsoNormal><br>Rephrasing Gijs’ note, there’s a couple of questions we should answer separately:<br><br>* Is this the easiest and best way to maintain these two platforms?<br><br>I think this is a clear yes, and this is more or less where we started in the mists of time, we only diverged significantly later on when we moved to a “native” icon set through GTK theming. That design is in the past now, so undoing the divergence seems to make sense.<br><br>* Would the result be considered “good enough” from a UX/visual perspective? (A question I’d like UX and Horlander to answer, ideally)<br><br>Honestly, I agree it’d probably look fine, and I’d argue that as long as we respect theming (i.e. colours and fonts) on the key platforms, we’re doing well for those users. Any marginal benefit we’re getting seems significantly outweighed by the marginal cost.<br><br>— Mike<o:p></o:p></p></blockquote></div><p class=MsoNormal><o:p> </o:p></p></div></body></html>