On 06/22/2011 08:52 PM, Patrick Ohly wrote:
I'm open for suggestions. We can still get it right for 1.2. Here are
some options:
1. sync config (used for syncing, contains the relevant "sync" mode
for sources) + target config (referenced by a sync config in
local:// syncURL)
2. local config (uses local databases) + target config (referenced
by a sync config in local:// syncURL)
3. sync config (used for syncing) + source config (use for
accessing the sources)
4. client config (uses templates for clients) + server config
(accesses the server)
5. server config (acts as SyncML server) + client config (SyncML
client)
I've thought of them as "local config" and "remote config". But I
suppose "sync" and "target" would work too.
(Besides,
webdav/README says the local config should use the "SyncEvolution
Client" template, which might also justify calling it client config.)
That a client template is used here is a technical detail that might
change at some point.
I hope not, since then the GUIs would need to be changed again...
Anyway, you didn't answer my actual question: for configuring slow sync,
one-way sync, or disabling sync, where should the "sync" configuration
go? Server/source config? Client/local config? Both?
Sorry, missed that part. The "sync" property needs to be set in the
"sync/local" config.
OK.
I guess my updated GUI is pretty much ready - apart from not being sure
if I'm going to need to handle config migration somehow (like put up a
prompt that launches syncevolution --migrate). And, of course, not
tested against what syncevolution 1.2 is going to be...
Thanks,
Ove
_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution
