mirror of
https://github.com/JakeStanger/ironbar.git
synced 2026-07-11 10:15:20 +01:00
[GH-ISSUE #544] [Workspace module] river tag support #177
Labels
No labels
A:Build
A:CI
A:Client
A:Config
A:Core
A:Documentation
A:Documentation
A:IPC
A:Testing
A:UX/UI
blocked
BREAKING CHANGE
duplicate
good first issue
GTK4
help wanted
invalid
M:Battery
M:Battery
M:Bindmode
M:Bluetooth
M:Brightness
M:Cairo
M:Clipboard
M:Clock
M:Clock
M:Custom
M:Focused
M:Keyboard
M:Launcher
M:Menu
M:Music
M:Music
M:Music
M:Network Manager
M:Notifications
M:SysInfo
M:Tray
M:Volume
M:Workspaces
partially resolved
P:Critical
P:High
P:Low
P:Medium
pull-request
T:Bug
T:Bug
T:Core Enhancement
T:Module Enhancement
T:New Module
T:Question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
JakeStanger/ironbar#177
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @aquifolly on GitHub (Apr 17, 2024).
Original GitHub issue: https://github.com/JakeStanger/ironbar/issues/544
Is your feature request related to a problem? Please describe.
i'm looking to switch to river at some point but would like to keep the majority of the other parts of my setup, including the bar, and from what i can see, there is no support for river's tag system
Describe the solution you'd like
support for river's tag system
Additional notes/links
https://codeberg.org/river/wiki/src/branch/master/pages/How-tags-work.md
@yavko commented on GitHub (Apr 17, 2024):
It seems river uses Wayland protocols for everything. Looking at i3bar-river, it seems to generate Wayland bindings. I think it's tag code could be used as a reference https://github.com/MaxVerevkin/i3bar-river/blob/master/src/wm_info_provider/river.rs
@JakeStanger commented on GitHub (Apr 17, 2024):
River using a different workspace model and different communication approach compared to Sway and Hyprland means this will be non-trivial to implement.
Definitely open to this, and if anybody wants to take it on go for it, but I will not be able to get to this for some time.
@yavko commented on GitHub (Apr 24, 2024):
Why was this closed lol
@JakeStanger commented on GitHub (Apr 24, 2024):
Because I got #554 and #544 mixed up whoops, sorry