9c0caae1c2
future plans, etc., please see http://www.gnome.org/start/2.4/. This commit represents work done by adamw, bland, and myself as well as many other contributers: Koop Mast <einekoai@chello.nl> Akifyev Sergey <asa@gascom.ru> Franz Klammer <klammer@webonaut.com> Øyvind Kolbu <oyvind@kebab.gaffel.nu> Thomas E. Zander <riggs@rrr.de> Jeremy Messenger <mezz7@cox.net> Without these contirbuters, and our faithful users, GNOME 2.4.0 would not be possible. Please check the FreeBSD GNOME site for any FreeBSD gotchas, as well as general FAQs and documentation (GNOME 2.4 updates to be posted soon). The best way to upgrade so that you get all shared library dependencies is: portupgrade -rf -m BATCH=yes atk portupgrade -R -m BATCH=yes gnome2 Approved by: portmgr (kris, will, myself implicitly) Requested by: re as well as many other users
22 lines
955 B
Text
22 lines
955 B
Text
GConf attempts to leapfrog the registry concept. It's a library which provides
|
|
a simple configuration data storage interface to applications, and also an
|
|
architecture that tries to make things easy for system administrators.
|
|
|
|
Here are some of the features of GConf:
|
|
|
|
* Replaceable backend architecture.
|
|
|
|
* Configuration key documentation. Applications can install documentation
|
|
along with their configuration data, explaining the possible settings and
|
|
the effect of each configuration key.
|
|
|
|
* Data change notification service. If configuration data is changed, all
|
|
interested applications are notified. The notification service works
|
|
across the network, affecting all login sessions for a single user.
|
|
|
|
* The client API is very abstract.
|
|
|
|
* GConf does proper locking so that the configuration data doesn't get
|
|
corrupted when multiple applications try to use it.
|
|
|
|
WWW: http://www.gnome.org/projects/gconf/
|