Thank you for starting this thread.

I'll join the meeting, I also use Plasma for digital painting my webcomic, Pepper&Carrot.

I blog-post install guides about it. But I rarely practised the Wayland territory (for a "lack of features" reason, and technical issues). So, it sounds perfect.

Note that neither @rempt nor @dkazakov are available this week. However, given that both are a little preoccupied with getting Krita 5 ready, perhaps it would be most fruitful to currently have a discussion with artists and discuss what kind of setups and needs they have, before discussing tech...

In T14971#265318, @woltherav wrote:

Note that neither @rempt nor @dkazakov are available this week. However, given that both are a little preoccupied with getting Krita 5 ready, perhaps it would be most fruitful to currently have a discussion with artists and discuss what kind of setups and needs they have, before discussing tech...

I feel like there are many things missing on wayland verses xorg. So we'll have to figure out what is missing, and what has working on going. Also what artists expected to have. That's the intention of the meeting.

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.

+1 please ping me, I'll be around.

I did our current KWin Wayland implementation for drawing tablets.

Conclusion:

colors/icc

• 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

tablet kcm that allows:

• button mapping to states (i.e. making some buttons responsible for toggling a tool's type, not letting these button events reach clients)
• mapping tablets to outputs
• calibration of tablets into outputs

Others

• allow higher brightness on active monitor

@apol will work on a new kcm in wayland to replace wacomtablet-kcm.
@hanyoung will ensure colord-kde works under wayland

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.