Originally I really liked the idea of having one config file per block, as this would allow block scripts to be distributed together with their configuration very easily. It also is, to some degree, separation of concerns.
However, in practice I found this quite cumbersome. It also makes backing up the configuration more tedious. Now that I've decided to move the block scripts out of the configuration directory, it seems like a reasonable thing to get rid of the block configuration directory entirely, which means to eliminate the need for block configurations.
Still, we need some way to configure blocks - the solution is obvious: go with the same approach as caption, where every block can have a configuration section in the main config file. The special section [bar] would then be reserved and used for the bar itself, while every block would be prefaced with a section named after the block, for example [datetime].
domsson
commented
4 years ago
Originally I really liked the idea of having one config file per block, as this would allow block scripts to be distributed together with their configuration very easily. It also is, to some degree, separation of concerns.
However, in practice I found this quite cumbersome. It also makes backing up the configuration more tedious. Now that I've decided to move the block scripts out of the configuration directory, it seems like a reasonable thing to get rid of the block configuration directory entirely, which means to eliminate the need for block configurations.
Still, we need some way to configure blocks - the solution is obvious: go with the same approach as caption, where every block can have a configuration section in the main config file. The special section
[bar]would then be reserved and used for the bar itself, while every block would be prefaced with a section named after the block, for example[datetime].