[copying the list with Ove's permission] On Di, 2011-06-21 at 22:45 +0200, Ove Kaaven wrote: > So I'm trying to update the Maemo GUI to take these DAV setups into > account, and it's getting a bit complicated. I've got a couple of > questions, and it's a bit hard to find the answers elsewhere (plus I > haven't compiled anything newer than 1.1.99.4), so I'll ask you... > > 1) Creation of a configuration from template > The webdav/README says that you should specify the sources you plan to > use, and apparently in both server and client configs. Now, assuming > you're going to add a Google Calendar and Yahoo template for the server > config, do I still need to specify which sources to create?
Depends. These templates are now in the master branch and they are set up so that the Google templates only has "addressbook" as source and Yahoo has "addressbook" + "calendar", but "addressbook" disabled. So you can create the source-config@yahoo like this: syncevolution --configure --template yahoo source-config@yahoo Because the template is deduced from the context name @yahoo, this shortcut also works: syncevolution --configure source-config@yahoo. But then creating the local sync config "yahoo" has to check which sources really work. > How should I > determine which sources to ask SyncEvolution to create for the client > config? Is it possible to find out using --print-config? Yes, --print-config --template will tell you that. Note that for an existing context (like @default) it will include sources already configured inside that context. But because the source-config configs are to be used inside their own context, that won't happen in this case. > 2) Sync method > I suppose that syncURL, WebURL, username, password, and uri should go in > the server config, and database (evolutionsource) should go in the > client config. But when the user wants to set up a source for slow sync, > one-way sync etc, where should it go? Server config? Client config? Both? Careful with the naming here. I prefer "source" config for the side that talks to the server (source-config@yahoo) and "local" or "sync" config for the side that is used for syncing (the one with local:// syncURL). With these names, the real, remote syncURL goes into the "source-config" where it can be used for command line operations like list/import/export/modify items. Username and password should be set in that same config, because these operations need them. uri hardly ever needs to be changed. Just use the default "addressbook/calendar/todo/memo". "database" is currently set automatically in the source config (recent change on master). We still need to add support for listing the WebDAV resources that could be set here. "database" and "backend" in the local config is the same as for SyncML. In fact, it comes from the @default source configs and is shared between all peer configs (including SyncML) defined in that context. -- 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
