config

The settings engine: declarations, levels, stores and the resolver.

Detailed description

A schema declares each setting one time. A resolver walks the levels of the schema and reports where a value comes from. Stores hold the values of one level. See config-ui §CFGM-2 to §CFGM-8.

Classes

Class What it is
ChangeNotifier Two change signals of one resolver
ChoiceProviders Run-time choice lists that apps register by name
Choices Values an `Enum` setting accepts (config-ui §CFGM-2b)
IHistory Undo history of a document that owns a level (config-ui §CFGV-3a)
IStore One level's storage, addressed by setting id (config-ui §CFGM-4)
Level One place a setting value can be set, in priority order
MapStore A level backed by a plain map keyed by setting id
NumericSpec Numeric facts of a number setting (config-ui §CFGM-2)
Relevance Whether a setting applies now, and why not (config-ui §CFGU-5)
Resolved Outcome of walking the cascade for one setting (config-ui §CFGM-4)
Resolver Walks a schema's chain of levels and reports where each value came from
Schema Every declaration of one app or library
SchemaPreset A named preset that a schema ships with (config-ui §CFGM-8)
Scoped A value that a level either sets, or does not (config-ui §CFGM-4)
SettingDef One setting, declared one time
Snapshot An immutable map from setting id to resolved value
WriteRateLimiter Newest-wins write coalescing with a trailing flush
WriteResult Outcome of a write or a clear through the resolver (config-ui §CFGM-5)

Namespaces

Namespace What it is
testing Fixtures for the tests of the settings engine and the settings window
ui Settings page: the item model, the views, the page, the framed window and the config.* tasks
In this section