Re: [Gramps-devel] Why gconf upgrade?

[Don A. <do...@gr...>]

I believe you are misunderstanding the upgrade.

We are upgrading *away* from gconf. If you have existing settings in
gconf, the upgrade procedure is supposed convert the gconf settings to
the .ini settings. After this, it should ignore the gconf settings.

This is done simply because it is silly to support two different methods
of saving program settings.

So, yes, we need the upgrade. But the upgrade is only to transition the
user's settings from the GNOME specific settings to GNOME independent
settings.

Don

On Sat, 2008-01-12 at 23:51 +0100, Benny Malengier wrote:
> Having looked at gconf upgrade, I can't help but wonder why we bother
> for 3.0.=20
> I see the following problem which I cannot test however as I don't
> have gconf:
>=20
> Upgrade is done every time GRAMPS starts. This because it is code in
> the __init__.py file of Config (not at the moment, but once Raphael
> fixes the wrong tab change, it will run again on every load). I cannot
> help but thinking that will lead to problems. Does this not overwrite
> things for GNOME users?=20
>=20
> Looking at the few preferences we have, why do we bother to upgrade
> gconf settings?=20
>=20
> Benny