Re: Composite Manager Specs

On Sun, 2003-11-23 at 01:10, Keith Packard wrote:
> 
> I'm still not sure making them separate is the best plan in the long run. 
> Performance of everything *except* window manipulation seems pretty good 
> so far, and merging the compositing manager and window manager together 
> should fix that.
> 

I think the compositing manager will be *much* easier to do inside the
WM. I've written a WM and also libwnck which does WM-like stuff outside
the WM, so I have a fairly reasonable idea what's involved here.

> However, I can see value in semantic labeling of the window manager frames 
> for all kinds of things like screen readers and magnifiers.  Perhaps we 
> can start with some conventions for that and see where it leads us.  In 
> particular, it would be nice to know which windows are menus, which are 
> dialogs and which are just visual effects.  Might be nice to know which 
> window is currently active.  These semantics seem independent of the 
> separation of compositing from window management and yet could be useful 
> for that as well.

EWMH already has a lot of this.

Havoc