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
Net147 has quit [Ping timeout: 480 seconds]
co1umbarius has joined #wayland
columbarius has quit [Ping timeout: 480 seconds]
Net147 has joined #wayland
Lucretia has quit []
zebrag has joined #wayland
zebrag has quit []
columbarius has joined #wayland
co1umbarius has quit [Ping timeout: 480 seconds]
c7s has quit [Ping timeout: 480 seconds]
Net147 has quit [Ping timeout: 480 seconds]
Net147 has joined #wayland
boistordu_ex has joined #wayland
hendursaga has quit [Remote host closed the connection]
hendursaga has joined #wayland
boistordu has quit [Ping timeout: 480 seconds]
leon-p has quit [Ping timeout: 480 seconds]
dcz_ has joined #wayland
danvet has joined #wayland
hardening has joined #wayland
spstarr has joined #wayland
pnowack has joined #wayland
novakane has joined #wayland
rgallaispou has joined #wayland
wlb has quit [Quit: Leaving.]
hendursa1 has joined #wayland
hendursaga has quit [Ping timeout: 480 seconds]
<pq>
zubzub, can you file a Gitlab issue, please?
<pq>
DemiMarieObenour[m], no, no "Foo over Wayland". If you absolutely must, write a tiny extension to deliver a socket fd over Wayland, and talk the Foo through the new fd.
<pq>
DemiMarieObenour[m], I don't think there are any good examples for any "Foo over Wayland", but that's just me and so far.
rasterman has joined #wayland
<DemiMarieObenour[m]>
pq: I am not at all surprised that “Foo over Wayland” is a terrible idea. It is obviously possible, but that doesn’t mean it is desirable.
<pq>
yeah
<pq>
it's also why we have refused to have any kind of "arbitrary (window) property strings" interface in Wayland, because that really is just another "Foo over Wayland".
<pq>
OTOH, passing socket or pipe fds around you probably don't even need new code to handle Foo, just use the libs that already exist.
<pq>
then you can also prioritize Foo vs. Wayland the way you want
d_ed has joined #wayland
Lucretia has joined #wayland
fmuellner has joined #wayland
leon-p has joined #wayland
<DemiMarieObenour[m]>
Wayland iCCCM is obviously something you do not want to have to write
<DemiMarieObenour[m]>
🙂
<DemiMarieObenour[m]>
s/ not/_not_/
<DemiMarieObenour[m]>
The only two good examples of “Foo over Wayland” I can think of are X11 and qyliss’s suggestion of PipeWire. The first to ensure synchronization (assuming that has not already been solved), the second for the reasons qyliss mentioned.
<qyliss>
passing pipes seems like a very sensible way to satisfy my requirements though!
MrCooper has quit [Remote host closed the connection]
MrCooper has joined #wayland
<qyliss>
or a socket, I suppose, because PipeWire needs to send fds
jgrulich has joined #wayland
jgrulich has quit [Ping timeout: 480 seconds]
novakane_ has joined #wayland
novakane has quit [Ping timeout: 480 seconds]
rsttst has joined #wayland
rsttst has quit []
<emersion>
pq, jadahl: i think it would be nice to get a wayland release out, it's been a while. anything you want in the next release?