05:44 <ramblurr> gbrlsnchs: i'm in the same boat. i've been preparing by getting my language of choice wired up so it can speak to a wayland server over a socket. i've used wayland-book and https://bugaevc.gitbooks.io/writing-wayland-clients/content/

13:07 <gbrlsnchs> ramblurr: ohhh nice... thanks for sharing! yeah, the reason I was wondering how the communication was established was due to trying to pick a language for it... above all things, I want to have fun doing that 😆

14:12 <The_Buhs> bugaevc's book helped me a lot writing my two (fairly simple) Wayland clients

14:42 <leon-p> I have recently found that I have the most fun writing Wayland code if I do the gritty details in C and the high-level policy bits in Scheme. In general trying to do the low-level wayland bits in a high-level language is usually not much fun IMO

14:44 <leon-p> it also forces you to have a stronger business-logic vs. UI-logic separation, possibly even with the former ending up as a library, which is good style anyway

14:45 <leon-p> I have used the style of writing applications as libraries a lot recently for (non-public) projects and I really like it

15:05 <ramblurr> i just flipped the public switch on my java/jvm bindings for libwayland: https://github.com/Ramblurr/wayland-java

15:05 <ramblurr> next step i'm going to implement my river layout generator in clojure, but using those bindings

15:09 <Nickli> speaking of layouts, is "widescreen" where its a central dedicated window with rest filling in the unused space on the sides?

15:18 <leon-p> I don't think there are canonical names even for common layouts

15:19 <leon-p> FWIW i have an ultra-wide screen and never really liked the layouts supposedly optimized for that, since I find it quite jarring that the window stack is split between left and right, feels a bit too jumpy for me

15:29 <Nickli> i've always preferred having a browser in the center which doesnt take up the full width (even at 1080p)

15:31 <Nickli> was wondering how widescreen worked in relation to Ultitile and Widerivers

16:09 <leon-p> I find ultra-wide best with just two windows side-by side. each window then has about the size of an 4:3 monitor, which I consider the ideal size for any productivity software

17:26 <robertgzr> does anybody know how to debug failing output configuration

17:26 <robertgzr> the WAYLAND_DEBUG output isnt super helpful

17:26 <robertgzr> it only show "zwlr_output_configuration_v1#3.failed"

17:27 <robertgzr> where do i look to find out what exactly it is failing on

17:27 <leon-p> what output configuration are you trying to apply?

17:27 <leon-p> if it involves custom modes, they may be invalid. if it involved multiple outputs, it may be a bandwidth issue

17:28 <robertgzr> multiple outputs

17:28 <leon-p> does it work if you leave one of the outputs off?

17:28 <robertgzr> cant get my external screen to work anymore :/

17:28 <leon-p> ah, so it used to work? are you using kanshi or wlr-randr or ?

17:28 <robertgzr> tried both

17:29 <robertgzr> my suspicion is that the wlroots 18.1 bump has something to do with it

17:29 <robertgzr> it worked until a reboot

17:30 <leon-p> if it used to work and doesn't anymore, a wlroots issue seems likely

17:31 <robertgzr> trying to go back to 0.18.0 now

17:31 <leon-p> there is the chance that the output names changed, perhaps

17:33 <robertgzr> just had a look. they check out