hicolor-icon-theme

[Jason W]

Thanks to bmarkus for:

Code: [Select]

Title:          hicolor-icon-theme.tcz
Description:    Default fallback theme
Version:        0.11
Author:         Various
Original-site:  http://icon-theme.freedesktop.org/releases/
Copying-policy: GPL v2
Size:           12k
Extension_by:   bmarkus
Comments:       Binaries only
                ----
                Compiled for TC2.x
                ----
                PPI compatible
Change-log:     ----
Current:        2009/11/23 First version


[Juanito]

Should this have shared-mime-info and gnome-icon-theme as deps, not much happens otherwise?

[curaga]

mime-info yeah, but the choice of an icon theme should be the user's..

[Arslan S.]

checked a few other distros hicolor-icon-theme does not have any dependencies

[bmarkus]

There is no need for any dependency.

[Juanito]

What I see is that apps like rhythmbox, blueman, bluez-gnome(?), etc will not display all of their icons unless hicolor-icon-theme, shared-mime-info and gnome-icon-theme (or equivalent) are present.

I suppose it could be said that shared-mime-info/gnome-icon-theme should be deps of rhythmbox/blueman, is that what you're suggesting?

[bmarkus]

What I see is that apps like rhythmbox, blueman, bluez-gnome(?), etc will not display all of their icons unless hicolor-icon-theme, shared-mime-info and gnome-icon-theme (or equivalent) are present.

I suppose it could be said that shared-mime-info/gnome-icon-theme should be deps of rhythmbox/blueman, is that what you're suggesting?

Yes,

shared-mime-info
hicolor-icon-theme

and a full icon theme, like gnome-icon-theme

must be added to the application's dep file as well as

librsvg

for scalable fonts. And don't forget .gtkrc-2.0 in /home/tc

See WIKI article http://wiki.tinycorelinux.com/tiki-index.php?page=GTK+themes

[Juanito]

I guess it comes down to a matter of opinion 

Rhythmbox, blueman, bluez-gnome, etc will all work without hicolor-icon-theme.

..but hicolor-icon-theme will not work without shared-mime-info/*-icon-theme

[bmarkus]

I guess it comes down to a matter of opinion 

Rhythmbox, blueman, bluez-gnome, etc will all work without hicolor-icon-theme.

..but hicolor-icon-theme will not work without shared-mime-info/*-icon-theme

hicolor-icon-theme is basically just a directory structure and alone does nothing. Both hicolor-icon-theme and shared-mime-imfo is used by the GTK+ theme engine. My advice elave dependencies as it is now.

[jur]

I guess it comes down to a matter of opinion 

Rhythmbox, blueman, bluez-gnome, etc will all work without hicolor-icon-theme.

..but hicolor-icon-theme will not work without shared-mime-info/*-icon-theme

I am having trouble with blueman's display of icons... most of the time I get a default not found type of icon, a white sheet with a red X. I haven't been able to find a foolproof way of making it display properly. hicolor and mime-info alone don't seem to work and without those it's also lost.

[Juanito]

I am having trouble with blueman's display of icons... most of the time I get a default not found type of icon, a white sheet with a red X. I haven't been able to find a foolproof way of making it display properly. hicolor and mime-info alone don't seem to work and without those it's also lost.

You need hicolor-icon-theme, shared-mime-info and gnome-icon-theme (or equivalent to gnome-icon-theme) and then the blueman icons will display properly.

[maro]

Whilst doing something else I stumbled over the startup file of 'hicolor-icon-theme.tcz' and was wondering what might be the reason for such a long list of commands.

Would it not make more sense to use a loop like
    grep '^Directories=' /usr/local/share/icons/hicolor/index.theme \
                    | sed -e 's#^Directories=##' | tr ',' '\n' \
                    | grep -v '^256x256/' | while read DIR ; do
            [ -e /usr/local/share/icons/hicolor/${DIR} ] \
                    || mkdir -p /usr/local/share/icons/hicolor/${DIR}
    done
Please note that I've tried to mimic the current behavior that does not create a '256x256' directory structure. Judging by the content of the .list files only very few icons for that resolution seem to exist.

Surely this is just a purely cosmetic suggestion and does as such offer no "real" improvement. I was just surprised by the length of the startup file and thought "gee, I wonder what's going on in there" ...

[bmarkus]

...
Surely this is just a purely cosmetic suggestion and does as such offer no "real" improvement. I was just surprised by the length of the startup file and thought "gee, I wonder what's going on in there" ...

Maro

thanks for the script. What is there actually is a fast and dirty solution with copy/paste. Your script is really nice and clever (BTW, did yout try ?).

There is a new upstream version out. I will consider to use your solution in the updated extension.

[maro]

bmarkus: I did some limited testing. By enclosing the content of the loop with "echo" I produced an output that I compared (in it's sorted form) against the (sorted version of the) current script. That way I realized the absence of the '256x256' directory structure. The only other difference I saw were additional parent directories in the current script, but those should be taken care of by the '-p' option of 'mkdir'.

Obviously that is no "absolute proof", but it was enough for me to have the confidence to post it.

[bmarkus]

maro@

I updated extension to 0.12 and replaced startup script with your. It works fine. I let it make 256x256 dir as well, it is the only modification done.

Thanks again!