Code review comment for lp:~vanvugt/mir/managed-surface

It may work well for WM policy affecting only a single surface (e.g. minimize, maximize, etc) but for things that involve state(s) to be applied across a number of surfaces, I imagine there will have to be an encompassing "coordinator" object to oversee the policy is enforced.

I can see the ManagedSurface class morphing into that in the future. Of course, the name would have to change and it should no longer inherit from ms::surface.

I guess my question is how would then a policy involving multiple windows/surfaces be enforced with this approach?