i3 blocks manager about i3blocks-contrib HOT 5 CLOSED

Are you suggesting something that just downloads the blocks and puts them in a convenient location for you, or something that actually enables/disables blocks in your status line? The former seems reasonable to implement, the latter seems too complicated as many blocks require special setup and/or user configuration.

from i3blocks-contrib.

I was thinking of the latter, but you're right, it will require efforts, and unfortunately I won't be able to contribute on this.
I'm not sure, however, if the former would really save the user some time. You would still need to search for the plugin, get its name/url, and write it down, instead of copy-pasting the code directly.

Thanks for the quick answer anyways, I appreciate the fast support :)

from i3blocks-contrib.

I agree that just a downloader wouldn't be much help. Perhaps there is a middle ground I'm not seeing, but I think most of the blocks require some user knowledge to set up. Only the "dumb" ones could be truly automated, so a manager would be tedious and involved.

I do wonder how much of a barrier the setup is. Do people view the READMEs and think "oh that's too complicated" and give up?

For now I don't see myself even attempting to implement a block manager. Of course if another contributor has the drive to do the hard part I'm willing to help however I can.

from i3blocks-contrib.

We could have an .i3blocks.d directory, each blocklet would be a file starting with a number (to sort them)

ie: ~/.i3blocks.d/01-mpd.conf ~/i3blocks.d/02-battery.conf etc

With another directory somewhere where all the blocks are available, the "manager" would just symlink them to our .i3blocks.d directory (more or less)

But then i3blocks would have to add a feature to load blocklets like this.

from i3blocks-contrib.

Closing because not feasible anytime in the near future due to unique setup required by each blocklet. Feel free to reopen in future if enhancement becomes feasible.

from i3blocks-contrib.