Ticket #764 (new task)

Opened 6 years ago

Last modified 5 years ago

Add capabilities support for evo2-sync

Reported by: dgollub Owned by: dfriedrich
Priority: normal Milestone:
Component: Plugin: evolution Version: 0.38
Severity: normal Keywords:
Cc:

Description

Capabilities support for evo2-sync actually should only consists of determining the version of evolution and reporting it via the OpenSync? version interface:

        const char *evo2_version = magic_evo_determine_version_function();
        OSyncVersion *version = osync_version_new(error);
        osync_version_set_plugin(version, "evo2-sync");
        osync_version_set_softwareversion(version, evo2_version);

And write capabilities and description files for evo2-sync which fits the evolution capabilities.

Change History

comment:1 Changed 6 years ago by dgollub

  • Owner changed from dgollub to dfriedrich
  • Component changed from OpenSync to Plugin: evolution2

comment:2 Changed 6 years ago by tuju

  • Milestone changed from 0.40 to 0.37

comment:3 Changed 6 years ago by tuju

  • Milestone changed from 0.37 to 0.38

comment:4 Changed 6 years ago by tuju

  • Milestone 0.38 deleted

non-core plugins wont block releases. thus milestone == NULL.

comment:5 Changed 5 years ago by tuju

  • Version changed from 0.36 to 0.38

comment:6 Changed 5 years ago by ianmartin

The evolution plugin is really a connector to the evolution-data-server not just Evolutions local data store.

So the capabilities are different if you are using google calender or OWA or the local data store.

Therefore until you have connected to the data store it is impossible to tell what the capabilities of the resource are. So capabilities must be generated dynamically much like syncml will have to.

comment:7 Changed 5 years ago by felixmoeller

Work has been done on this with r4413. I do not know whether is is finished.

Note: See TracTickets for help on using tickets.