freenode/#clim - IRC Chatlog
Search
14:34:23
random-nick
libwayland is actually just a library for local RPCs, and the wayland specification is a RPC protocol for requesting a window, drawing on that window and getting input
14:35:10
random-nick
which means the compositor has to do everything Xorg does (input handling, graphical output...)
14:42:28
beach
random-nick: I am sure this is all very interesting, but I don't see how it fits in with the desktop stuff I started with.
14:43:26
beach
So, what if on #lisp I suggest "reviving Eclipse" as an independent project? It would be a non-tiling window manager written in Common Lisp.
14:44:33
beach
Perhaps hinting that it could become the basis of a desktop environment written in Common Lisp?
14:45:19
beach
I mean, it is unlikely that there would be any taker, but I could always add it to my list of suggested projects. But I will do that only if it is a reasonable thing to do.
14:51:00
beach
jackdaniel: OK, so nothing obviously wrong about it as far as you can see. I'll think about it some more and maybe suggest it.
15:00:19
beach
I see. And a window manager seems to me that it must be very dependent on the display server. Right?
15:03:08
jackdaniel
someone interested in fooling around could make application-frame-pane monsteriosity, subclass grid-pane composite pane, add window decorations and pretend, that full screen "top-level application frame" is a window manager
15:09:33
djeis[m]
Wayland, for example, is actually little more than a communication protocol between a display server and the programs wanting to draw on said display.
15:10:32
djeis[m]
The equivalent of the window manager in a wayland system actually replaces X11 entirely- it talks directly to the graphics card and has full control over actually painting all of the windows on screen.
15:11:14
djeis[m]
It also recieves the input events from the kernel and passes them along to applications using the wayland protocol.
15:12:06
djeis[m]
Since it actually is what paints the windows on the display it's often called a wayland compositor instead of a window manager.
15:16:51
djeis[m]
Also, the window manager actually is what provides multiple desktops/workspaces in an X11 environment, there's just a protocol by which other applications can ask the window manager what windows are on which workspaces and to switch workspaces. It is just mapping/unmapping windows internally tho, the window manager just has to orchestrate it because of the way other protocols for controlling a window manager work.
15:18:09
djeis[m]
Like the list of minimized applications in a taskbar- said taskbar can actually be implemented by a 3rd party program just talking to the window manager, but if the window manager isn't what manages workspaces then that taskbar has no good way to restrict its list of tasks to just those on the current workspace.
20:32:19
scymtym
i will probably have a pull request for the encapsulation and INDENTING-OUTPUT-STREAM fixes (including a new test) in a bit
21:34:42
jackdaniel
I've changed the margin conception a little, but indenting-output won't change much in it (unless there are good reasons for that)
21:35:11
jackdaniel
in essence instead of creating a new class I repurpose margin abstraction (for filling-output too)
1:00:15
eschatologist
Mezzano uses neither X11 nor Wayland. It just talks to a framebuffer and does software compositing.
1:02:21
eschatologist
What Wayland calls a “compositor” is what NeXT/Apple calls a “window server.” It provides drawing surfaces to applications, composites those surfaces on screen (really, manages the GPU doing so), receives input from HI devices, and dispatches that input to the appropriate application(s).