[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:       Kevin Ottens <ervin () kde ! org>
Date:       2020-04-08 16:10:52
Message-ID: 1663139.ls6UR92QIY () wintermute
[Download RAW message or body]


Hello,

On Wednesday, 1 April 2020 14:04:10 CEST David Edmundson 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)

The part of the list above makes me wonder, shouldn't the window positioning 
and windowmanager features be on KWindowSystem?

I got no idea regarding kdeconnect-kde and the fake input...
 
> 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

I think the above is less of an issue, right? Because workspace would have a 
copy of KWayland which could be shared with whatever stability constraints 
needed.

Hope that helps. :-)

Regards.
-- 
Kevin Ottens, http://ervin.ipsquad.net

enioka Haute Couture - proud patron of KDE, https://hc.enioka.com/en
["signature.asc" (application/pgp-signature)]

[prev in list] [next in list] [prev in thread] [next in thread]