🚀 go-pugleaf

Excerpts from mail: 23-Feb-90 icon-groups & iconification.. Colas
Nahaboo@mirsa.inri (503)

> > Consider
> > an editor, for example, which opens multiple top-level windows.  All of
> > those windows are now perforce in the same window group, but it would
> > probably not be proper behaviour to iconify and deiconify them in a group.

> Well, in gwm by loading the "icon-groups" package, you iconify the 
> whole group by iconifying the leader. (if you iconify a member, only this
> one is iconified.) It is a very primitive feature, but I use it all the time
> with xmh and epoch, and find it very useful!!!

Yep -- if the leader is accessible.  One toolkit I use creates 1x1 group
leaders that are never mapped for the sole purpose of placing the
WM_COMMAND and WM_CLIENT_MACHINE properties.  One possibility would be
to put some property on the leader if group iconification is desired (or
not desired).  For example, group iconification is desired if the
property WM_GROUP_ICONIFY is defined on the group leader of the window
group, whether or not the group leader is mapped.  Or the
WM_GROUP_ICONIFY property could be placed on individual top-level
windows of the group, signifying that iconifying this window should
iconify all windows in the group, but other top-level windows in the
group without the property should be iconified individually.  I guess
I'm not saying that window groups are never useful for group
iconification, but that we need extra mechanism to avoid interacting
wrongly with the other defined use of window groups.

Bill