10:38 <miffi> hello, i wanted to ask about https://github.com/ifreund/river/issues/24 . Is there any chance the patch to the gtk repo will ever get merged. This would be a nice enhancement to have.

15:42 <cmoi11> Hi there. Just tested this project and it looks pretty cool. Is there a statusbar that can be used with river?

15:42 <ifreund> cmoi11: Indeed, there's a couple with river support: https://github.com/ifreund/river/wiki/Recommended-Software

15:44 <cmoi11> Ah thanks. I hadn't the wiki yet!

15:45 <ifreund> there's not a whole lot there yet, it's world-editable so feel free to expand it if you feel inspired :P

15:48 <cmoi11> Sure. I really like that there is an alternative to sway finally! So thank you for your work :)

15:48 <ifreund> you're most welcome, though river's not the only sway alternative

15:49 <ifreund> wayfire and hikari exist too, as well as a few others that aren't as mature yet :)

15:51 <ifreund> also river itself still has a good ways to go before it reaches non-window-management feature parity with sway

15:53 <cmoi11> Yeah but it looks quite good already.

15:54 <cmoi11> I checked out other Tiling Compositor Project but so far none of them I really liked.

15:55 <cmoi11> Sway is good and stable but I never liked i3.

16:01 <cmoi11> How do you develop river, if I may ask?

16:02 <cmoi11> I mean in what environment and how to test it when you make changes.

16:02 <leon-p> cmoi11: write code, compile, then try it out. Just like every other project.

16:03 <leon-p> you can run river inside a parent compositor, so testing is simple

16:03 <leon-p> you don't even have to manually interact with it. When I worked on the resize move and snap functionality, I scripted the riverctl commands

16:05 <cmoi11> Ok. Is this also possible from X or do I need to be on wayland?

16:05 <ifreund> cmoi11: I test most things in a nested river session

16:05 <ifreund> you can run it nested in X if your wlroots is built with support

16:06 <ifreund> as for an editor, I use kakoune, kak-lsp, and zls

16:07 <leon-p> Vim and emacs also provide pretty good editing environment for zig. I used both extensively in the past.

16:07 <ifreund> "sway is good and stable but I never liked i3" <--- this is pretty much why I started river :D

16:07 <ifreund> got hooked on the wayland part of sway but hated the i3 part

16:08 <leon-p> same here

16:09 <anthony25> same :}

16:10 <anthony25> I don't like i3, don't really like its philosophy, and as sway is following it, well…

16:10 <anthony25> so I stay on bspwm for now

16:11 <ifreund> anthony25: if I may ask, what feature of bspwm would you miss the most if river didn't support it?

16:11 <anthony25> I can tell you what I don't like on sway

16:11 <leon-p> a little more "bling" than sway would also be nice. A bit too early in rivers development to think about it, but we technically already have one animation, so maybe in the future we can add more fancy things :)

16:12 <anthony25> otherwise it's a bit difficult to answer

16:12 <anthony25> on sway I find the tiling way too rigid

16:12 <anthony25> worded weirdly: I find the tiling too much rigid

16:13 <anthony25> meaning that on bspwm, I can do a preselect and say exactly how I want the next window to be

16:13 <ifreund> yup, that's the classic manual vs dynamic tiling conflict

16:13 <anthony25> half top, half bottom, half left, half right

16:13 <anthony25> or any percentage from the current select window

16:14 <anthony25> I can also do a preselection, move to another desktop, and say "I want to send this window where I preselected"

16:14 <anthony25> and it just sends the window there

16:14 <anthony25> also, things on sway that I don't like but am not too much bothered by it is the fact that they like to decide of the behavior of the wm for me

16:15 <anthony25> meaning that "oh you don't use this desktop anymore? we're gonna remove it automatically, you don't have any choice"

16:15 <anthony25> "why would you want to keep an empty desktop?"

16:16 <anthony25> because I want to have a static list of desktops

16:16 <anthony25> also, one thing I never found anywhere outside of qtile

16:16 <anthony25> is a pool of desktops shared by all screens

16:16 <anthony25> I did it by hacking for bspwm

16:17 <anthony25> meaning that in sxhkd and in my bar, I move desktops from one screen to another if the one I want is not on my selected screen

16:18 <anthony25> and I also have a thing where it will swap desktops between 2 monitors if the desktop I want is currently active on another monitor

16:19 <leon-p> moving all visible views from one output to another is a valid use case we may need to consider in river

16:21 <anthony25> this way I don't have to think at which desktops are currently attached to which screens, I can just have every desktops everywhere

16:21 <anthony25> yeah not having that would really be a blocker for my desktop computer

16:21 <anthony25> on my laptop, with one screen, I don't care

16:22 <leon-p> well, in river it will not be possible to move a "workspace" from one output to another, because we just don't have workspaces. However we can cartainly move n views to another output while keeping their relative order

16:24 <leon-p> depending on how river-control-v2 will work, this may be doable from an external client even

16:24 <leon-p> but I should probably finish work on river-layout before thinking about the next protocol :D

16:31 <anthony25> hehe

16:35 <ifreund> Better multiple output support is definitely something I plan to look into, but I need a second monitor and more free time before that will happen

16:35 <ifreund> for now it's pretty much just what dwm does which is OK but not great

16:42 <anthony25> well, I could move my lazy ass and help also for that

16:43 <leon-p> Even just trying multi-monitor out and providing some ideas on how to improve the experience will already be helpful I think

16:44 <ifreund> awesomewm and xmonad might be good sources of inspiration as well

16:44 <ifreund> they both are still pretty close to the dwm model river currently uses afaik

16:46 <ifreund> velox decided to disallow views from having multiple tags, which means that multiple outputs can share the same tags which is another interesting solution

16:46 <ifreund> the real problem is that I don't know what I want yet though, since I haven't played around with multiple monitors and dynamic tiling enough yet