On Tue, Mar 17, 2020 at 11:27 AM David Edmundson
wrote:
>
> There's definitely a problem, and I think it's a lot more than just
> discussing location and protocol versions.
>
> My typical workflow is reading the wayland protocol in detail, and
> kwayland is in that awkward position where I absolut
There's definitely a problem, and I think it's a lot more than just
discussing location and protocol versions.
My typical workflow is reading the wayland protocol in detail, and
kwayland is in that awkward position where I absolutely still need to
read those underlying docs and the abstraction kwa
On 3/6/20 12:55 AM, Kai Uwe Broulik wrote:
Frameworks:
===
Looks like just Plasma Dialog in Plasma-Framework, for which I believe
KWayland was turned into a Framework to begin with.
Other:
==
- Spectacle
- Yakuake
- Latte Dock (presumably similar uses as plasmashell)
Some of
Am 05.03.20 um 17:27 schrieb Nate Graham:
What are the known users of KWayland outside of KWin? Are there any?
Quick lxr suggests there's actually a bunch:
In Plasma (for which we could do an "integration" library without
Frameworks guarantees in plasma-workspace, similar to e.g.
LibTaskMana
Moving it into KWin itself seems sane to me, on the surface. What are
the known users of KWayland outside of KWin? Are there any?
Nate
On 3/5/20 5:21 AM, Vlad Zahorodnii wrote:
Hi,
KWayland is a library that provides convenience wrappers for Wayland
protocols. Usually, when we want to impl
Hi,
KWayland is a library that provides convenience wrappers for Wayland
protocols. Usually, when we want to implement some Wayland protocol,
first, we add corresponding wrappers in KWayland and after that we
actually implement the protocol in KWin.
Unfortunately, we made a bad design choice
