ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput | register your nick to speak
pochu_ has joined #wayland
pochu has quit [Ping timeout: 480 seconds]
pochu has joined #wayland
pochu_ has quit [Ping timeout: 480 seconds]
fmuellner has quit [Ping timeout: 480 seconds]
columbarius has joined #wayland
co1umbarius has quit [Ping timeout: 480 seconds]
bluepenquin has joined #wayland
floof58 is now known as Guest1330
floof58 has joined #wayland
___nick___ has quit []
Guest1330 has quit [Ping timeout: 480 seconds]
___nick___ has joined #wayland
___nick___ has quit []
___nick___ has joined #wayland
smallville7123 has joined #wayland
Lyude has quit [Quit: Bouncer restarting]
Lyude has joined #wayland
Leopold_ has quit [Remote host closed the connection]
nerdopolis_ has quit [Ping timeout: 480 seconds]
mxz has quit [Quit: cya]
mxz has joined #wayland
zebrag has quit [Quit: Konversation terminated!]
smallville7123 is now known as Guest1340
smallville7123 has joined #wayland
Guest1340 has quit [Ping timeout: 480 seconds]
smallville7123 has quit [Ping timeout: 480 seconds]
smallville7123 has joined #wayland
smallville7123 has quit [Ping timeout: 480 seconds]
floof58 is now known as Guest1347
floof58 has joined #wayland
dcz_ has joined #wayland
Guest1347 has quit [Ping timeout: 480 seconds]
kts has joined #wayland
kts has quit [Quit: Leaving]
hardening has joined #wayland
kts has joined #wayland
tagr has joined #wayland
bodiccea has quit [Remote host closed the connection]
bodiccea has joined #wayland
smallville7123 has joined #wayland
junaid has joined #wayland
kts has quit [Quit: Leaving]
rasterman has joined #wayland
bodiccea has quit [Remote host closed the connection]
bodiccea has joined #wayland
bodiccea has quit [Remote host closed the connection]
bodiccea has joined #wayland
junaid has quit [Quit: leaving]
junaid has joined #wayland
kts has joined #wayland
junaid has quit [Quit: leaving]
junaid has joined #wayland
danvet has quit [Read error: Connection reset by peer]
bodiccea has quit [Remote host closed the connection]
bodiccea has joined #wayland
bodiccea has quit [Remote host closed the connection]
bodiccea has joined #wayland
bodiccea has quit [Remote host closed the connection]
bodiccea has joined #wayland
rasterman has quit [Quit: Gettin' stinky!]
kts has quit [Quit: Leaving]
SardemFF7 has quit [Remote host closed the connection]
SardemFF7 has joined #wayland
kts has joined #wayland
jmdaemon has quit [Ping timeout: 480 seconds]
junaid has quit [Ping timeout: 480 seconds]
SardemFF7 has quit [Remote host closed the connection]
junaid has joined #wayland
SardemFF7 has joined #wayland
junaid has quit [Ping timeout: 480 seconds]
danvet has joined #wayland
junaid has joined #wayland
Leopold_ has joined #wayland
Leopold_ has quit []
Leopold_ has joined #wayland
kts has quit [Quit: Leaving]
caveman has joined #wayland
cvmn has quit [Ping timeout: 480 seconds]
<ifreund>
DemiMarie: My Zig wayland-scanner already does a bit more advanced analysis than wayland-scanner, for example it enforces that the object creation hierarchy must be a tree
<ifreund>
(with exceptions for the forever v1 wl_callback and wl_buffer)
<ifreund>
this allows it to generate safer code with regards to protocol versioning and forwards compatibility
<ifreund>
the user must specify the version of each global interface they depend on at build time and the generated wl_registry_bind() call equivalents clamp to that version as a safeguard
kts has joined #wayland
nerdopolis has joined #wayland
<ifreund>
source-level forwards compatibility is also way easier as I can just not generated newer events/requests/interfaces than were requested at build time
Leopold_ has quit [Remote host closed the connection]
junaid has quit [Remote host closed the connection]
<emersion>
hm, not convinced it really buys a lot
<emersion>
clients generally support a range of versions
<ifreund>
To be clear, clients specifiy their maximum supported version at build time, they can still bind to older versions of the global if needed
Leopold_ has joined #wayland
Leopold_ has quit [Remote host closed the connection]
Leopold_ has joined #wayland
cvmn has joined #wayland
caveman has quit [Ping timeout: 480 seconds]
floof58 is now known as Guest1380
floof58 has joined #wayland
Guest1380 has quit [Ping timeout: 480 seconds]
smallville7123 has quit [Ping timeout: 480 seconds]
__nick__ has joined #wayland
___nick___ has quit [Ping timeout: 480 seconds]
Leopold_ has quit [Remote host closed the connection]
Leopold_ has joined #wayland
fmuellner has joined #wayland
nerdopolis has quit []
nerdopolis has joined #wayland
caveman has joined #wayland
cvmn has quit [Ping timeout: 480 seconds]
anomalous_creator[m] has quit []
Leopold_ has quit []
caveman has quit [Ping timeout: 480 seconds]
caveman has joined #wayland
caveman has quit [Remote host closed the connection]
caveman has joined #wayland
rgallaispou has joined #wayland
kts has quit [Quit: Leaving]
rgallaispou has quit [Read error: Connection reset by peer]
cvmn has joined #wayland
caveman has quit [Ping timeout: 480 seconds]
co1umbarius has joined #wayland
Leopold_ has joined #wayland
columbarius has quit [Ping timeout: 480 seconds]
Lyude has quit [Read error: Connection reset by peer]
cheako has joined #wayland
Lyude has joined #wayland
Leopold_ has quit [Remote host closed the connection]
<DemiMarie>
ifreund: that is absolutely awesome!
cvmn has quit []
caveman has joined #wayland
caveman has quit []
<DemiMarie>
emersion pq: what do you mean by using `drm_fourcc.h` instead of `wl_shm.format`? My understanding is that those are equivalent, except for `DRM_FORMAT_ARGB8888` and `DRM_FORMAT_XRGB8888`.
<emersion>
DemiMarie: yeah, because we made a mistake and fixed it later
<emersion>
wl_shm.format predates drm fourcc
<i509VCB>
I'm guessing we would use drm_fourcc directly because we never update the wl_shm.format enum either
<emersion>
drm_fourcc.h is a better source of canonical formats
<DemiMarie>
Can this switch be made while preserving the existing C API?
<DemiMarie>
emersion: you asked about implementations, and my answer is that my MR *is* the compositor-side implementation. That is a feature I want to preserve.
<emersion>
you need 2 more
Leopold_ has joined #wayland
<i509VCB>
emersion hopefully I don't sound like a broken record, would be nice if a wayland-protocols 1.28.1 release could be made with the content type protocol definition fix.
<DemiMarie>
emersion: it is the implementation for every compositor that uses libwayland-server’s `wl_shm` support.
<jadahl>
i509VCB: i can make such a thing tomorrow
<i509VCB>
Thank you jadahl in advance
<DemiMarie>
Compositors that use libwayland-server for `wl_shm` are not even aware that they now support v2, because libwayland-server handles it automatically.
<cheako>
I'm watching and planning my eventual forced transition, not trying to start a big argument but ppl act super passionate about the way things currently are. Is wine not using Xwayland? That's the application I use most often, and my perception is that it's being treated poorly with the architecture as is.
<i509VCB>
I think the rules still mention a client needs an implementation even if every server got it
<i509VCB>
I promised to implement the v2 wl_shm in smithay soon, just need to find time for it once I get the wayland-rs protocol bumps in
<i509VCB>
I can't recall of head, you defered V3 to a latter MR?
<DemiMarie>
i509VCB: Suggestions? Most clients use sealed memfds on Linux, and probably some emulation on non-Linux.
<DemiMarie>
i509VCB: Correct — I can’t make immediate use of it, and it requires non-trivial spec changes.
<DemiMarie>
i509VCB: Thank you.
<i509VCB>
If you were looking for a client, foot I believe already uses fixed size shm pools, so that night be a client to implement
<DemiMarie>
cheako: Wine still uses Xwayland but is working on changing IIRC.
<emersion>
DemiMarie: we don't count each compositor using wlroots' impl as an impl
<cheako>
thanks for the update
<emersion>
"Most clients use sealed memfds on Linux"
<emersion>
not really no
<i509VCB>
I do know that there is a wayland branch for wine somewhere
<DemiMarie>
emersion: the only two production-quality wl_shm implementations I know of are those in libwayland-server and Smithay
<DemiMarie>
I am handling libwayland-server and i509vcb is handling Smithay.
<i509VCB>
Well I need to actually write it lol
<i509VCB>
Shouldn't be too long when I get the time
cheako has left #wayland [#wayland]
<emersion>
DemiMarie: clients impl as well
<emersion>
the impl in libwayland is for servers only
<DemiMarie>
emersion: fair, my point was that I can’t contribute to three server impls if only two exist
<emersion>
3 impls, at least one client and one server
<DemiMarie>
Ah okay
<DemiMarie>
So libwayland-server + Smithay + foot would suffice
<DemiMarie>
I thought the rule was 3 servers and 3 clients.
<emersion>
ah, no
<emersion>
it would
Leopold_ has quit [Remote host closed the connection]
Leopold_ has joined #wayland
__nick__ has quit [Ping timeout: 480 seconds]
dcz_ has quit [Ping timeout: 480 seconds]
nerdopolis has quit [Remote host closed the connection]