cxreiff
commented
3 days ago Hello! Sounds like a good idea. The code is written in such a way to make custom textures quick to add in the future (texture paths are passed in to the individual screensaver systems during command line argument parsing) so that part should be an easy lift.
I'm hesitant to force people to clutter their dotfiles for such a silly little tool, so I probably would add any desired configuration options as command line flags first and then add a config file fallback as a separate feature with all the same options.
I would like to add some flexibility to the application through a config. This could allow the user to define their own textures and colors to better match their system (such as changing the texture for the logo example, changing the colors of the bubbles, changing the clear color, etc).
On my own setup I added a feature to change the background color to match my terminal and was conflicted if it should be made an argument or if a config file+parser should be added. I personally prefer config files from a ease of use standpoint, but it would add extra scope. A config would also allow users to easily randomly play a screen saver and have it use all their own options.
Let me know of any preferences or insights anyone may have!