Active window title
thom-cameron opened this issue · 6 comments
Hi,
I've just switched away from using X with dwm, slstatus, etc. to Wayland with river and i3bar-river. So far the setup is working great - thanks for creating this project.
One thing I miss from slstatus though is the name of the active window being displayed alongside the tag indicators. I like the window borders to be unobtrusive, so sometimes seeing the name of the selected window helps out.
I'm not familiar enough with Wayland or the architecture of river (or other Wayland wms) to know whether this is a feasible request or not. Is this something that could be implemented in i3bar-river?
Cheers.
This can be implemented in i3bar-river, but i don't think it should. Instead, use the status command. For example I use i3status-rs, it has a "focused window" block which works under wayland.
Ah, like I said I'm not familiar enough with the ecosystem yet. Sounds like you're absolutely right. I'll do that, thanks!
This can be implemented in i3bar-river
I would love to know how? I have tried using the 'block' but it's just not the same. THis is the one feature I'd love to have, active window title alongside tags.
Even if you dont intend to implement this option, I'm happy to modify my local source code if you can explain how?
This can be implemented in i3bar-river
I would love to know how?
Using the wlr-foreign-toplevel-management-unstable-v1
protocol.
Using the
wlr-foreign-toplevel-management-unstable-v1
protocol.
Is there a guide on how to use this? I wouldn't know where to start.
Thanks
EDIT
I wonder why an additional wlroots protocol is needed when other wayland bars are already capable of this function.
I'll keep reading, but if you get time and can explain it to me like I'm 5 that'd be awesome.
Is there a guide on how to use this? I wouldn't know where to start.
You may use the i3status-rust's implementation as a reference.
Here is the protocol documentation: https://wayland.app/protocols/wlr-foreign-toplevel-management-unstable-v1 (it is a bit more pleasant than reading raw xml file).
I wonder why an additional wlroots protocol is needed when other wayland bars are already capable of this function.
Other wayland bars use this exact protocol, if not WM-specific side channels (like sway IPC, etc.)
explain it to me like I'm 5 that'd be awesome
Ideally you should have some experience in writing wayland clients. But hey, this is an opportunity to gain it. I would recommend reading the protocol docs (link above), look at the examples which show how to use the wayland library used in this project, and creating a small test project to play with it. I would also recommend reading this "book", which explains the core of wayland.