Re: [gtk-list] Re: WM hints interface

[Marko Macek <Marko Macek snet fri uni-lj si>]

raster@redhat.com wrote:
> even thoogh the ICCCM specs say it must be of the default visual - there
> is no good reason for  a programs icon window to not be on any visual. S
> window of any visual canbe reparented to a parent of a different
> visual. If you want a color icon, use an icon_window. Using a pimap
> will mena you violate the ICCCM standards - having a multi-depth pixmap
> here woudl break WM's if they aren't wirtten to be very robust and
> check pixmap depth becuase ICCCM allows them to ASSUME 1-bit deep icon
> pixmaps.

I agree with all of the above mentioned (ICCCM suggests but does not
specify
that icon windows should use the default visual). Also using color
icon/mask
pairs is not ICCCM compliant.

That is why I proposed the following extenstions (they should be easy to
support).

WIN_ICONS (on application window) contains pixmap,mask pairs. They can
be of
any size or depth. We should specify a list of suggested sizes/depths to
have
(like default depth and square icons with sizes 16,32,48).

WIN_ICON_SIZES (on root) a list of icons sizes (and possibly depths??)
that
window manager would like to have.
 
> WM_CLIENT_LEADER is not part of any ICCCM I know odf not in versiion
> 1.0 or 2.0 of ICCCM unless this is a motif hint?

It is part of session manager support. (page 49 on my .PS). Maybe using
it it is not such a good idea after all.

> What i woudl like is a canonical unambigous list of all the hints
> (motif included) ont eh cxlib level (ie atom names) and EXACTLY what is
> expected of these hints.

I agree. Making such a list would be very useful.

> ->  to that window. It's not supported by any wm I have seen (I will support
> ->  it  in icewm unless I find something is wrong with this).
> 
> if it wants a leader it should set the group XID to its own window Id
> (according to ICCCM) and all other windows int hat grup chocul set the
> XID to the leader window ID - according to ICCCM. If it is not doing
> this si it not conforming to ICCCM specs - which i spent the whole
> weekend reading over again - making E0.14 fully 100% ICCCM compliant.

I understand this. I am not sure if using WM_TRANSIENT on the group
leader
window should have the effect of having an group transient (instead of 
just window transient) window.
 
> ->  No. Most application provide an icon of some random size ;-)
> ->  Actually what is need is small/large icon size that depends on display
> ->  size. OS/2 does things this way (16/32 or 20/40).
> 
> the app should be able to provide an icon in ANY size form 1x1 to
> 1000x1000 or even bigger. The WM just has to set the size ranges it
> wants with the XA_WM_ICON_SIZE atom. the client, if ICCCM complient

I agree with the above. However, specifying an icon using an icon
window is not useful, because it can only be put in one place. My
wm always has at least two copies visible and can often have four
of them visible (app window, taskbar, window list and window menu).
It needs 16x16 icons to do this. For Alt+Tab (windows like switcher
between windows it would be nice to have 32x32 or 48x48 icons
displayed).

If applications provided more icon sizes, I could even have the default
icon
size changing with screen resolution. (I'm sure 16x16 is small on
1600x1200
and above). Scaling could be an option, but it produces ugly icons most
of
the time (same as scaling bitmapped fonts).

Mark
-- 
... MouseDevice "/dev/null"
--------_--------------------------------------------------------------
Marko.Macek@snet.fri.uni-lj.si      http://ixtas.fri.uni-lj.si/~markom/