Gnome Configuration (GConf)

To transform a GConf configuration element into an APOC component and path, the following mappings are performed:

• All GConf related components are prefixed with org.gnome.

• /apps/<subdir>/... is mapped to the component suffix apps.<encoded subdir>.

• /desktop/<subdir>/... is mapped to the component suffix desktop.<encoded subdir>.

• /system/<subdir>/... is mapped to the component suffix system.<encoded subdir>.

• /extra/<subdir>/... is mapped to the component suffix extra.<encoded subdir>.

• /extra/<keyname>/... is mapped to the component suffix extra.

• Keys not following the naming conventions are mapped to the component suffix ooc.<encoded subdir> if they feature a subdir and ooc otherwise.

• /schemas/<keypath> is mapped to the component part schemas, and then the above rules apply for the rest of the key.

• GConf key subdirs mapped to component parts are encoded to comply with component parts restrictions.

Example A–1 Gnome Configuration

• /apps/myapplication/sampleSub.Dir/sampleSetting becomes org.gnome.apps.myapplication/sampleSub.Dir/sampleSetting,

• /desktop/sampleDir/sampleSub.Dir/sampleSetting becomes org.gnome.desktop.sampleDir/sampleSub.Dir/sampleSetting,

• extra/sampleSetting becomes org.gnome.extra/sampleSetting,

• /sample.Dir/sampleSetting becomes org.gnome.ooc.sample.Dir/sampleSetting,

• /schemas/apps/gnome-setting/sampleSubDir/sampleSetting becomes org.gnome.schemas.apps.gnome-setting/sampleSubDir/sampleSetting.