RFC Evolving Mir support for writing shells

[Alan Griffiths]

Hi,

I've been spiking replacing DefaultWindowManager with the "Canonical"
one from examples (and discovered a number of tests make implicit
assumptions about the default window management policy). But I'm
wondering what the right end-state is:

    1. Should a shell::BasicWindowManager template be public, supported
    and used by examples? Or should it be private and copy exist in
    examples?

    2. Should shell::CanonicalWindowManagerPolicy just be a "snapshot"
    of example::CanonicalWindowManagerPolicy which could remain for
    experimentation or should the code move?

    3. We have some tests and playground that are coupled to the
    PlacementStrategy & SurfaceConfigurator used with
    DefaultWindowManager but I don't think these configuration points
    are needed downstream. Are we happy to "unpublish" them (for now)
    but keep them to support the legacy code in tests and playground?

Opinions?

Thanks in advance,
Alan

PS If you want to look at the spike it is here:

   
https://code.launchpad.net/~alan-griffiths/mir/spike-using-camonical-window-manager/+merge/253653

NB I won't be MPing it in this form. The main point of interest is the
test changes  - the rest is dependent upon the above discussion.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/mir-devel/attachments/20150320/b459618b/attachment.html>