"It won't be long now until Wayland has a tenth of X's features. "
haters gonna hate. even if Høgsberg is convicted of killing his wife, wayland is gonna gonna die. never!
I don't really know, hence why I asked. So don't ask the clueless, better explain it to him...Weston is a WM/compositor/display server that uses the Wayland protocol, isn't it?
Sorry if I sound noobish, but in that topic I am.
Wayland is the protocol. Just like X has the X11 protocol, for clients to talk with the server. So yes, you could say it is between toolkits (Gtk, Qt, EFL, ...) and a server.
Libwayland (often just "wayland") is a C library, which implements the Wayland (core and few extensions) protocol bindings, and offers a C application programming interface for easy use. You could say that libwayland turns C function calls into bytes that are transferred through a local Unix socket, and it does also the opposite.
Weston is the reference Wayland server (and a compositor and a window manager in the same package). It is the reference compositor, because it is what the Wayland depelopers mainly work on. There are also other Wayland compositors, I think Qt has a handful, for instance.
I dunno, the more I read about what wayland is in this thread, the more I keep thinking "this is just X11 with a different name" lol.. so basically it's a protocol (much like X11) that can manage windows and workspaces (much like X11)..
I was under the impression that Wayland provides a very thin layer for applications to dump their GUI stuff on. I didn't think there would be window management involved or anything like that.
Please forgive me if I sound noobish here.
Last edited by 9a3eedi; 06-13-2012 at 06:22 PM.