Problems in KWayland causes by API and ABI compatibility promises

Aleix Pol aleixpol at kde.org
Wed Apr 1 13:55:45 BST 2020


FWIW I ported KDE Connect away from it here:
https://invent.kde.org/kde/kdeconnect-kde/-/merge_requests/199

Leaving the rest as plasma-specific components.

Aleix

On Wed, Apr 1, 2020 at 2:04 PM David Edmundson
<david at davidedmundson.co.uk> wrote:
>
> Here is a list of active uses of the KWayland::Client API.
>
> frameworks
>     plasma-framework (for window positioning)
>
> apps:
>     spectacle (for window positioning)
>     kdeconnect-kde  (for fake input)
>     yakuake (for window positioning)
>
> extragear
>     latte-dock (for window positioning, custom shadow (which could be
> ported already) and windowmanagement)
>
> workspace:
>     kwin unit tests
>     libkscreen
>     breeze (till Qt5.15)
>     oxyen (till Qt5.15)
>     xdg-desktop-portal
>     kinfocenter
>     plasma-workspace
>     plasma-nano
>     kscreenlocker
>     powerdevil
>     kwayland-integration (the backend for kwindowsystem)
>     plasma-phone-components
>     plasma-integration
>
> David


More information about the Kde-frameworks-devel mailing list