From kde-core-devel Thu Oct 31 14:51:18 2002 From: Antonio Larrosa =?iso-8859-15?q?Jim=E9nez?= Date: Thu, 31 Oct 2002 14:51:18 +0000 To: kde-core-devel Subject: Re: kdeartwork/IconThemes X-MARC-Message: https://marc.info/?l=kde-core-devel&m=103607592516140 El Jueves, 31 de Octubre de 2002 14:04, Stephan Binner escribi=F3: > On Thursday 31 October 2002 13:15, Antonio Larrosa Jim=E9nez wrote: > > Did you read any of my comments about icon themes and how they work? > > No, where? kde-core-devel? kde-artists? Don't expect me to read all > commits. Sorry, I tried to sent a Cc of the cvs commits were I said something=20 important to kde-core-devel, but it seems I forgot that one. > > > They should inherit from "hicolor" or "default" (they mean the same > > now). > > Why hard-code a fix for this when it can be corrected in these files? > We can fix it in those files, but not on every 3rd party icon theme (like=20 the ones at kde-look.org), which we definitely want to continue supporting= =20 (specially if the user already has it installed, as we don't want to break= =20 his configuration). Hicolor (or default) is just an "empty" icon theme (which is not selectable= =20 by the user) in which 3rd party apps should install their icons if they=20 want them to be available independently of the icon theme the user is=20 using. That way, we can even change again the default icon theme in the=20 future and 1) nothing will break and 2) we won't have to do as many=20 changes as we've had to do with the hicolor->crystalsvg change. Of course, apps can _in addition_ install icons to other icon themes (like= =20 kdeclassic, crystal, or ikons), but that's optional (unless the developers= =20 want their apps only to work ok when the user is using a given icon theme=20 :-) . Greetings, =2D- Antonio Larrosa Jimenez KDE core developer - larrosa@kde.org http://devel-home.kde.org/~larrosa/ Mejor leer algo en ingl=E9s que una adivinanza en espa=F1ol.