[WIP] [✨ FEATURE] use ~/.config to save all the configs/options

[snisarg]

Is your feature request related to a problem?
Makes it easier to share configs across devices or with friends who I've been pushing to use FluidVoice. :)

Describe the solution you'd like
Use a typical .yaml or .json file to save all the config options inside the standard ~/.config/FluidVoice/?? folder so it can be synced and shared.

Describe alternatives you've considered
The UI still controls the configs; this is just another way.

Additional context
Any other context or screenshots.

[altic-dev]

did you check this out? :)

[snisarg]

Ah I missed this. However this isn't the same, this is having a way to read/write directly from a single file; so external modifications are read as well.
In any case, this is a pretty minor requirement, don't prioritize this haha!

[altic-dev]

I understand the ask. It's a v good one! I will keep this in the TODOs to work on soon :) config.toml incoming!

[florinungur]

Still wanted.

Do file values seed the defaults once, or win on every launch? @snisarg's ask points at the second, which needs the UI to show those controls as read-only or as overridden. Otherwise a UI edit and the file disagree, with nothing on screen to say so.

No workaround exists today. On macOS the only route is defaults write com.FluidApp.app <key> <value> against undocumented key names, plus killall cfprefsd and a restart. A symlinked plist breaks the first time cfprefsd replaces the file, and BackupService import runs through a file picker, so no script applies it at startup.

(I raised the same idea at #991 before I found this issue, and have closed it as a duplicate.)