| KWin |
This lifts the enablement code for outputs from the DRM backend to Platform
allowing other Wayland backends in the future to use this interface as well.
To do that we also create some helper functions on Platform level and have to
spill some KWayland classes into AbstractOutput what motivates a further split
of Platform into a Wayland child class like for AbstractOutput.
Disabled and enabled an output in DRM session.
| Lint OK |
| No Unit Test Coverage |
| Buildable 15820 | |
| Build 15838: arc lint + arc unit |
How much code do we need to share between all platforms?
I don't like that AbstractOutput now contains wayland stuff. What's the different between AbstractOutput and AbstractWaylandOutput?
Depends on what functionality we want to share between multiple platforms. For Wayland session platforms I assume all of it since we want to at least test it with the virtual backend.
I don't like that AbstractOutput now contains wayland stuff. What's the different between AbstractOutput and AbstractWaylandOutput?
For that we need a Wayland session child class of Platform as with AbstractOutput and AbstractWaylandOutput. One argument for this is that AbstractOutput is on the same level as Platform although Platform contains some Wayland bits.