Nov 11 2023
Nov 5 2021
This is marked as resolved but I would also like to be looped in on how the mapping tablets to outputs effort goes as I am writing user-space drivers for a few tablets that get picked up by libinput.
Oct 29 2021
- per-display
- KWin needs to support color management
- WIP color-management-unstable protocol: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/14
- colord is already used to upload calibration curves.
- colord-kde kcm needs working on, it should be able to callibrate displays too. See displaycal.
- HDR: yes, please. See https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/14
Oct 25 2021
+1 please ping me, I'll be around.
I will be joining too. I used to work under wayland, with a functional Gnome 3 environment before migrating to KDE Plasma. I also worked with Linux Wacom project on some tricky bugs so I might be able to provide some useful info.
Thank you for starting this thread.
Jun 11 2021
Mar 30 2021
Mar 8 2021
Dec 18 2020
Not a revert but rather rollback of SNI part:
https://invent.kde.org/plasma/kwin/-/merge_requests/560
We are going to revert this in favor of https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/181:
it supports all the existing functional here plus missing one (problem with short layout names was solved):
- flags and/or short text for the layouts
If any objections, please tell.
Dec 10 2020
Oct 29 2020
see generic point
Is there a way to implement an "emulation" for applications that don't explicit support said back functionality?
Alright some notes from discussions:
There are 2 ways we can approach this: generic (sending mouse back events) and powerful (have a dedicated API for it)
There are pros and cons to each method
Generic:
- Pros: simple, doesn't require anything from app developers
- Cons: not extensible, won't work consistently with different apps, could lead to a poor experience nullifying the point
Powerful(API):
- Pros: Extensible, reliable, consistent
- Cons: Requires an implementation from developers (although gives users a good experience), not all apps will be supported
Aug 10 2020
Jun 3 2020
May 27 2020
Great. Thanks for the follow up.
I am. Patch is complete will upload soon.
For the record, here is a link to the protocol in Qt 5.15 documentation :
https://doc.qt.io/qt-5/qtwaylandcompositor-attribution-wayland-primary-selection-protocol.html
May 25 2020
The biggest problem with sharing the dmabuf buffers it that its memory management becomes quite complex (and I'm unsure it's really doable).
PipeWire has mechanisms to create the buffers it's going to need, juggling this with passing the buffer from the app/output and making sure it stays relevant feels messy and error-prone.
Copying from dmabuf->dmabuf shouldn't be very expensive though, as it shouldn't go through the buses (AFAIK, that is).
May 12 2020
Oh, that's a good compromise given I'll want it anyway.
I wouldn't have a big problem with merging as is, it could make sense to have QFuture<QVariant> retrieveData as is. It would make it easier to time out when a client is being shitty and would allow to parallelize different queries.
That's now all done. Pending merge after 5.19 forks.
May 7 2020
BTW, GDM seems already run so :)
It's also worth to have a look at libweston/input.c.
May 4 2020
May 1 2020
Apr 29 2020
Sure, but this is not what this ticket is about.
There's the org.kde.plasma.colorpicker that does this.
Apr 27 2020
The hard part is the seat handling.