Due to all the discussion about buttons and the various opinions on what looks best, i'm thinking it might be nice to allow customization for such an item that is so visible to the user. <div><br></div><div>Attached is a mockup. This would allow the user to preview installed button themes, and if decided upon, maybe even offer a way to get new themes, install themes, or remove unwanted themes. </div>
<div><br></div><div>Shipping a few button themes would allow some customization while maintaining a standard for button theme construction. If this were the case, it would probably be best to provide a single button svg for each theme instead of including each with the default theme file. </div>
<div><br></div><div>Perhaps if a standard for button theme construction is clearly defined, custom themes wouldn't be as much of an issue, and would provide the user a bit more flexibility for customization if they do decide to create a custom theme (and maybe even share it). </div>
<div><br></div><div>This same idea could probably be extended to color schemes, allowing the user to preview what a dark, light, or defined color scheme would look like before applying it.</div><div><br></div><div>If a hand-full of good button themes / color schemes are already provided, that should eliminate most of the need for users to create their own themes.</div>
<div><br></div><div>- Lee </div><div><br><div class="gmail_quote">On Fri, Oct 30, 2009 at 2:26 PM, Thomas Pfeiffer <span dir="ltr"><<a href="mailto:colomar@autistici.org">colomar@autistici.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">> > The svg file can be edited, and that controls most of the theme.<br>
> > Amarok is fairly styleable already, we just don't advertise it because<br>
> > we don't want to support the results.<br>
><br>
</div>Hm ok. Then maybe we'd have to find a way to allow relatively safe<br>
customization. Some themes could be provided by the team (which would then be<br>
supported), and others could be contributed via GHNS. And you don't offer full<br>
support for GHNS-stuff anyway, do you?<br>
<br>
I think providing maybe two or three skins (a rather plain default skin that<br>
goes well with the standard KDE look plus maybe two fancy ones, one dark and<br>
one light) packaged directly with Amarok would suffice. Others could be<br>
contributed via GHNS (if at all).<br>
<div class="im"><br>
> Thanks Dan for summing this up concisely. One note to all<br>
> contributors: Please try to keep your mails short and to the point.<br>
><br>
> For a variety of reasons some of us (including me) cannot or do not<br>
> want to read overly long mails. Keep it short and sweet, and<br>
> structured with paragraphs. Thanks :)<br>
><br>
</div>Ok, will do. Hope this one is short enough.<br>
<br>
Regards,<br>
<font color="#888888">Thomas<br>
</font><div><div></div><div class="h5">_______________________________________________<br>
Amarok-devel mailing list<br>
<a href="mailto:Amarok-devel@kde.org">Amarok-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/amarok-devel" target="_blank">https://mail.kde.org/mailman/listinfo/amarok-devel</a><br>
</div></div></blockquote></div><br></div>