In message <[email protected]>,
Chris Siebenmann <[email protected]> wrote:
> The bad news is that modern EWMH X programs generally don't supply
>their icons as files in the filesystem; instead, they provide multiple
>sizes of icons as X properties, which you can usually see by using
>'xprop' on a suitable window (it's all of the _NET_WM_ICON stuff, and
>I think the WM_HINTS stuff, although I don't know how the bitmap ids
>are used).
Thanks much. I really -am- just to dumb end-luser, and thus didn't even
know about xprop until just now.
But I ran it on (non-minimized) Firefox and Opera browser windows on my
system of interest and it appears that Opera only offers up a single 48x48
icon, whereas Firefox now offers all of: 16x16, 32x32, 48x48, 64x64, and
128x128 versions.
Strangely, the output of xprop executed on a Chrome{ium} browser window
-seems- to say to me that Chrom{ium} is only offering up a 128x128 icon
for itself, but when minimized, the icon displayed in actually way smaller
than that... somwhere between the 48x48 icon size used by Opera and what
I am just guessing is probably the somewhat larger 64x64 size used , at
present, for Firefox.
I just mention this because it appears to me that in that (Chrom{ium}) case,
someboyd may be doing some sort of scaling or something.
So, anyuway, what I want is for Fvwm to be using the 48x48 icon for its
representation of a minimized Firefox window.
Surely there -must- be -some- way to force that, no?
>If you want to see what size of icon fvwm is using for some
>window, you can use 'xwininfo' on the icon; this will tell you the
>icon's Width and Height.
Thanks. Yet another thing I learned today.
>The actual source PNGs for these Firefox icons are present in the
>source code but are magically bundled into the compiled and installed
>Firefox.
I guess that me offering this observation is rather pointless, but I'll
offer it anyway: This choice, to embed the icons into the compailed
binaries, is, in my humble opinion, of debatable merit.
I know. I know. If I want to grouse about -that- questionable design
decision, then I'm in the entirely Wrong Place for doing so. (If I get
motivated, I'll register my opinion on this topic elsewhere.)
>Never the less you can simply pull the PNGs out of the source
>code, once you know the magical location. Probably the simplest way is
>through the Github Firefox mirror, where I believe you can find all of
>the sizes in the default*.pngs here:
>
>https://github.com/mozilla/gecko-dev/tree/master/browser/branding/official
OK, I -think- I understand what you are suggesting. I'd basically be
telling/forcing Fvwm to override the icon size choice it is currently
making in the case of Firefox. And I'd be doing it by forcing Fvwm to
use a .png of my choosing... which is exactly the kind of localized hack
that I myself had suggested earlier. But please answer me this: Why
should I even have to go through all this if the Firefox binary that
I'm using already has an built-in/compiled-in 48x48 icon? Why can't
I just tell Fvwm that my first preference for icon sizes in 48x48 in
all cases?
>So, basically, you probably want to use xwininfo on an Opera icon to
>find out how big it is, then download the appropriate sized defaultNN.png
>file and set it as Firefox's icon. This will override anything Firefox
>is hinting to fvwm and fvwm is picking up on.
See above. I'm still perplexed as to why I even need to resort to such a
hack.
And BTW, who or what is doing the apparent scaling on the Chromium icon?
Maybe I just need to get that thing working on my side, eh?
