GConf

GConf is a used by the GNOME desktop environment system for storing configuration settings for the desktop and GNOME applications. With the release of version 3 of the working environment, it is deprecated and will be gradually replaced by the newly introduced GSettings.

Method

Changes to the settings are made by the gconfd daemon. gconfd monitors the database for changes and apply new settings to all applications that use them. This technique is also known as "auto apply" ( automatically applying ) as opposed to "explicit apply", be adopted in which changes only when the user clicks "OK" or "Apply" button clicked. Also, the term "instant apply" (immediate Apply ) is sometimes used.

The database of GConf defaults to a directory structure with XML files ~ /. Gconf is stored in the directory. GConf may be other backends, such as a database server, use, however storage in XML files is the most common configuration.

The use gconf-editor allows users to change settings manually, it is usually used but not by end-users to define user settings. This should be managed by the application itself.

Architecture

GConf is based on the ORBit -called C implementation of CORBA. The software consists of a Sitzungsdaemon that initializes various sources of configuration schemas when the user logs. Each source is based on a specific backend that provides the key - value pairs in the configuration database. By default, the backend is based on XML. Currently this is the only functioning backend for GConf, next only exists an LDAP backend in the early stage of development. Each source can also be operated in read-only mode to, for example, in corporate networks provide a basic configuration.

The values ​​in the GConf database are accessed via a path of the form / path / to / anwendungsschluessel.

Disclosure of changes

An application that uses GConf, should not query by polling the database, but a callback function (callback ) Register for the desired key, which is the Model View Controller paradigm. Each time an application changes the bound to this key value, the callback functions are called.

Schemes

An application that uses GConf should provide to each key that it invests in the GConf database a description. This ' scheme ' mentioned configuration, metadata is also stored in the configuration database. The scheme should contain a ( localized if possible ) descriptive text, a valid value type and a default.

Interfaces

How many libraries of the GNOME platform can also be accessed on GConf in various programming languages ​​such as C, C , Perl, Java, and Python.

Normally the GConf is not edited directly by the end user. Access is indirectly about the application, which deposited its settings. However, certain additional options are not configurable via a graphical interface and can be set only in the registry. The developers and advanced users are purpose tools such as the command -line tool gconftool or gconf-editor graphical tool available.

363165
de