KDE Plasma Can Now Run On Wayland
An anonymous reader writes "With the upcoming KDE 4.11, there's an initial Wayland backend through the KWin manager. The author notes on his blog: 'Once the system is fully started you can just use it. If everything works fine, you should not even notice any difference, though there are still limitations, like only the three mouse buttons of my touchpad are supported ;-)'"
Predicates are great, they let you be right even though you're not.
E.G: "If everything works fine, you should not even notice any difference"
This is true, but it doesn't tell you whether or not you will notice any difference, it just gives you the predicate under which you will not but doesn't walk the walk of telling you it will work fine.
I should use this sig to advertise my book ISBN-13 : 978-1501515132.
That brings to mind some of the old SunOS and Ultrix workstations that we had in college, which had 3 mouse buttons. Somewhat wierd to handle, particularly when using the 4th finger to right click. Subsequent versions replaced the middle button w/ the mouse click of both left & right, but I'm sure that broke plenty of software that used a combination of left-middle or middle-right. Not to mention Ctrl-left-middle or Alt-right-middle or things like that.
TFA - so does KDE 4.10 already run on Wayland? Or will it be KDE 5.x? That thing seems to need Wayland as well - not just Plasma.
What is the point of developing software if it makes no difference?
The reason that there is no functional difference between this setup and a regular X11 setup is that KWin can't yet run as a Wayland compositor, because this support is a work in progress. The main difference from a technical standpoint is that X11 is not running as the root display server - KWin is running as a Wayland client rather than an X client. Weston, the reference Wayland server implementation, is being used as the system compositor and the root display server.
When KWin does get support for running as a Wayland compositor, there will be a real difference. Applications that can run as Wayland clients then be able to do so, and X11 clients will be handled using XWayland.
This is subtly different. In the scenario you describe, KWin was running as an X client using XWayland under Weston. In the KDE Wayland backend, KWin runs as a native Wayland client without the XWayland compatiblity layer.
Sure it is. KWin can run as a Wayland client instead of an X client now. That's a big deal, and it indicates concrete progress on the transition to full Wayland support in KDE. How is that not newsworthy?