12:38 <ifreund> leon-p: do you have a complete rwm client written?

12:39 <ifreund> I'm at the stage where I could try and get it to render something though input won't work yet

12:39 <ifreund> if not no problem, I'll need to write my own sooner or later

15:19 <leon-p> I have one, but I can't remember how complete it was. I'll take a look when I am back home at my laptop

15:20 <leon-p> although realisitcally, rivertile needs to be ported anyway

15:40 <ifreund> yeah, I started on a rivercompat window manager

15:40 <ifreund> I think I can make it a Wayland server as well that provides a very limited set of protocols for layout generator compatibility

15:42 <ifreund> right now the goal is just to have something I can use to test the thousands of lines of completely untested new code in river

18:23 <UNIXGUY> Trying to understand how `rivertile.zig` works - interested in modifying it so that new windows are inserted not as the Main window, but as the window after Main / before the rest of the slaves, which function would I look at modifying? Am I in the right direction for looking at `fn addOutput(context: *Context, registry: *Registry, name: u32)

18:23 <UNIXGUY> !void` ? Is the `outputs` field in the `Context` struct representing the active windows?

18:28 <ifreund> UNIXGUY: the layout generator doesn't have control over where new windows are inserted

18:28 <ifreund> you are looking for `riverctl attach-mode <foo>`

18:29 <ifreund> also, "outputs" generally refers to monitors/displays/whatever on wayland

18:30 <ifreund> "output" as in output of the compositor to your display hardware

18:32 <UNIXGUY> thank you! I will check that out.

18:33 <UNIXGUY> helpful info, good to know. thank you

19:53 <ifreund> rendered a foot with the rwm branch :)

19:53 <ifreund> https://0x0.st/8rzH.png

19:54 <TheAnachron> (imagine a thumbs-up reaction here)

20:00 <tiosgz> this probably means my holiday plans to learn for exams are cancelled :)

20:01 <tiosgz> maybe input doesn't work yet, but apparently i'm severely lagging behind the rwm branch

20:01 <ifreund> tiosgz: I haven't pushed yet, one minute

20:02 <tiosgz> you wanna make my lagging-behind more severe? :D

20:03 <ifreund> pushed now :D

20:03 <ifreund> nothing useful yet of course, but an important step forward

20:04 <ifreund> writing code without being able to test any of it was very energy draining

20:04 <ifreund> I need dopamine from working images on the screen :D

20:04 <ifreund> also it crashes when foot is closed, but that's my next step to fix

20:05 <vyivel> embrace delayed gratification, imagine how well it will run once you're done and keep writing without testing

20:05 <TheAnachron> ifreund I imagine creating protocols like wayland is even more energy draining than implementing them.

20:05 <ifreund> I found the protocol writing bit pretty fine

20:06 <ifreund> it's easy to abstractly describe what you want to happen, actually writing the code is where things get hard

20:06 <TheAnachron> Really? I checked the new color spec and I saw a lot of headache. Or maybe its just me...

20:06 <ifreund> color management is a whole different beast

20:06 <sewn> woah a title

20:07 <ifreund> sewn: do you mean foot's client side decoration?

20:07 <sewn> awwww its from foot