On Fri, 2012-02-17 at 07:24 +1300, Jane Atkinson wrote: > On 16/02/12 21:56, Patrick Ohly wrote: > > The workaround that I have in SyncEvolution (open+close+open) > > really is just a hack. A proper solution has to be in EDS, > > something like "open and refresh now, even if it takes a while". > > I could file a bug against EDS, though I suspect I'll be told that > it's an upstream problem (and probably not likely to be fixed in time > for release, unfortunately).
It's indeed unlikely to be fixed soon. It's nevertheless a good idea to report the problem, either in your distro or upstream. > > Do you absolutely need the data in Evolution? It's not currently > > working yet, but it would be feasible to let SyncEvolution > > synchronize a phone with a CalDAV server directly. > > > > Good question. There are two things that have held me back here. One > is figuring out the config necessary (laziness on my part?). The other > is that I've been using bluetooth, and it sounds as though direct > CalDAV sync involves setting up other servers as well. No, just a CalDAV server, SyncEvolution (not running as server) and a SyncML capable phone should be enough. But there's still a bit code missing (reading credentials for CalDAV without the usual target-config config), so you cannot try it at the moment. > As a separate issue, Thunderbird / Lightning doesn't have a method of > dealing with memos, which Evolution does. If anyone knows of another > lightweight (i.e. not a full PIM) way of reading and editing memos, > I'd be interested to hear about it. I don't know. -- 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
