<div dir="ltr"><div>The 3 platform themes do seem to be more varied than we'd like. My personal proposal would be to unify the sizing and structure of elements in shared. Then add visual styling in the individual theme folders.<br>
<br></div><div>For example, if you were to change the size of the navigation toolbar as it is now, it would have to be done in 3 different stylesheets in 3 different selectors. Some platforms have padding on it and others have the elements (toolbar buttons) stretch.<br>
</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Mar 26, 2014 at 10:43 AM, Mike de Boer <span dir="ltr"><<a href="mailto:mdeboer@mozilla.com" target="_blank">mdeboer@mozilla.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div>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…</div>
<div><br></div><div>Allow me to try with a little schematics:</div><div><br></div><div><font face="Courier New"> Themes</font></div><div><font face="Courier New"> —> Shared</font></div><div><font face="Courier New"> —> OSX</font></div>
<div><font face="Courier New"> —> WinLin</font></div><div><font face="Courier New"> —> Windows</font></div><div><font face="Courier New"> —> Aero</font></div><div><font face="Courier New"> —> XP</font></div>
<div><font face="Courier New"> —> Linux</font></div><div><br></div><div>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.</div>
<div><br></div><div>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.</div>
<div><br></div><div>I hope this adds the necessary context to my message.</div><span class="HOEnZb"><font color="#888888"><div><br></div><div>Mike.</div></font></span><div class=""><br><div><div>On 26 Mar 2014, at 15:14, Mike Connor <<a href="mailto:mconnor@mozilla.com" target="_blank">mconnor@mozilla.com</a>> wrote:</div>
<br><blockquote type="cite"><br>On Mar 26, 2014, at 8:19 AM, Mike de Boer <<a href="mailto:mdeboer@mozilla.com" target="_blank">mdeboer@mozilla.com</a>> wrote:<br><br><blockquote type="cite">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:<br>
</blockquote><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</blockquote></div><br></div></div><br>_______________________________________________<br>
firefox-dev mailing list<br>
<a href="mailto:firefox-dev@mozilla.org">firefox-dev@mozilla.org</a><br>
<a href="https://mail.mozilla.org/listinfo/firefox-dev" target="_blank">https://mail.mozilla.org/listinfo/firefox-dev</a><br>
<br></blockquote></div><br></div>