Plasma Sprint discussion planning

[Martin Gräßlin]

Am 2017-01-13 16:27, schrieb Marco Martin:
>> 3. Maintaining X11 specific code:
>> Over the last half year exclusively on Wayland I realized that I 
>> cannot
>> maintain X11 specific code any more. KWin is mostly no problem as
>> XWayland windows are used the same way as native X windows. But things
>> which have a different implementation on Wayland I cannot maintain any
>> more. This affects mostly kglobalaccel, klipper and partly the
>> KWin-standalone platform. I want the team to think about plans how we
>> can continue to maintain the X11 specific parts especially with more 
>> of
>> the team (hopefully) moving to Wayland.
> 
> This is one of the most important things that have to be discussed at 
> the
> sprint, yes

Just giving an idea: Some parts where KWin is responsible for on 
Wayland, it could also become responsible on X11 and take over the part 
of whatever component provided it before. E.g. KWin could manage the 
keyboard layout on X11 as it has all the code for Wayland. The glue code 
on X11 would be rather minimal.

That's also what I want to focus on in KWin internally. My aim for 5.10 
is to replace more and more of the X11 specific code through the new 
implementations added for Wayland.

Cheers
Martin