翻訳と辞書
Words near each other
・ Gdańsk Zaspa railway station
・ Gdańsk Zaspa Towarowa railway station
・ Gdańsk Św. Wojciech railway station
・ Gdańsk Żabianka railway station
・ Gdańska Street, Bydgoszcz
・ Gdański Bridge
・ Gdańskie Wydawnictwo Oświatowe
・ GCN5L2
・ GCNA
・ GCNT1
・ GCNT2
・ GCO
・ GCOA
・ Gcobani Bobo
・ GCompris
GConf
・ Gconf-editor
・ GCOS
・ Gcov
・ GCP
・ GCP Infrastructure Investments
・ GCPC
・ GCpedia
・ GCR
・ GCR Audio
・ GCR Class 1
・ GCR Class 11B
・ GCR Class 11E
・ GCR Class 11F
・ GCR Class 1A


Dictionary Lists
翻訳と辞書 辞書検索 [ 開発暫定版 ]
スポンサード リンク

GConf : ウィキペディア英語版
GConf

GConf was a system used by the GNOME desktop environment for storing configuration settings for the desktop and applications. It is similar to the Windows Registry.
It was deprecated as part of the Gnome 3 transition. Migration to its replacement, GSettings and dconf, is ongoing.〔(【引用サイトリンク】title=GNOME Goal: Gconf to GSettings migration )
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).
== Architecture ==
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 /path/to/application/key.
The proper way to access the GConf database held by the GConf daemon is to use the GConfClient GObject-based class.

抄文引用元・出典: フリー百科事典『 ウィキペディア(Wikipedia)
ウィキペディアで「GConf」の詳細全文を読む



スポンサード リンク
翻訳と辞書 : 翻訳のためのインターネットリソース

Copyright(C) kotoba.ne.jp 1997-2016. All Rights Reserved.