5:35 p.m.
On Mon, 2011-10-17 at 20:08 +0000, stephan wrote:
Patrick Ohly <patrick.ohly@...> writes:
>
> On Sun, 2011-10-16 at 23:11 +0200, stephan0h@... wrote:
> > Am 2011-10-16 21:36, schrieb Patrick Ohly:
> >
> > So examples or hints to adequate documentation would be very appreciated!
>
> How about "man syncevolution", online at
> http://syncevolution.org/documentation/syncevolution-usage ?
>
> The question is meant seriously. If that isn't written well enough, how
> could it be improved?
>
> There is no explicit example for setting "database", but there is one
> for setting "sync":
>
> syncevolution --configure \
> sync=two-way \
> memotoo <at> other addressbook
>
> Substitute "sync" with "database", "two-way" with your
database name and
> replace the config/source name with the ones matching your existing
> config and you are done.
>
man syncevolution was my first bet - but maybe you need to have some background
knowledge to fully understand it. Some definition of concepts would be helpful.
What exacatly is a peer, source, database, context, template in syncevolution's
context.
The first paragraphs of the USAGE section are meant to explain the
SyncEvolution specific terms. For example, "A peer is either a SyncML
server (the traditional usage of SyncEvolution) or a client (the new
feature in 1.0)".
Would it be easier to find this when highlighting the new terms or using
a definition list?
I also need to check whether all terms are explained well enough.
And I didn't quite get the relation between configuration files
and the
"syncevolution --configure" statement. Can I do my changes either way? Can I
create a configuration file for a specific source/database? And I missed some
more examples and a list of options/properties.
All of these are fair points. Let me try to answer with a revised README
sometime this week.
Can I do a:
syncevolution --configure databaseuser=<user> password=<pwd> \
funambol@webcal://something calendar
Note that it has to be databaseuser and *database*password. Otherwise
you end up setting the normal password used to log into the peer.
Do you already have the funambol@webcal://something config? The command
above will both modify an existing configuration and create a new one,
based on the "funambol" template. But a new one won't have a valid
username and thus won't be usable.
Note that "funambol@webcal://something" gets simplified to
"funambol@webcal___something" automatically when storing the config in
the file system. You can still reference it via the
"funambol@webcal://something" name.
Hmm, quite a few automatisms which can be surprising :-/
Hope this helps a little and if I can contribute anything please tell
me.
Your feedback is already invaluable. If you are a developer and want to
spend some time on improving SyncEvolution, that of course would also be
welcome.
--
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.