config synchronization

Bug #181651 reported by Pierre Slamich on 2008-01-10
Affects Status Importance Assigned to Milestone
Desktop Agnostic Library for GLib-based Projects

Bug Description

This is not detailed enough to be a blueprint , so I'm reporting it as a bug.

The latest version of MacOS (Leopard) enables dock synchronization:
"# .Mac Sync for Dock Items
Make your Dock look the same on all the Macs you use. Change the Dock on one and it will automatically be updated on the others.

There's a synchronization program which is The idea would be to create a dataprovider to make dock syncing possible. As far as I know, there's work going on for Gconf synchronization.

Mark Lee (malept) wrote :

Pretty much all of this information is held in the configuration backend. Currently it's GConf, but I have a branch which allows for more configuration backends, which I would like to merge into trunk soon. This should be taken into account when thinking about this feature.

John Carr (johncarr) wrote :

GConf sync in Conduit is working, but relies on applications listening for their gconf keys changing. This didn't happen when John Stowers tested the original version of the gconf code so panel sync (for example) didn't work without killing and restarting the relevant processes :-(

If Awn will have multiple backends then the correct approach would probably be to give Awn some kind of dbus interface that provided access to this information. Would it be possible for Awn to have this, either built in or (i suppose ideally from the Awn POV) via a plugin/extension?

Neil J. Patel (njpatel) wrote :

Woo this would be pretty cool, backed up by something on Otherwise, we can have an option in awn-manager to backup/restore configuration. Where selecting backup would dump a tar.gz which contains all the necessary info (themes, applets, appearance, launchers)?

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers