Patrick Ohly wrote: > On Thu, 2010-03-25 at 18:13 +0000, Frederik Elwert wrote: >> Since I’m currently moving Genesis from commandline usage to D-Bus >> communication (sync/reports done, configuration coming next), I’d like >> to know how automatic sync can be used via D-Bus. After a quick look, I >> didn’t find it in the docs (but maybe I was looking at the wrong >> places). > > It's enabled by setting the following sync properties, then starting the > syncevo-dbus-server, or setting them via D-Bus directly. Directly > editing config files while the D-Bus server is running is a loophole - > the server will not detect that (could be added, of course).
Apropos... I was thinking how to solve the problem QA reported: that autosync works like a black box: you just turn it on and have no idea if it's working or when it's going to work. I liked the idea of showing "last synced an hour ago, syncing again in 30 minutes" to solve this the best. Looking at the server code, it doesn't seem like I can make that sort of estimates though (not without additional information). Or maybe I can, if I show something more vague when it seems that a autosync time would be close: "...syncing again soon"? Any other bright ideas? Some already presented were: * show the interval in UI: this is ok, but doesn't really fill me (the user) with confidence that something is happening * mention the sync method in the last-synced message: "Last synced an hour ago (automatic sync)": This still doesn't work right after I enable autosync... - Jussi _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
