-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Config file format #60
Comments
Something like an INI parser is simple enough to bundle with xdpw. Something I've been wondering about is that we maybe want to allow compositors using xdpw to ship some default config files. This way they could customize xdpw appearance and behaviour without having to tell their users to manually copy-paste a config file. We could for instance look for |
cc @ammen99: would that be helpful for you? |
Wayfire by default uses all the tools made for Sway (grim/slurp/swayidle/etc) however I am pretty sure some people that are building more full-featured DEs on top of Wayfire would want to provide their own output chooser. |
You mean a self written one, or a dependency like iniparser?
That would be great! Maybe also |
If we start shipping a config file, which I agree is a good idea, I think it is also time to create some man pages. Right now, the only real documentation is here on the Github Wiki. |
Opened #67 for the man page. |
To offer custom options for an outputchooser we need a config file #59 .
To make it easily readable, we should stick to a plaintext, or sway like config.
I could think of an ini like file, where each section could represent a different portal.
Is there something easy adoptable or an often used library?
The text was updated successfully, but these errors were encountered: