twelve has quit [Remote host closed the connection]
_whitelogger has joined #river
sentry has joined #river
Snetry has quit [Ping timeout: 260 seconds]
Nosrep has quit [Ping timeout: 248 seconds]
<Ireozar>
falafool: you could probably use CSS, can't check rn though sadly
letherlick has joined #river
letherlick has quit [Ping timeout: 272 seconds]
alexherbo2 has joined #river
catman has quit [Quit: WeeChat 4.6.3]
catman has joined #river
alexherbo2 has quit [Remote host closed the connection]
alexherbo2 has joined #river
alexherbo2 has quit [Remote host closed the connection]
flower_ has joined #river
lordmzte has joined #river
<lordmzte>
Have we ever considered using the scenefx renderer for River? Is there any consensus regarding this?
<fleischie>
I don't care much for eye-candy. Would it be possible to allow eye-candy enthusiasts to leverage this instead of the default renderer?
Ireozar has quit [Read error: Connection reset by peer]
Ireozar has joined #river
<lordmzte>
Seems like that might be an unreasonable amount of maintenance effort :P I'm not someone who insists on having eye-candy, but I certainly won't say no either :D
<ifreund>
lordmzte: I'm not interested in maintaining that kind of thing
<ifreund>
also, we very much want the wlroots vulkan renderer for color management
letherlick has joined #river
ramblurr has quit [Ping timeout: 252 seconds]
letherlick has quit [Ping timeout: 272 seconds]
letherlick has joined #river
letherlick has quit [Quit: Client closed]
letherlick has joined #river
letherlick has quit [Ping timeout: 272 seconds]
letherlick has joined #river
letherlick has quit [Ping timeout: 272 seconds]
<leon-p>
also minor eye-candy will be possible with the normal wlroots renderer anyway
<leon-p>
especially thanks to the new toplevel capture thing, some animations can now be done client side by a river WM, as soon as all of that is supported
<leon-p>
not sure if wlroots will ever support that transparency background effect protocol, but if it does, every wayland server built on wlroots might get stuff like blur For Free(TM)
<leon-p>
the only thing we can't have easiely is things like rounded corners, since doing that properly (i.e. including antialiasing and fitting borders) will require a custom shader
<leon-p>
and you can always just use client-side decoration if you want things like rounded corners and drop-shadows right now
libzip-so has joined #river
libzip-so has quit [Client Quit]
<pkap>
Is there a plan to add the new toplevel capture protocol in the near/midterm future or is that something for after the river-rwm release?
<ifreund>
pkap: I don't plan on implementing it for river 0.3.x but would merge a PR if someone did so
<ifreund>
I will implement it for master eventually after rwm is merged
<pkap>
ifreund: That's great news. Maybe I'll give it a shot.
<ifreund>
cool, just make sure you work off of the 0.3.x branch :)
<ifreund>
pkap: acutally, is the wlroots side of things part of 0.19 or is it unreleased?
<ifreund>
might need to wait for 0.20
<pkap>
ifreund: It's unreleased.
<pkap>
That gives plenty of time to develop and test it in river.
<ifreund>
Yeah, it would have to wait for wlroots 0.20 to land in 0.3.x though of course
<pkap>
Yeah of course. Would be nice if we have a PR ready once that happens.
<pkap>
But looks like this will be months, so I guess there's no need to rush.
<pkap>
ifreund: I would create an issue now to track progress on this.
<ifreund>
Sure
andyrtr_ has joined #river
andyrtr has quit [Ping timeout: 276 seconds]
andyrtr_ is now known as andyrtr
<leon-p>
I think there is also still some need for the image capture clients to catch up anway
<pkap>
leon-p: There's already a draft PR for the wlr portal.
<pkap>
Which is important one, arguably.
Nosrep has joined #river
Guest42 has joined #river
<leon-p>
I'll be very happy when I finally see all of those hacky scripts that just crop a normal screenshot die
<Guest42>
hey, having some trouble getting rules to work for Librewolf windows. I want browser windows to tile, but I want popups, such as this window title "Extension: (Bitwarden Password Manager) - Bitwarden — LibreWolf" to float. I've tried every -title glob i can think of. "Extension: *", "*Bitwarden*", even "Extension: (Bitwarden Password Manager) -
<Guest42>
Bitwarden — LibreWolf" the entire thing, still does not work. -app-id librewolf works every time. not sure where i'm going wrong in trying to target window titles
Guest9 has joined #river
<Guest9>
this is on 0.3.10, but same behavior on 0.3.9. , also apparently irc disconnected so if there was a response I did not see. unsure why
Guest42 has quit [Ping timeout: 272 seconds]
<leon-p>
Guest9: Firefox (and therefore its Forks) sometimes (in some versions under some circumstances) set window title and app-id /after/ the window has been mapped
<leon-p>
river rules are only triggered during map
<leon-p>
you can use `lswt --watch` to find out if this is the case for you
<Guest9>
must be specific to title in this instance, as -app-id "librewolf" functions as intended.
<Guest9>
good idea, i was using lswt but did not use --watch
<Guest9>
yep, started as (null).
<leon-p>
yeah in that case this can't be worked around, sorry
<gbrlsnchs>
leon-p: I wonder if that's something a WM could handle transparently by handling the 'parent' event...?
<Guest9>
firefox strikes again. dang
<leon-p>
gbrlsnchs: perhaps, although I do not know whether firefox sets the parent property for popup windows
<leon-p>
although a WM could also just implement filters that act on every title / app-id change
<Guest9>
i seem to recall it being handled well enough some time ago on hyprland, but i haven't touched that in over a year so hard to tell anymore
Beer has joined #river
belanthor has joined #river
<leon-p>
oh it is totally possible to react to title changes after a window is mapped, that's just not how river rules are implemented
<ifreund>
we should arguably apply filters on title change as well as map
<ifreund>
this comes up fairly frequently and is always confusing
Beer has quit [Quit: Client closed]
ramblurr has joined #river
Guest7 has joined #river
Guest7 has quit [Client Quit]
<leon-p>
should that be done unconditionally or should filters have a flag that can be used to set them to apply always?
belanthor has quit [Quit: Leaving]
<ifreund>
leon-p: maybe we need a flag, not sure what problems would arise in practice
<ifreund>
but also I'd rather just work on rwm and make this not my problem(tm)
<ifreund>
also, janet-wayland is like 90% done so its time for me to write a wm I can daily drive
<ifreund>
at that point I'll probably just merge rwm to master and split off river-classic
lxkraken has joined #river
letherlick has joined #river
<leon-p>
what is the plan for input configuration? still interested in the input config protocol we talked about a year ago?
<leon-p>
what's missing in my native guile wayland impl is a way to define methods at runtime which isn't an ugly hack. Methods are also just instances of a class stored in a special list (which in turn is an instance of the <generic> class) so it's possible to hackily imitate all that, but it's not a very nice way of doing things
<leon-p>
also there is a good chance I just go back to zig+chicken, since I need to call at least pixman and xkb which is probably nicer from zig
letherlick has quit [Quit: Client closed]
twelve has joined #river
lxkraken has quit [Quit: Client closed]
twelve has quit [Ping timeout: 260 seconds]
ingenarel has joined #river
<ingenarel>
hiii chat, kinda new here, switching to river from hyprland
<ingenarel>
is anyone using river with waybar?
<ingenarel>
i tried to use sway/hyprland's workspace rules for river tags, but couldn't find a way to do so
<ingenarel>
yes i saw, that is the window module, i'm actually not talking about window modules, for sway/hyprland workspaces, i can use window rules to change how the workspace is shown
<ifreund>
leon-p: yeah, I still think an input config protocol is the best option
<ifreund>
though we could probably get away with a config file or something on the compositor side, exposing it to clients is more flexible and it would be nice UX to configure everything in the same place
<ifreund>
I'm not going to block merging to master on that though
<ifreund>
All I want before I merge to master is a protocol where I don't forsee the need for breaking changes and a full compositor-side implementation
<ifreund>
It's fine if its not 100% feature complete
letherlick has quit [Quit: Client closed]
letherlick has joined #river
ingenarel has joined #river
<ingenarel>
hey, me again, is there any way to launch something with specific window rules?