[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-frameworks-devel
Subject: Re: Problems in KWayland causes by API and ABI compatibility promises
From: Aleix Pol <aleixpol () kde ! org>
Date: 2020-04-01 12:55:45
Message-ID: CACcA1RrLW5cGm5CFpHw50UAs18U2db5ZvZWFaTScwEPrVw6ZpQ () mail ! gmail ! com
[Download RAW message or body]
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@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
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic