On Nov 21, 2003, at 2:30 PM, Biot Olivier wrote:
Or we may include versioning information to a preference, so we know
when it
is introduced (or removed or renamed). This will be required in cases
where
a preference is created, then removed, then created again but with
another
meaning given to it.
Presumably that versioning information would be written to the
preferences file.
Another thing we may want to do in addition to the versioning of
preferences, is provide a "preference scrubber", that gets rid of old
preferences.
It's called the "Save" button. :-) (Old preferences aren't saved when
you save your preferences. Of course, doing so saves *all* preference
settings, including those you haven't changed.
Arguably, it should save only those that differ from the values they
have after reading in the system-wide preferences file but before
reading in the user preferences file, so that if the default setting of
some preference changes, or a system-wide preference file is changed,
it changes the value of any preferences to which you haven't done
anything; however, once you change a preference, you might then want
some way of saying "revert to the default or system-wide setting for
*this* preference" other than editing your preferences file, and you
might also want some way of knowing whether a preference is set in your
preference file or not, otherwise it might be a bit hard to figure out
how your settings will end up - two users that see the same values in
"Edit->Preferences" might get *different* behaviors if a default or
system-wide setting changes.)