On Wed, 2009-09-09 at 23:25 +0200, Patrick Ohly wrote: > I'll continue to work on the sync-related methods. Because this is in a > different part of the file, we should be able to merge changes easily.
Hurray! It syncs! Spending some time on a plane or train away from new email is a very productive way to move ahead with implementation work ;-) The code on the "dbus-api" branch now implements running a sync session. GetStatus/Progress and the corresponding signals are implemented, but currently are only updated/fired at the start and end of a sync. I'll add that soon, after making the Connection interface work. The missing parts are all marked with "TODO" comments in "syncevo-dbus-server.cpp". Yongsheng, I suggest that we fill in these blanks together. You can start with the get/set config methods, then pick some of the other missing pieces. Ping me via chat or email first so that we don't start working on the same thing. > Storing the temporary configuration is unclear at this point. We can > leave out that part of the API for the time being. I introduced some Session members where these settings can be stored to be used in Session.sync(). See commit d74901682fc2870a919184be8c1c224d221ca092 Author: Patrick Ohly <[email protected]> Date: Mon Sep 14 22:33:30 2009 +0200 syncevo-dbus-server: implemented Session.Sync() parameter handling The Session.Sync() parameters are a special case of temporarily overriding the source properties of all or some sources. This patch uses the new per-source config filters to transfer the parameters to the core sync engine. This patch also introduces Session members for temporary config changes, which is another way of setting these and other parameters. These Session members must be set in SetConfig(temporary=true) calls (not done yet). -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
