[Digikam-devel] KDE SC 4.8 release, Oxygen icons and official digiKam icon

[Paristo]

On 13 January 2012 11:07, Martin Klapetek <martin.klapetek at gmail.com> wrote:

> On Fri, Jan 13, 2012 at 07:06, Gilles Caulier <caulier.gilles at gmail.com>wrote:
>
>> i totally agree with your viewpoint. digiKam icon must be hosted by
>> the project as well. I don't know why Oxygen team whant to force to
>> use Oxgen application icon if project one  is enough. Why to waste
>> time for that ???
>>
>
> In the worst case, you can always simply install your own icon, you can
> even overwrite the one in oxygen by a cmake icons install macro. Questions
> is how would the distributions deal with that..
>
>
The KDE application icons goes to
/usr/share/icons/<theme>/<size>/apps/<appname.png>

I have the understanding that digiKam itself adds own icons there as well.
But it has not been at least on my two computer so for some time when
Oxygen new icon has been. I have even done myself that I copy the icons
manually after KDE or digikam update to /usr/share/icons/oxygen/ with
correct way but still digiKam icon does not get changed in KickOff but it
use the Oxygen version. I have tried to track that icon going trough all
oxygen icons visually and checking KickOff configuration for digiKam entry
data what points to correct location. I have started to think that I have
missed somekind icon cache. As even when I create a new user, the Oxygen
version is used, instead digiKam own.

I have as well tested two different LiveCD distributions by installing a
digikam in them and even then Oxygen version is used instead digiKam own.

The solution for problem is not just that we could overwrite digiKam icon
over Oxygen version, but that the Oxygen icon theme is used in many others
as well, and when there is wrong icon named as "digikam.png" it is already
doing its damage as it is then used in different purposes. So when people
tie the Oxygen version to digiKam, it is not good for digiKam brand.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-devel/attachments/20120113/37cb5ff0/attachment.html>