Newest at the top
| 2025-12-06 22:18:19 +0100 | <[exa]> | yushyin: thanks! |
| 2025-12-06 22:18:12 +0100 | <[exa]> | interesting |
| 2025-12-06 22:14:51 +0100 | <davean> | Lots of worry about a thing, but I never found the discussion of how they settled on that thing, etc |
| 2025-12-06 22:13:47 +0100 | <davean> | but that wouldn't be as clean IMO |
| 2025-12-06 22:13:40 +0100 | <davean> | One could also have a realtime thread for the renderer, but that wouldn't accomplish the restart portion, one could use something like hint for the config and update the datastructure for the renderer ... |
| 2025-12-06 22:11:49 +0100 | lambda_gibbon | (~lambda_gi@2603:7080:ee00:37d8:35d4:1aac:9a2f:cd11) (Ping timeout: 260 seconds) |
| 2025-12-06 22:10:59 +0100 | <davean> | and I was missing something huge reading the discussions about it |
| 2025-12-06 22:10:45 +0100 | <davean> | It seemed like everyone got on the same page of how to go about those projects somewhere else that I couldn't find |
| 2025-12-06 22:10:20 +0100 | <davean> | like I'd probably go about running a pauseless-GC renderer with a standard control process and make the control process restartable but the renderer not. |
| 2025-12-06 22:09:39 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 250 seconds) |
| 2025-12-06 22:09:38 +0100 | <davean> | I did see people worrying about pause times, but I didn't even see discussions of the pauseless GC or seperating out a rendering process from a control process or anything |
| 2025-12-06 22:08:45 +0100 | <davean> | I didn't get deep enough into them to figure it out |
| 2025-12-06 22:08:00 +0100 | <davean> | so very confused |
| 2025-12-06 22:07:57 +0100 | <davean> | I didn't even see places it would differ from the automation |
| 2025-12-06 22:07:43 +0100 | <davean> | Their custom Setup.hs stuff, all the hand done stuff for straight bindings ... |
| 2025-12-06 22:05:16 +0100 | <davean> | it confused me |
| 2025-12-06 22:05:13 +0100 | <davean> | I mean I looked at some of that code and I was lacking the context for why they went about it the way they did |
| 2025-12-06 22:05:00 +0100 | lambda_gibbon | (~lambda_gi@2603:7080:ee00:37d8:35d4:1aac:9a2f:cd11) |
| 2025-12-06 22:04:44 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-12-06 22:02:48 +0100 | <geekosaur> | one would think, sadly that's exactly where waymonad and the new attempt failed. I don't know why either but suspect I won't do any better if I try to pick up e.g. the work done by the folks on discourse (look for "wlroots" and "tinywl-hs") |
| 2025-12-06 22:00:48 +0100 | <davean> | I've not gotten into it much but I really have wondered whats going on with them running into issues with the parts I think should be the easy parts |
| 2025-12-06 21:57:53 +0100 | <davean> | Every time I've looked in at waymonad I've been confused about the things they were running into issues with, like I don't get why they have issues with the bindings |
| 2025-12-06 21:56:30 +0100 | amadaluzia | (~amadaluzi@user/amadaluzia) (Remote host closed the connection) |
| 2025-12-06 21:54:42 +0100 | skum | (~skum@user/skum) skum |
| 2025-12-06 21:54:17 +0100 | <geekosaur> | I don't really know, or I'd be at least helping out with the waymonad stuff instead of cheering from the sidelines 😞 |
| 2025-12-06 21:54:01 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 264 seconds) |
| 2025-12-06 21:52:00 +0100 | lambda_gibbon | (~lambda_gi@2603:7080:ee00:37d8:35d4:1aac:9a2f:cd11) (Ping timeout: 265 seconds) |
| 2025-12-06 21:50:51 +0100 | skum | (~skum@user/skum) (Quit: WeeChat 4.7.2) |
| 2025-12-06 21:48:57 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-12-06 21:45:30 +0100 | tcard | (~tcard@2400:4051:5801:7500:cf17:befc:ff82:5303) tcard |
| 2025-12-06 21:45:16 +0100 | Lycurgus | (~juan@user/Lycurgus) (Quit: alsoknownas.renjuan.org ( juan@acm.org )) |
| 2025-12-06 21:41:58 +0100 | lambda_gibbon | (~lambda_gi@2603:7080:ee00:37d8:35d4:1aac:9a2f:cd11) |
| 2025-12-06 21:40:49 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 264 seconds) |
| 2025-12-06 21:37:05 +0100 | tcard_ | (~tcard@2400:4051:5801:7500:cf17:befc:ff82:5303) (Quit: Leaving) |
| 2025-12-06 21:36:29 +0100 | deptype | (~deptype@2406:b400:3a:9d2f:1142:a400:8c37:c8a7) (Remote host closed the connection) |
| 2025-12-06 21:35:21 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-12-06 21:28:53 +0100 | lambda_gibbon | (~lambda_gi@2603:7080:ee00:37d8:35d4:1aac:9a2f:cd11) (Ping timeout: 244 seconds) |
| 2025-12-06 21:25:35 +0100 | <yushyin> | I've toyed around with wlroots a bit in haskell, and I got to the point where I could spawn clients that were rendering correctly and worked xD But I never got any further than that, lack of time and all that |
| 2025-12-06 21:24:08 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 244 seconds) |
| 2025-12-06 21:21:03 +0100 | <yushyin> | [exa]: xdg-shell is the basic protocol for the window managing stuff, but you should read about the wayland protocol design first. https://wayland-book.com/ this might be a ok starting point |
| 2025-12-06 21:19:33 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-12-06 21:13:47 +0100 | <[exa]> | cc geekosaur ^ |
| 2025-12-06 21:13:34 +0100 | <[exa]> | is there some good overview of how wayland actually does the windowmanaging stuff? (for people untouched by wayland so far) |
| 2025-12-06 21:11:24 +0100 | pavonia | (~user@user/siracusa) siracusa |
| 2025-12-06 21:09:01 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 264 seconds) |
| 2025-12-06 21:03:46 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-12-06 21:02:45 +0100 | ChanServ | +v haskellbridge |
| 2025-12-06 21:02:44 +0100 | haskellbridge | (~hackager@96.28.224.214) hackager |
| 2025-12-06 21:00:55 +0100 | haskellbridge | (~hackager@96.28.224.214) (Ping timeout: 240 seconds) |
| 2025-12-06 20:57:05 +0100 | pebble | (~pebble@37.63.35.63) pebble |