If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
No announcement yet.
LightDM Caught Off-Guard By Mir, Plans For Wayland
Ok so from what I gather it looks something like this (please correct me if I'm wrong about any of this):
+ Wayland system compositor
+--- Splash screen
+--- Display manager
+--+ Wayland compositor
Wayland is the standard that defines how these parts interact. The implementation of these different parts can vary. The system compositor can be the default reference implementation or something else. The display manager can be LightDM, GDM, KDM or something else. The Wayland compositor can be Weston or something else.
The system compositor is at the bottom of the stack, and basically doesn't do any actual compositing per se, it just switches inputs between splash screen, display manager and the actual compositor. The actual compositor (Weston or equivalent) works as the window manager, on top of which all the applications run.
So the display manager is still needed to show the login screen, ask for username/password, and choose the session type. Then it basically just gets out of way and the actual compositor takes over.
If I understand it correct? The guy has in the last half a year written a qt library for lightdm (a Canonical project) to use with kde. He do this because he expect Canonical to develop the wayland backend to lightdm.
Instead Canonical switch to MIR and UNITY next. The result canonical use his qt library for Unity next but do not support the wayland port. So he gave Canonical a half a year work with the qt support but can as it's now not use it himself? At least if he don't also do the wayland port?
Of course he can use it himself. If it's under GPL, he just has to fork his own project, so that it stays under GPL. A GPL-licensed software cannot be fully closed - if Canonical owns the copyright to it, they can only "close" it so that the next version they release would be proprietary, but the last GPL-released version would still be under GPL and anyone can fork or use it under GPL.
The GPL is designed specifically to prevent the code being closed. So anyone can use it as long as they keep it under GPL - no matter who "owns" the code.