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
bim9262 has joined #wayland
slattann has joined #wayland
co1umbarius has joined #wayland
columbarius has quit [Ping timeout: 480 seconds]
Emantor has quit [Quit: ZNC - http://znc.in]
Emantor has joined #wayland
lxsameer has quit [Ping timeout: 480 seconds]
lsd|2 has quit []
luc4 has quit []
eroc1990 has quit [Quit: Ping timeout (120 seconds)]
eroc1990 has joined #wayland
cool110_ has joined #wayland
cool110 has quit [Ping timeout: 480 seconds]
zebrag has quit [Quit: Konversation terminated!]
Moprius has quit [Quit: Konversation terminated!]
duxsco has joined #wayland
slattann has quit []
Company has quit [Quit: Leaving]
duxsco has quit [Quit: duxsco]
ashketchum[m] has joined #wayland
rv1sr has joined #wayland
dcz_ has joined #wayland
slimbo has quit [Quit: slimbo]
slimbo has joined #wayland
cool110 has joined #wayland
c7s has quit [Ping timeout: 480 seconds]
cool110_ has quit [Ping timeout: 480 seconds]
bittin has joined #wayland
rpigott has quit [Read error: Connection reset by peer]
rpigott has joined #wayland
danvet has joined #wayland
lsd|2 has joined #wayland
cool110 has quit [Remote host closed the connection]
cool110 has joined #wayland
rasterman has joined #wayland
hardening has joined #wayland
manuel1985 has joined #wayland
lxsameer has joined #wayland
___nick___ has joined #wayland
manuel1985 has quit [Ping timeout: 480 seconds]
txtsd has quit [Ping timeout: 480 seconds]
jmdaemon has quit [Ping timeout: 480 seconds]
txtsd has joined #wayland
<wlb> wayland-protocols Issue #88 opened by () Interaction of relative-pointer and wl_pointer.frame https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/88
flacks_ has quit [Quit: Quitter]
flacks has joined #wayland
luc4 has joined #wayland
ecloud_ has quit [Ping timeout: 480 seconds]
Company has joined #wayland
duxsco has joined #wayland
Moprius has joined #wayland
neonking has joined #wayland
ecloud_ has joined #wayland
rasterman has quit [Quit: Gettin' stinky!]
zebrag has joined #wayland
cvmn has joined #wayland
caveman has quit [Ping timeout: 480 seconds]
lsd|2|2 has joined #wayland
lsd|2|2 has quit []
lsd|2 has quit []
lantizia has joined #wayland
<lantizia> Presumably... a) the wayland spec doesn't *itself* include any parameters for accessing wayland 'sessions' (I say that loosely, thinking like an x.org user) remotely....
<lantizia> b) accessing such wayland 'sessions' would be via such things like pipewire... and such vnc servers, xrdp, nomachine, etc... can access the screen data via that
<lantizia> c) (and this is the main question)... such data that your remote-access-software-of-choice can access... would purely just be pixels? i.e. no instructional window/widget-level information like early X.org forwarded windows and such!?
eroc1990 is now known as Guest3239
eroc1990 has joined #wayland
<lantizia> i'm thinking... a) yes, b) yes, c) yes
Guest3239 has quit [Ping timeout: 480 seconds]
luc4 has quit []
<any1> Currently, there are only screen capturing protocols that can give you composited pixel buffers.
duxsco has quit [Quit: duxsco]
<any1> It would be possible to create a protocol that passes a collection of pixel buffers and some information on how to composite them.
<any1> Although, that wouldn't be particularly useful. You'd probably end up transmitting more data than if you just used composited buffers.
<any1> Doing things on the widget level would require the protocol to be somehow integrated with some of the more populare toolkits such as qt and gtk
<i509VCB> On C, it could be raw pixels or draw commands in OpenGL/Vulkan if you were willing to hack that into place to execute on the remote client
ecloud_ has quit [Ping timeout: 480 seconds]
Narrat has joined #wayland
andyrtr_ has joined #wayland
ecloud_ has joined #wayland
andyrtr has quit [Ping timeout: 480 seconds]
andyrtr_ is now known as andyrtr
c7s has joined #wayland
ecloud_ has quit [Ping timeout: 480 seconds]
danvet has quit [Remote host closed the connection]
lantizia has quit [Remote host closed the connection]
ecloud_ has joined #wayland
andyrtr_ has joined #wayland
andyrtr has quit [Ping timeout: 480 seconds]
andyrtr_ is now known as andyrtr
<wlb> wayland-protocols Issue #89 opened by () wayland-protocols needs replacement for XDS dnd file saving protocol https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/89
jmdaemon has joined #wayland
___nick___ has quit []
___nick___ has joined #wayland
___nick___ has quit []
___nick___ has joined #wayland
Moprius has quit [Quit: Konversation terminated!]
zebrag has quit [Quit: Konversation terminated!]
cvmn has quit []
caveman has joined #wayland
eroc1990 has quit [Ping timeout: 480 seconds]
PuercoPop has joined #wayland
Hypfer has quit [Read error: Connection reset by peer]
Hypfer has joined #wayland
manuel1985 has joined #wayland
duxsco has joined #wayland
dcz_ has quit [Ping timeout: 480 seconds]
Moprius has joined #wayland
Narrat has quit []
___nick___ has quit [Ping timeout: 480 seconds]
zebrag has joined #wayland
rv1sr has quit []
hardening has quit [Ping timeout: 480 seconds]
duxco has joined #wayland
duxsco has quit [Ping timeout: 480 seconds]
duxco is now known as duxsco
lxsameer has quit [Ping timeout: 480 seconds]
eroc1990 has joined #wayland
agd5f has quit [Ping timeout: 480 seconds]
zebrag has quit [Quit: Konversation terminated!]