"Defaults" button in every settings screen
ndrwrdck at googlemail.com
Fri Dec 9 13:40:13 CET 2011
On 12/09/2011 03:44 PM, Nick Schermer wrote:
>> The link between the dialog box and the xfconf sub-tree isn't always that
>> obvious. For example if we wanted to change settings of a single launcher in
>> the panel, we'd first have to know its ID (which may change) and then
>> save/restore properties matching the pattern:
> Plugin-id's never change.
My mistake, sorry. When I added new plugins to the panel they were
occasionally getting IDs lower than the highest existing ID, so I
assumed the IDs are reused.
> Per-module is better, where each module ships a file (or maintainer in
> the profile-manager) where settings are stored. For example the
> xfce4-panel xfconf config is useless without content of
> ~/.config/xfce4/panel and keyboard settings has properties in 2
> channels (some for a lot of other xfce4-*-settings plugins).
>> - What if there are cross-dependencies or conflicts? (some options depending
>> on the compositing being enabled etc.)
> The code should protect that, not the setting in a channel.
It feels like working around limitations of xfconf by pushing
configuration management back to the applications.
I don't say it is bad solution (it may be the only practical one) but it
just doesn't look like a nice design in my eyes.
More information about the Xfce