You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[FEATURES/IDEAS] QoL feature proposals for ex-waybar users: inhibit-idle, time+more actions for media button, more consistent button icon properties
#770
Open
ppenguin opened this issue
Feb 14, 2025
· 0 comments
Here some ideas, could probably add some more and should probably be split out to separate issues. Maybe just initiate at-will/as needed and link back to this issue as the summary.
media: visible play-time/remaining time and/or better configurability (format string with info-fields) for the media bar.button. Also we may want some kind of polling that ensures that new players show, maybe the number of active players as (x), or that we can select between multiple players with a button action
... ...
Some other ideas:
would it be feasible to implement custom modules more "pluggable", so that one would be able to register any dir containing a "valid" module by just referring to it from the config file?
more consistent property handling of bar.buttons, i.e. all would have the same basic properties, including e.g. active_icon.{text(emoji),color, background} / inactive_icon.*. Buttons that don't have multiple activation states would just only evaluate the active one and ignore the rest. This would make it easier to have common component templates and less boiler plate per component.
home-manager module: just use "to json conversion" of config attribute sets, which sacrifices deep option checking but guarantees that we can express any supported feature in the module.
The text was updated successfully, but these errors were encountered:
Here some ideas, could probably add some more and should probably be split out to separate issues. Maybe just initiate at-will/as needed and link back to this issue as the summary.
Coming from Waybar, what I'm missing:
x
), or that we can select between multiple players with a button actionSome other ideas:
active_icon.{text(emoji),color, background}
/inactive_icon.*
. Buttons that don't have multiple activation states would just only evaluate the active one and ignore the rest. This would make it easier to have common component templates and less boiler plate per component.home-manager
module: just use "to json conversion" of config attribute sets, which sacrifices deep option checking but guarantees that we can express any supported feature in the module.The text was updated successfully, but these errors were encountered: