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
d42 has joined #wayland
mvlad has quit [Remote host closed the connection]
neonking has quit [Remote host closed the connection]
ahartmetz has quit [Quit: Konversation terminated!]
asocialblade has joined #wayland
asocialblade has quit []
asocialblade has joined #wayland
asocialblade has quit []
asocialblade has joined #wayland
asocialblade has quit []
asocialblade has joined #wayland
asocialblade has quit []
asocialblade has joined #wayland
fmuellner has quit [Ping timeout: 480 seconds]
dyronl^ has joined #wayland
dcz has joined #wayland
dcz_ has joined #wayland
dcz has quit [Ping timeout: 480 seconds]
Arnavion has quit [Quit: Arnavion]
Arnavion has joined #wayland
jmd has quit [Ping timeout: 480 seconds]
occivink has quit [Server closed connection]
occivink has joined #wayland
___nick___ has joined #wayland
zebrag has quit [Quit: Konversation terminated!]
reillybrogan_ has joined #wayland
reillybrogan has quit [Ping timeout: 480 seconds]
ppascher has quit [Quit: Gateway shutdown]
ppascher has joined #wayland
nadrian has quit [Server closed connection]
nadrian has joined #wayland
leandrohrb has quit [Server closed connection]
leandrohrb has joined #wayland
danvet has joined #wayland
ppascher has quit [Quit: Gateway shutdown]
ppascher has joined #wayland
ppascher has quit []
ppascher has joined #wayland
FLHerne has quit [Quit: There's a real world out here!]
hardening has joined #wayland
FLHerne has joined #wayland
caveman has joined #wayland
duxsco has joined #wayland
frog has quit [Ping timeout: 480 seconds]
V has quit [Server closed connection]
V has joined #wayland
mooff has quit [Server closed connection]
mooff has joined #wayland
cmeissl[m] has quit [Server closed connection]
cmeissl[m] has joined #wayland
duxsco has quit [Ping timeout: 480 seconds]
Fester^ has quit [Ping timeout: 480 seconds]
wolfshappen has quit [Server closed connection]
wolfshappen has joined #wayland
luc4 has joined #wayland
floof58_ has joined #wayland
floof58 has quit [Ping timeout: 480 seconds]
floof58_ is now known as floof58
captainchris has joined #wayland
<captainchris>
Hi everybody
rasterman has joined #wayland
<captainchris>
I'm trying to understand the principe of wayland. I'm french and I have lot's of difficult to understand the usage of wl_registry, the communication between server and client ... Do you have video tutorial about that
<captainchris>
yes of course I'm trying to read it. I'm reading bugaevc github tutorial too but video tutorial will better to understand
mceier has quit [Ping timeout: 480 seconds]
flacks has joined #wayland
floof58 has quit [Quit: floof58]
floof58 has joined #wayland
dreda has quit [Server closed connection]
dreda has joined #wayland
dreda is now known as Guest389
mceier has joined #wayland
bodiccea has quit [Remote host closed the connection]
ahartmetz has joined #wayland
<dottedmag>
Ah, video tutorials... Giving easy illusion of understanding.
<captainchris>
dottedmag: yes
<dottedmag>
The main word is *illusion*
bodiccea has joined #wayland
<captainchris>
but there are lot's of notion to understand registry proxy backend seat ...
<captainchris>
I'm lost
bodiccea has quit []
bodiccea has joined #wayland
<captainchris>
I'm reading about wl_registry it says when a client creates a registry object, the registry object will emit a global event for each -> global <- currently in the registry
<captainchris>
I surround global but what is the global surrounded, is it event ??
<captainchris>
it is object(message) ??
adia has quit [Server closed connection]
adia has joined #wayland
Shimmy0 has quit [Server closed connection]
Shimmy0 has joined #wayland
<captainchris>
I think that i need schema to really understand thje functionality about proxy/registry/object between client and server
<dottedmag>
captainchris: global is a "global object" stored in the registry. you can bind it using 'bind'. "global" event notifies client about the "global object" stored in registry.
<kennylevinsen>
global objects are the interfaces/protocols the compositor exposes that you can "call methods" on
<captainchris>
ok and global object are messages ??
<kennylevinsen>
Messages carry either requests or events, both of which act on an object. E.g., you can send a "commit" request on a wl_surface object to say "apply the changes I made to this surface".
<kennylevinsen>
everything has to happen on an object, and so to kickstart things, wl_registry gets to be a magically implied object 0 that always exists. Thr wayland server uses this to notify you of what things it has to offer, and you then create instances of the things you want using wl_registry::bind