On Fri, 2011-10-21 at 10:52 -0400, David Hampton wrote: > On Thu, 2011-10-20 at 20:39 +0200, Patrick Ohly wrote: > > That is indeed the case. Use the same sync URL as for the > > SyncEvolution client and the "addressbook", "calendar", "todo", "memo" > > names as URIs. > > $ syncevolution --configure --template SyncEvolution_Client \ > --sync-property remoteDeviceId=9123456789ABC-123456789ABCDEF \ > --sync-property username=david \ > --sync-property password="123" \ > --sync-property uri=addressbook \ > galaxys2 > ERROR: '--sync-property uri=addressbook': no such property
I know why I stopped insisting on the --sync/source-property option ;-) Should have been "--source-property". Fixed. > I tried again without the uri property and the command was accepted. Yes, I'm wondering whether it is really needed. Probably not (only resets explicitly set uris to their defaults, which happen to be the same). > I can now successfully sync my phone contacts, calendar and todos. I > had to change the default server paths in Synthesis to match the the > URIs you listed, but it all works now. What are the default paths? The configuration line above could be changed so that the default SyncEvolution names as well as the Synthesis paths are accepted. > > Should there be a third HOWTO covering the "phone <-> SyncEvolution > > HTTP SyncML server with Evolution" case or can you think of some > > changes to the existing HOWTOs which avoids the need for such a third > > one? > > The steps are very similar, but I've tried the wording a couple of > different ways and it keeps getting awkward. That's what I feared. > Mostly because you have > actual command line examples for the two syncevolution case, and I can > only come up with a broad waving of hands on how to configure the phone > client. (Unless I tailor it specifically for the Synthesis android > client and then readers can extrapolate to their own devices.) Perhaps > one page with two sets of steps on it? I've attached some text below. That's a good start. I'd probably make it a bit more general and talk about "any device with a SyncML client" instead of "Android phone". Let's clarify the question above and then change the text accordingly. -- 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
