Lots of profiles should use GConf?

GNOME Power Manager stores different profiles depending on the serial numbers of the batteries inserted into the laptop. This means we can profile separately, and still provide accurate times when the user only has the second battery inserted “some of the time“.

At the moment, I'm creating two 4Kb comma separated value files for each profile, one for discharge and one for charge, e.g. :

The filename thus becomes profile-3658Q-1234A-charging.csv if we have two batteries inserted.

So, quick question: Should I be using GConf for this? I was under the impression that creating gconf keys with no schema is frowned upon. Is it quicker or more efficient to use GConf over direct file access?

Published by


Richard has over 10 years of experience developing open source software. He is the maintainer of GNOME Software, PackageKit, GNOME Packagekit, GNOME Power Manager, GNOME Color Manager, colord, and UPower and also contributes to many other projects and opensource standards. Richard has three main areas of interest on the free desktop, color management, package management, and power management. Richard graduated a few years ago from the University of Surrey with a Masters in Electronics Engineering. He now works for Red Hat in the desktop group, and also manages a company selling open source calibration equipment. Richard's outside interests include taking photos and eating good food.

One thought on “Lots of profiles should use GConf?”

  1. IIRC, GConf isn't writable in some cases (e.g. certain network setups might have a read-only gconf dir), so I'm not sure that using GConf would be a good idea.

Comments are closed.