Add CLI Options for Config File and Output Path

[partisani]

As the title says, this tool is too inflexible to be used correctly in most scenarios that involve scripts, especially ones embedded in places like a NixOS configuration.

Some things that should be changed:

• Theme and configuration should be allowed to load from files other than ~/.config/gowall/config.yml via a command line argument
• The user should be allowed to change where the output file(s) is/are saved

btw i still use this tool instead of other ones because this one is better

[Achno]

Hello there @partisani,
The output path for the images instead of the default gowall dir being configurable is understandable.

Could you explain why config.yml path should be configured? What problems did you face with the standard config files in ~/.config ?

i will address these enhancements when the exam season is over because i'm overwhelmed right now, i hope you understand.

It will be ready by the time v.0.2.0 is released though

[partisani]

i will address these enhancements when the exam season is over because i'm overwhelmed right now, i hope you understand.

No pressure or anything, it is ok.

Could you explain why config.yml path should be configured? What problems did you face with the standard config files in ~/.config ?

I found that generating the colorscheme from a script or something else would require the configuration file to be overwritten everytime the colorscheme changed, which lead me to do this as a workaround. And always pass base16 as the theme everytime i called gowall.

In my case, doing this forces Home-Manager to create and (re)build a derivation only to regenerate gowall/config.yml everytime, while some other tool called dipc allows the colors to be passed at runtime via command line arguments. (to the detriment of other features i would need)

[Achno]

@partisani Okay since i had some free time i implemented these enhancements locally, and i just want you to give me feedback

1. You can now specify the OutputFolder in ~/.config/gowall/config.yml : The below sets the directory to ~/MyImages

OutputFolder: "MyImages"
themes: ....

2. You can now load themes in runtime via giving a .json file in combination with the usual -t flag for the theme

gowall convert ~/Pictures/img.png -t test.json

You can use a relative path with ~ with the json file like this :

gowall convert ~/Pictures/img.png -t ~/clr/test.json

The test.json must have the following interface :

{
    "name": "MyTheme",
    "colors": [
        "#F5E0DC",
        "#F2CDCD",
        "#F5C2E7",
        "#11111B"
    ]
}

What do you think ?

[partisani]

I think now the only thing missing is something like -o <output file> (to define one output for each input file), but the rest already works very well!

[Achno]

@partisani

I think now the only thing missing is something like -o output file

Oh, that already exists, someone made an issue here : #22 and i already implemented the functionality. Must have forgot to put it in the docs. You must get the version from the main branch though.

Well, i will test the above enhancements for more bugs and push it to main when i have more time. In 3 weeks once the exam season ends v.0.2.0 will be released with all the goodies and shortly after , NixOS should be up to date in a day too ;)

[partisani]

Then that's it! Thanks!

[Achno]

Reopening to close it when i push the enhancements to main

[Achno]

Implemented in 992690a closing