obsolete: GConf editor
|Last release||3.2.6 / January 22, 2013|
|License||GNU Lesser General Public License|
Changes to this system are controlled by GConfd, a daemon. GConfd watches out for changes to the database, and when they are changed, it applies the new settings to applications using it. This technology is known as "auto-apply", compared to "explicit-apply", which requires users to press an OK or Apply button to make changes come into effect. The term "instant-apply" is sometimes used, compared to plain "apply".
The GConf database by default uses a system of directories and XML files, stored in a directory called
~/.gconf. GConf can also use other backends, such as a database server, but XML file storage is the most common configuration.
The application gconf-editor is provided to allow users to change settings manually, but it is not usually used for end-user preferences. These should be provided by the application, but hasn't in some cases, causing upset among users (see main gconf-editor article for details).
GConf is currently based on the C implementation of CORBA named ORBit. Its architecture consists of a session daemon that initializes various sources of configuration schemas on user login. Each source is based on a specific backend that translates the key and value pairs that compose the configuration database; the default backend is based on XML. At this time, this is the only working backend for GConf, although an LDAP backend existed in embryonic form. Each source can also be set to read-only, in order to create a default basic configuration, e.g. in a corporate network.
The values inside the GConf database are indexed using a path string in the form of
When writing an application that uses GConf, one should never directly poll the database. Instead, one should attach a callback to a given key, thus using a Model-view-controller paradigm. Each time an application changes the value bound to a specific key, the notification callbacks will be invoked.
An application using GConf should provide a description for each key it creates inside the GConf database. This configuration meta-data is also stored inside the configuration database, and is called a schema; it could contain a (possibly localized) descriptive text, the valid type of the value bound to a key, and a default value.
- "GNOME Goal: Gconf to GSettings migration". GNOME. Retrieved 2014-11-05.