Re: [Evolution-hackers] Might be a generic ESourceExtension useful?

[Milan Crha <mcrha redhat com>]

On Tue, 2013-02-05 at 08:01 +0100, Milan Crha wrote:
> ...What about solving such issue with a generic ESourceExtension, which...

After a little discussion with tristan on IRC, not a generic
ESourceExtension, but an API added directly to ESource, similar to
"property" API on the old source.

And with respect of examples, one is the 'contacts' calendar backend,
which duplicates .c code for the extension in both eds and evo. The
files (e-source-contacts.c/.h) are not the same in gnome-3-6,
interestingly.

And example of the other side in eds/libedataserver full of unrelated
source extension, residing extensions for calendar and book ESources
beside each other, while the other code for book and calendar is divided
into its own folders, which makes it less mess. (My opinion.)

	Milan