Patrick Ohly <patrick.ohly@...> writes:
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:
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 <at> 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 <at> webcal://something" gets simplified to
"funambol <at> webcal___something" automatically when storing the config
in
the file system. You can still reference it via the
"funambol <at> 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.
I managed now to disable all non-local calendars by putting a
"evolutionsource = Personal" in default/sources/calendar/config.ini
It also appears to me that my assumptions where wrong as I surely cannot
sync one calendar in funambol with more than one calendars in evolution.
Some more research in necessary.
Regarding syncevolution's terms and conecpts: Maybe a small diagram
would be helpful. Maybe I can contribute that once my understanding
is good enough :-)
cheers,
stephan