Στις 23/02/2014 12:38 πμ, ο/η alx έγραψε: > Antonis Tsolomitis wrote: >> Στις 22/02/2014 04:58 μμ, ο/η alx έγραψε: >>> Antonis Tsolomitis wrote: >>>> >>>> An iconified application uses an icon that according to the >>>> advanced CDE >>>> user's guide >>>> can be set with >>>> >>>> Dtwm*clientname*iconImage: /path/to/image/file >>>> >>>> This seems not to work with most non-CDE applications. >>>> >>>> To get the clientname one uses xprop to find the window WM_CLASS >>>> >>>> Firefox for example, sets its WM_CLASS to "Navigator" and to >>>> "Firefox": >>>> >>>> [atsol@callisto ~]$ xprop | grep WM_CLASS >>>> WM_CLASS(STRING) = "Navigator", "Firefox" >>>> [atsol@callisto ~]$ >>>> >>>> So a line in .Xdefaults or .Xresources like >>>> >>>> Dtwm*Navigator*iconImage: /path/to/image/firefox.l.pm >>>> >>>> ought to work. Same with this line >>>> >>>> Dtwm*Firefox*iconImage: firefox >>>> >>>> with firefox.l.pm, firefox.m.pm and firefox.t.pm copied to >>>> $HOME/.dt/icons/ >>>> >>>> ------------------------- >>>> >>>> The reason I am looking into this is that new applications get a tiny >>>> icon when they get iconified instead of a large >>>> icon that CDE apps get. This is not a Firefox bug. The same happens >>>> with >>>> thunderbird, libreoffice, gimp and many others. >>>> All of them get tiny icons instead of large ones (48x48). >>>> >>>> Icons for these apps can be found in my desktop_approots.tgz from my >>>> page: >>>> http://myria.math.aegean.gr/~atsol/newpage-en/software/cde/ >>>> <http://myria.math.aegean.gr/%7Eatsol/newpage-en/software/cde/> >>>> >>>> Antonis. >>>> >>>> >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> >>>> >>>> Managing the Performance of Cloud-Based Applications >>>> Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. >>>> Read the Whitepaper. >>>> http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk >>>> >>>> >>>> _______________________________________________ >>>> cdesktopenv-devel mailing list >>>> cdesktopenv-devel@lists.sourceforge.net >>>> https://lists.sourceforge.net/lists/listinfo/cdesktopenv-devel >>>> >>> The problem with this is that applications can override (hardcode) the >>> icon resource. Native CDE apps do not, but anything GTK/Qt based >>> almost certainly will. >> >> Thanks for this information. >> >> Hmmm..., OK I understand. But still, the desktop is managed by dtwm and >> not by firefox. So dtwm must >> have a way to override this. It is dtwm that draws the minimized window. >> It asks for the resources and you rightly say >> that firefox give something bad. OK, then dtwm must be able to ignore >> whatever the app wants >> if a user or root insists on his own. >> >> Antonis. >> >> > > Technically, dtwm's behavior is correct. ICCCM specification states > that if the client sets the icon pixmap, window manager is expected to > display it. And while applications are encouraged to obtain > appropriate icon size from WM hints, and supply matching pixmap, they > are not required to do so. > I see your point, and the fact that not many app > developers/maintainers would worry about aesthetics on anything other > than GNOME/KDE in the near future, but...
I am not convinced that this is surely the issue. How do you explain that a firefox installation comes only with one icon, namely mozicon128.png, which is an 128x128 icon? But the icon of firefox when minimized is 16x16. Antonis. ------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk _______________________________________________ cdesktopenv-devel mailing list cdesktopenv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cdesktopenv-devel
