04:41 <LarstiQ> adamcstephens: hah, that's my strategy too ;)

18:10 <pkulak> So, is this silly, if I want different locations and ratios depending on focused tags? It actually seems to work fine, but I'm wondering if I'm abusing the system, or like, making windows resize for 8 frames, etc.

18:10 <pkulak> riverctl map normal Super V spawn \

18:10 <pkulak>     "riverctl send-layout-cmd rivertile 'main-location right' && \

18:10 <pkulak>      riverctl send-layout-cmd rivertile 'main-ratio 0.6' && \

18:10 <pkulak>      riverctl set-focused-tags $((1 << 7))"

19:45 <novakane> pkulak: it would probably better to use or write a layout generator that do per tag layout instead

19:45 <novakane> that's a bit hacky like that

19:49 <pkulak> haha, yeah, you're probably right. Maybe that will be my next project. :D

19:57 <pkulak> Oh, hey, you wrote rivercarro! haha, yeah, you might know. Rivercarro doesn't do per-tag, right?

19:58 <novakane> yeah, it doesn't

20:00 <pkulak> 👍

20:03 <MrBrownFR> hey everyone, i was trying out river and comparing it to hyprland as my main wm, and so far i really like river and its concept of having a separate executable for config and layout managment, however (at least on my machine, i3 7th gen) river uses 10x more cpu than hyprland (ram usage is ~=), does anyone have an idea why is that ?

20:03 <MrBrownFR> on a more technical note, would anyone know if it is possible to write a layout manager which adds animations or rounded corners as of now ?  these aren't dealbreakers like cpu usage, but still nice, and i am more than ok with implementing these myself if it allows me to have the freedom of just switching layout managers to basically switch wm

20:03 <MrBrownFR> which river offers

20:04 <leon-p> high CPU usage likely means river is using the pixman renderer

20:05 <leon-p> layout generators only recommend window dimensions, they are unrelated to rendering / presentation. As of now, no eye candy is present in river.

20:05 <leon-p> river in general should run better since it uses the scene graph API and uses wlroots default render pipeline

20:07 <MrBrownFR> thx, i will look into rendering then

20:07 <MrBrownFR> it definitely feels smoother than hyprland, but at idle its cpu usage is higher, i'm just curious why it might be

20:07 <MrBrownFR> alright, i'll do without then :)

20:07 <MrBrownFR> without eye candy*

20:09 <tiosgz> note that river only uses wlr-scene on git master; last release had no (or close to no?) damage tracking

20:09 <leon-p> ah yeah, true

20:09 <leon-p> kinda forget sometimes that some people do not build river from git master

20:10 <tiosgz> that's what you get if you make releases :P

20:11 <MrBrownFR> if i switch to the dev branch should it run "lighter" ?

20:12 <pkulak> Is master pretty stable? Been waiting for 0.3, but zero damage tracking is a laptop wrecker for sure.

20:13 <leon-p> MrBrownFR: Yes, definitely

20:13 <tiosgz> MrBrownFR: iirc i could even notice my fan spinning less after wlr-scene got into river

20:13 <MrBrownFR> pkulak yes it is, i've been using it for the past 2 weeks and no issues so far

20:14 <leon-p> pkulak: there is damage tracking in old river, it's just a basic start-stop and not a fine grained one. It get's you like 80% of the proper thing.

20:14 <pkulak> Ah, got it. Thanks, guys.

20:14 <leon-p> "Stable" is a loaded term, but crashes are pretty rare

20:14 <tiosgz> s/guys/people/

20:15 <pkulak> My bad! Sorry

20:15 <MrBrownFR> leon-p awesome, i'll try it out ! thanks !

20:15 <tiosgz> not that i helped, but autocorrect is stronger