Naming convention: pixel_format_array => PixelFormatArray (PixelFormats is probably better)
~~~~
88 + for(auto const& f : availableFormats )
Whitespace. Vis:
for (auto const& f : availableFormats)
~~~~
It seems odd to be adding OutputConfiguration as a parameter to create_display() when it is only relevant to NestedPlatform. Why not make it a dependency of NestedPlatform and supply it to the constructor?
5 add_executable( mir_demo_ server_ shell placement_ strategy. h placement_ strategy. cpp outputs. h outputs. cpp configuration. h configuration. cpp
6 demo_shell.cpp
7 + fullscreen_
8 fullscreen_
9 + translucent_
10 + translucent_
11 + window_manager.h
12 window_manager.cpp
13 + ../server_
14 ../server_
15 )
Don't add header files to the sources.
~~~~
86 +MirPixelFormat TranslucentOutp uts::get_ pixel_format( pixel_format_ array const& availableFormats)
Naming convention: availableFormats => available_formats
~~~~
196 + typedef std::vector< MirPixelFormat> pixel_format_array;
Naming convention: pixel_format_array => PixelFormatArray (PixelFormats is probably better)
~~~~
88 + for(auto const& f : availableFormats )
Whitespace. Vis:
for (auto const& f : availableFormats)
~~~~
It seems odd to be adding OutputConfiguration as a parameter to create_display() when it is only relevant to NestedPlatform. Why not make it a dependency of NestedPlatform and supply it to the constructor?
~~~~
198 + virtual MirPixelFormat get_pixel_ format( pixel_format_ array const& availableFormats) = 0;
"get_" lacks semantic content. Perhaps "choose_"?