Implement preferences window
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kupfer |
Fix Released
|
Medium
|
Unassigned |
Bug Description
A preferences window should be implemented
Ulrik knows how to implement the autostart option.
The rest of the options are such that they should be written to the config file in $XDG_CONFIG_
The default config is installed somewhere in $XDG_DATA_
Preferences should be written to the first file if they deviate from the default.cfg. Preferences set to default values should not be written anywhere; this way, user's who didn't change anything will get new defaults with new versions (This is _the_ sensible way for most applications to behave. And the reason why kupfer installs default.cfg)
As of this writing it should have these options:
[First tab]
[ ] Start automatically on log in
[x] Show icon in notification area
Keybinding "<Ctrl>space"
[Second tab]
List all plugins with name and description and author and version. Choose to disable, or include direct or in catalog. See default.cfg for what the default looks like.
Separate list for directories to include in catalog and directly. Also DeepDirectories (none by default) and choice of depth.
=======
Original report
The /home/vadi/
kupfer should copy the default preferences from /usr/local/
Changed in kupfer: | |
assignee: | nobody → Ulrik Sverdrup (ulrik-sverdrup) |
status: | Confirmed → In Progress |
Changed in kupfer: | |
status: | In Progress → Fix Released |
The way the config files are organized is in preparation for an implemented Preferences dialog.
It is tricky to get preferences right, but I want to do it this way; we separate default config from user-set config. This way only nondefault configuration is saved into the user configuration folder, and default config that changes between versions will be active unless previously overridden. I think that architecture is superior, and I hope it's going to work out that way.