Re: Various comments, mostly on Implementation Notes

[John Harper <john dcs warwick ac uk>]

Owen Taylor writes:
|> File Manager desktop
|> ...
|
|(It wasn't very accurate before, but since Nautilus is using the
|big-window model, I guess it is now accepted. There is a problem in
|that we need a way of marking a window unmoveable, currently, e.g.,
|alt-drag in Sawfish has the nice property of moving these windows...)

This was just sawfish not respecting the WIN_STATE_FIXED_POSITION flag.
I think that _NET_WM_WINDOW_TYPE_DESKTOP will imply immovability
without needing anything else


|> If the WM_TRANSIENT_FOR property is set to None or Root window, the
|> window should be treated as a transient for all other windows in the
|> same group. It has been noted that this is a slight ICCCM violation,
|> but as this behaviour is pretty standard for many toolkits and window
|> managers, and is extremely unlikely to break anything, it seems
|> reasonable to document it as standard.
|
|This is wrong. The "traditional" behavior was to decorate the window
|as if it was transient for another window, but not impose stacking
|order or other relationships commonly associated with the transient-for
|relation. Making it transient for the entire group breaks legacy
|apps. 

imho the WM_TRANSIENT_FOR hint should only be used for the
_non-decoration_ aspects of this. _NET_WM_WINDOW_TYPE_DIALOG seems
ideally suited for windows that just want to get a different
decoration. (Should the spec clarify exactly what TYPE_DIALOG means?)

(Actually, I'd rather that WM_TRANSIENT_FOR was restricted to being a
top-level window, not Root or None or anything else..)

	John