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

* You can't call a_scene_surface->some_method() and accidentally bypass the management policy.

Hmm true...

 * Any surface functionality can be modified by the shell in future this way.

Kind of a blessing and a curse on this one though right? in the sense that total flexibility means you provide nothing.

 * Any surface metadata can be neatly attached to a surface instance by the shell, without touching the core BasicSurface. e.g. the restore location and soon a lot more like decoration state, minimize location, animation state etc.

This could be solved by association...

I'll investigate your states branch though...still yet to form a full opinion.