DisplayChanger customization point

[Daniel van Vugt]

I'm not convinced *DisplayChanger are good abstractions. If you're 
touching them then maybe we can think of a cleaner way to approach the 
task of changing displays :)

http://objology.blogspot.com.au/2011/09/one-of-best-bits-of-programming-advice.html
http://www.benhallbenhall.com/2013/01/naming-objects-er-object-names/

Or if unused then remove even...

On 20/11/14 23:50, Alan Griffiths wrote:
> As part of the mir::Server API migration I'm looking at some acceptance
> tests that customize the [frontend]DisplayChanger.
>
> Now, with the phone we've not got any downstreams that use this
> customization so it is currently hidden.
>
> But I think it is needed for desktop and that the customization point
> should really support the mir::DisplayChanger.
>
> So my thinking is:
>
> 1. Introduce shell { class DisplayChanger : public
> frontend::DisplayChanger, mir::DisplayChanger {}; }
>
> 2. Now have MediatingDisplayChanger : public shell::DisplayChanger
>
> 3. provide a mir::Server customization point wrap_display_changer() ->
> shell::DisplayChanger
>
> Does that make sense?
>