On Thu, 2009-10-15 at 11:24 +0100, Ghee Teo wrote: > Rodrigo Moya wrote: > > On Tue, 2009-10-13 at 23:06 +0200, Luca Ferretti wrote: > > > >> 2009/10/13 Rodrigo Moya <[email protected]>: > >> > >>>> Ryan is a bit sad to not get feedback on his proposal, so a bit more > >>>> seriously: I think what we probably need is a migration plan. Should we > >>>> move all the code from gconf to dconf in one cycle (if possible)? Should > >>>> apps implement migration for the data in gconf? etc. > >>>> > >>>> > >>> I think it makes sense to do the migration for all the apps at once. > >>> > >> Are we speking about: > >> a) all GNOME Desktop applications > >> b) all applications hosted on git.gnome.org > >> c) all GNOME/GTK+ apps using GConf :) > >> > >> ?? > >> > >> Serius: what's the plan for thirdy part applications? > >> > > > > if dconf listens to changes in gconf, 3rd party apps would just need to > > link to glib/GSettings instead of libgconf, and their migration would be > > done automatically, right? > > > If dconf listens to changes in gconf, does not 3rd party apps would just > work? > This is a question of run-time interoperability, is dconf inter operate > with gconf clients? > Please clarify this. I can see lots of reasons why 3rd party doesn't > want to re-link to glib/GSettings :) > this is for doing the migration, once apps are ported to GSettings API (and hence not linking against libgconf), their settings should be in the dconf database automatically, because dconf migrated them
That's how I would see it _______________________________________________ desktop-devel-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/desktop-devel-list
