the problem is that afaik evolution does not provide a api to access its
address, tasks and calendar. they are accessed by working on the files
where they are stored (~/evolution/local/...).
Actually, the DO have an API to access these through the backend
(wombat). This is what the Evo plugin use
hi rob,
the problem is that afaik evolution does not provide a api to access its
address, tasks and calendar. they are accessed by working on the files
where they are stored (~/evolution/local/...).
the connector source dont appear there (for a obvious reason) and
therefore cannot be accessed. i