ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
Brainium has quit [Quit: Konversation terminated!]
Moprius has quit [Quit: bye]
Moprius has joined #wayland
<mstoeckl>
riteo: re wl_registry names: libwayland internally has a server-global list of globals+names, but I would not rely on this since other implementations may differ
<mstoeckl>
also: in case you're interested, I've written a few proxy/embedding programs of varying quality (waypipe, wmux, windowtolayer, wborder, swaylock-plugin, ...); in practice they all need a lot of code to handle program requests.
<danieldg>
yeah, any proxy has to have full understanding of all globals it permits to be present
<danieldg>
even if it's just "this one doesn't need any special handling"
<riteo>
mstoeckl: I see, that makes sense. I'll choose a more conservative approach then
<riteo>
also, yes, I'm interested indeed, I think proxying has a lot of potential still :D
<riteo>
I didn't know you made so many programs! I think what I'm doing is basically wmux but for clients
<riteo>
(to be clear, what I mean is that I only heard about waypipe, I had no idea other proxies existed)
<riteo>
danieldg: I don't mind really, I think it's still way cleaner than manually hooking up every global through a compositor library
<riteo>
like, I'm fine with basically building a wayland-only compositor at this point. Since I don't need to handle rendering, scene tree, output management and whatnot, I think that any logic of proxying/accounting is going to be simpler and easier to extend than any generic compositor library
<linkmauve>
And waypipe now works perfectly on panvk. :)
<riteo>
also rn the only thing my proxy has to know about most interfaces are the signatures, really. That's like, "add this pointer to this place" and we're done, compared to hooking up every single event handler to basically relay the same thing.