[–] amano-kenji 2y ago ↗ For years, I used i3pystatus, but I was frustrated by the fact that it's not flexible or extensible.I considered using i3blocks, but I didn't like the limitations of its INI-style configuration.I wanted the flexibility of a proper scripting language.Thus, I created https://codeberg.org/amano.kenji/j3blocks which comes with a few built-in modules.j3blocks requires you to write a janet script. You can shoot your foot with scripting, but it is very flexible. You can easily write your own j3blocks modules after you learn j3blocks.https://codeberg.org/amano.kenji/j3blocks-extra has extra modules. One of them is pipewire-node which lets you watch and control pipewire nodes on i3bar or swaybar.pipewire-node shows you changes to a pipewire node immediately. You can control a pipewire node through mouse clicks or unix domain socket messages.The whole system is very flexible, but it took two weeks to polish it to the point where I can talk about it.
1 comment
[ 0.26 ms ] story [ 12.7 ms ] threadI considered using i3blocks, but I didn't like the limitations of its INI-style configuration.
I wanted the flexibility of a proper scripting language.
Thus, I created https://codeberg.org/amano.kenji/j3blocks which comes with a few built-in modules.
j3blocks requires you to write a janet script. You can shoot your foot with scripting, but it is very flexible. You can easily write your own j3blocks modules after you learn j3blocks.
https://codeberg.org/amano.kenji/j3blocks-extra has extra modules. One of them is pipewire-node which lets you watch and control pipewire nodes on i3bar or swaybar.
pipewire-node shows you changes to a pipewire node immediately. You can control a pipewire node through mouse clicks or unix domain socket messages.
The whole system is very flexible, but it took two weeks to polish it to the point where I can talk about it.