ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
co1umbarius has joined #wayland
columbarius has quit [Ping timeout: 480 seconds]
lbia has quit [Ping timeout: 480 seconds]
lbia has joined #wayland
fmuellner has quit [Ping timeout: 480 seconds]
nerdopolis has joined #wayland
mclasen has joined #wayland
garnacho has quit [Ping timeout: 480 seconds]
aaron465 has quit [Quit: Client limit exceeded: 20000]
Brainium has quit [Quit: Konversation terminated!]
nerdopolis has quit [Ping timeout: 480 seconds]
bjorkint0sh has joined #wayland
mclasen has quit [Ping timeout: 480 seconds]
bjorkintosh has quit [Ping timeout: 480 seconds]
mxz__ has joined #wayland
glennk has joined #wayland
mxz___ has joined #wayland
mxz has quit [Ping timeout: 480 seconds]
mxz___ is now known as mxz
mxz_ has quit [Ping timeout: 480 seconds]
rv1sr has joined #wayland
mxz_ has joined #wayland
mxz has quit [Ping timeout: 480 seconds]
mxz__ has quit [Ping timeout: 480 seconds]
mxz_ is now known as mxz
kts has joined #wayland
sally has quit [Ping timeout: 480 seconds]
sally has joined #wayland
Crocodillian has left #wayland [WeeChat 4.2.1]
KDDLB has quit [Read error: Connection reset by peer]
kode54 has quit [Write error: connection closed]
kode54 has joined #wayland
kode54 has quit []
kode54 has joined #wayland
KDDLB has joined #wayland
bcheng has quit [Remote host closed the connection]
bcheng has joined #wayland
kts has quit [Ping timeout: 480 seconds]
kts has joined #wayland
crazybyte has quit [Quit: Ping timeout (120 seconds)]
crazybyte has joined #wayland
crazybyte has quit [Read error: Connection reset by peer]
crazybyte has joined #wayland
privacy has quit [Remote host closed the connection]
<KarenTheDorf>
What's the criteria for a protocol to be in 'staging' vs 'unstable'?
<zzag>
unstable is obsolete
<zzag>
new protocols should go to "staging"
narodnik has joined #wayland
mclasen has quit [Ping timeout: 480 seconds]
<KarenTheDorf>
Well that's simple. :D
<KarenTheDorf>
I assume truely unstable stuff now lives out-of-tree, and staging is for things that are sufficently implemented cross-compositor or otherwise on-track to end up as stable?
Brainium has quit [Quit: Konversation terminated!]
mclasen has joined #wayland
feaneron has joined #wayland
Guest1344 is now known as raghavgururajan
feaneron has quit []
daz has joined #wayland
d42 has quit [Ping timeout: 480 seconds]
riteo has quit [Ping timeout: 480 seconds]
kts has quit [Quit: Konversation terminated!]
leon-anavi has quit [Quit: Leaving]
mclasen has quit [Ping timeout: 480 seconds]
rasterman has quit [Quit: Gettin' stinky!]
lsd|2 has quit [Ping timeout: 480 seconds]
bjorkint0sh has quit [Quit: "Every day, computers are making people easier to use." David Temkin]
lsd|2 has joined #wayland
mclasen has joined #wayland
<ids1024_>
KarenTheDorf: I don't know if there's a set rule, but it seems generally protocols that are meant to be used by multiple compositors should be proposed to wayland-protocols. While out-of-tree protocols should generally be compositor-specific and prefixed with the compositor. The "truely unstable" version of the protocol is the one in a merge request to wayland-protcols that hasn't
<ids1024_>
been merged yet.
<KarenTheDorf>
Got it. xdg-decoration is 'unstable' but it seems widely supported by those DEs that wish to support it, so I should be fine to use it I guess. :crossed_fingers:
<ids1024_>
Or in other words: if you want to propose a protocol to be implemented by multiple compositors, open an MR on wayland-protocols adding it to `staging`.
<ids1024_>
Even if a new breaking version of xdg-decoration (xdg-decoration-unstable-v2) is released, generally compositors wouldn't stop supporting xdg-decoration-unstable-v1.
Brainium has joined #wayland
<KarenTheDorf>
Oh I'm not brave enough yet for adding new protocols. (And kwin has stopped supporting kde-server-decoration, which is why I had a minor concern)
<KarenTheDorf>
It's basically the same as xdg-decoration-v1 except for the interface names afaict
mclasen has quit [Quit: mclasen]
agd5f has quit [Read error: Connection reset by peer]
<zzag>
KarenTheDorf: kwin still supports the kde protocol
<KarenTheDorf>
*checks wayland-info* Huh! It does! I don't know why I thought it didn't!
<KarenTheDorf>
But I've ported my library to xdg now so I have no use for this now-corrected misconception. :)
<emersion>
KarenTheDorf: it's not the same, with xdg the compositor is in full control
mclasen has quit [Ping timeout: 480 seconds]
mvlad has quit [Remote host closed the connection]
<KarenTheDorf>
emersion: Is it? I guess the comments suggest the server should honor the request? Regardless, I have my code set to just say "screw it, you're only getting fullscreen" if either 1) xdg-decoration isn't supported or 2) It is but the server insists on client anyway
<KarenTheDorf>
One day I might implement libdecor
<kennylevinsen>
KarenTheDorf: in xdg decoration, what the client specifies is just a preference. The server decides and is free to disregard the client preference, and may change its decision at will.
<KarenTheDorf>
I thought that was how the kde one worked as well given the requests and events, but one of the comments does seem to imply it's not optional for the server to refuse. (I say that like there isn't one server that will ever implement it, kwin)