>> Sound potentially useful, but I'm not sure what a good UI for that would
>> look like.
> The only UIs needed is a menu of known tags + possibility to add new
> ones (something as simple as the workspace rename feature might be enough.)
Looking forward to using it ;-)
>> Along the same lines, a window that's in screen 0 could only belong to
>> workspaces of screen 0 and not to workspaces of other screens (so
>> there's never a situation where you might need to display a given window
>> at two different places at the same time). Of course, displaying
>> a given window at several places at the same time might be reasonably
>> easy to do by "compositing" but I don't know if anyone is up to making
>> ctwm do it.
> It would complicates the code a level more.
Could be. I was thinking that maybe it can be made fairly simply: when
you select workspace W in screen S, the only change is to skip (leave
alone) all the windows that are not in screen S.
> We can not dissociate screens as you describe without facing problems.
> As if a window has its left part on first screen and its right one on
> the second screen, what should happen ?
We already have the notion of "this window is in screen S" for example
when you do a fullzoom (or when you choose where to place the aux
information box while moving/resizing), so we'd use the same notion.
Stefan
