[kde-artists] Icon naming issue

James Richard Tyrer tyrerj at acm.org
Fri Apr 27 22:49:06 BST 2007


Kenneth Wimer wrote:
> On Thursday 26 April 2007 21:46:12 Kenneth Wimer wrote:
>> On Thursday 26 April 2007 21:20:06 Aaron J. Seigo wrote:
>>> On Thursday 26 April 2007, Urs Wolfer wrote:
>>>> On Wednesday 25 April 2007, Jonathan Riddell wrote:
>>>>> SVN commit 658018 by jriddell:
>>>>>
>>>>> Move icons to oxygen namespace
>>>> I'm not really happy with this solution. We move crystal (cr) icons to
>>>> the oxygen (ox) namespace. This way we make a mess. Artists have it
>>>> harder to see which icons do not work. If the icons are in cr or
>>>> highcolor (hi), they can just drop the icon folder and start an
>>>> application to see which icons are missing.
>>>>
>>>> My suggestions to sort out this problem:
>>>> * make Oxygen inherit from cr instead of hi (at least for the next
>>>> time)
>>> and of course, we can easily take this particular action as we get closer
>>> to the release. in the meantime having ?s for icons is suitable and helps
>>> point out what needs work where.
>>>
>>> mixing in non-oxy icons into oxy is a exactly what everyone involved has
>>> been hoping to avoid so we don't end up with a crystal-like madness of
>>> inconsistency.
>> PLEASE, PLEASE, PLEASE do not make oxygen inherit crystal. Aaron is
>> completely correct. In fact, we did this purposely this way. Change will
>> only make things more difficult.
> 
> To clarify this: oxygen should be set as default and should fallback to the 
> monochrome set. This way we can very easily see what needs to be done without 
> the backup set influencing our design ideas on oxygen.

Do you mean that this should be hard coded, or simply that: "inherits" 
should be set in the: "index.theme" file?

-- 
JRT
______________________________________________________________________________
kde-artists at kde.org |  https://mail.kde.org/mailman/listinfo/kde-artists




More information about the kde-core-devel mailing list