01:05 <NickH> Bye, bye stacktile 😥

14:45 <gbrlsnchs> What features would the new WM protocol allow that are currently not possible—or feasible—today? Asking out of curiosity really, since I don't have any experience with creating layout managers

14:46 <gbrlsnchs> and also because I would love to hear your plans for the incoming protocol 🙂

16:03 <leon-p> gbrlsnchs: so many new things that it would be futile to list them

16:05 <leon-p> basically, instead of just being asked to create a list of positions and dimensions for windows at specific times like the layout protocol, the WM protocol most importantly allows the WM client to target specific windows, control focus, control whether a window is displayed or not, can draw decoration and desktop widgets and more

16:44 <gbrlsnchs> leon-p: gotcha, thanks for the briefing... is there going to be a default behavior in case the WM client doesn't implement any of these features?

16:50 <ifreund> gbrlsnchs: no, river will always require a WM to be useful. I do plan to make a river-compat WM that implements rivers current window management features and and tries to be as compatible as possible with river 0.3 though

16:54 <gbrlsnchs> ifreund: I see... yeah, that would be nice not only to have river (post WM protocol) working out of the box but also as a reference WM for newbies (like me) to get started with WM client development 😁

16:55 <gbrlsnchs> cool stuff folks!!!

16:56 <ifreund> gbrlsnchs: for sure, a big goal with this work is to make WM development and experimentation as easy as possible :)

16:56 <novakane> that made me think, ifreund do you intend to write a simple one like rivertile or you gonna let this to 3rd party

16:57 <ifreund> novakane: you mean a reference WM for documentation purposes?

16:58 <ifreund> I agree that something like that should exist, I'll probably do it if nobody else has and it becomes a release blocker :D

16:58 <novakane> yeah something like that or something that we would send new user to use as a starting point

16:58 <ifreund> I dont think all users should be expected to write their own WM

16:59 <ifreund> I hope to see a variety of WMs arise which make different tradeoffs

16:59 <ifreund> I would also like to see something in the spirit of awesomewm using lua

17:00 <ifreund> golfing a minimal dwm implementation might be a fun inspiration as well

17:02 <novakane> I sure hope so we'll have a lot of variety, I'm probably gonna go with something simple though :p

17:14 <gbrlsnchs> ifreund: haha I had the same thought about using Lua to arrange the WM layout... it's a rabbit hole, but a fun one

17:15 <gbrlsnchs> but yeah, I also have some ideas geared towards my daily usage, specially for (boring) work 🙄

18:14 <kztx> Do you have a writeup of said usage? Interested to see workflows.

19:28 <gbrlsnchs> kztx: Not sure if directed to me, but my boring daily work requires working on different repositories at the same time. Usually I always have one window with the code and another one with its respective terminal. That's the layout I use for each repository I'm working on. But I also like to keep work stuff attached to the same tag (easier to organize IMO).

19:29 <gbrlsnchs> That said, I would like to "flip" between repositories in the same tag. Probably achievable through some scripting and rivertile currently, but I haven't delved into it yet to see how feasible it currently is. I imagine a WM client would handle it more elegantly.

19:36 <gbrlsnchs> Each tag would have its "dark side" where you could flip all current views in a given tag with the views on that invisible side. Or it could even have a pool of non-visible sets of views. Like a tabbed tag or something. Not like tabbed views, but like tabbed tags instead. I haven't organized my thoughts about it yet though.

20:43 <gbrlsnchs> What I have today in place very primitive but works: I have two layers of tags, one ranging from 1 to 9 in normal mode and the other ranging from 10 to 18 in a "toggled" mode. Switching between them requires changing mode first and then navigating to the flipped layer. A little involved and limited to a double layer. To have a pool of viewsets in a tag would be feasible with a WM client I think.

22:07 <leon-p> totally. a WM can control window visibility directly, so you can use basically any workspace / tag / whatever system you can come up with

22:08 <leon-p> I personally will try to replicate the "viewport" system some old X WMs had

23:05 <kztx> Yeah it was directed to you :) thanks. Yeah that's really cool. I was also thinking of utilizing 1-9 and 10-18 as well but integration with waybar wasn't immediately obvious and I had too many other things to do.

23:05 <kztx> Do you display all 18 tags or 1-9 and also display the mode?

23:38 <gbrlsnchs> kztx: I'm not using any bar at the moment. I've setup a shortcut to show me a notification with date, time and current window name. I use river-tag-overlay to display the tags, and I've configured it to show me 2 rows of 9 tags (first row is normal, second is the toggled mode)

23:39 <gbrlsnchs> I currently don't have any indicators of which mode is on, but toggled mode only has mappings to tag-related commands, so at least I know that if nothing else is working, it's because I'm on that mode

23:41 <gbrlsnchs> as a side note, kudos to leon-p (and contributors, if any) for providing a configurable option for river-tag-overlay in order to allow setting how many tags per row are shown, my overlay is looking beautiful right now

23:42 <gbrlsnchs> I wonder though whether river-tag-overlay will still be a thing after the WM protocol, would that be the case?

23:44 <gbrlsnchs> I ask that because I don't know which protocols river-tag-overlay rely on, and whether they'll be deprecated after the WM protocol is out