Paul Rensing wrote:
Hi there.
I am testing out using Opensync between Evo2 and the file-sync plugin. I actually have a use for this: with some manual work, I can copy my calendar from Evolution to Outlook/Exchange (yes, I know about Connector, but I don't like it.). Maybe I will eventually try to write an Exchange plugin, but not now.
However, the file-sync plugin writes out the old VCARD/VEVENT formats (1.0 and 1.0 respectively), but I want the newer versions (1.1 and 2.0). I think I understand that the output format that is coming out is the first one that the format tree traversal found that works.
Is there some existing mechanism to choose between formats? Would it make sense to improve the file-sync plugin to be able to select formats?
we already had a discussion internally about this but didnt quite come up with a solution. The problem is more generic actually:
The file-sync plugin can store binary data (read: it can store everything). It uses its own format named "file". as long as there is a valid converter from your format (vcard 2.1/3.0, vcal 1.0/2.0) it can store the data. The path finding algorithm will just pick the first valid path it encounters. But what if this path isnt the one you want? (Like your case)
i think the solution should consist of 2 parts: 1. write something that can actually enable/disable certain paths on the conversion (so that you could disable the vcard2.1->file path). This has to be generic and work for all formats/paths. 2. write something so users can configure this enabling/disabling of paths. This could either be file-sync plugin specific or be generic.
i didnt have a good idea yet how to present this to the user so it is easy to manage (maybe we could use the filter interface here?)
Paul Rensing
signature.asc
Description: OpenPGP digital signature
