Re: [Evolution-hackers] Regarding ESource and ESourceExtension
- From: Matthew Barnes <mbarnes redhat com>
- To: Tristan Van Berkom <tristanvb openismus com>
- Cc: evolution-hackers gnome org
- Subject: Re: [Evolution-hackers] Regarding ESource and ESourceExtension
- Date: Mon, 08 Oct 2012 07:55:32 -0400
On Mon, 2012-10-08 at 18:40 +0900, Tristan Van Berkom wrote:
> Is it intended that the frontend must know what extensions are
> supported by a given backend ?
What extensions are you worried about, specifically? And what's the use
case for configuring them by hand?
This page explains which extensions are typically present in a given
type of key file: https://live.gnome.org/Evolution/ESourceFileFormat
The various "config" modules in Evolution [1] serve as configuration
backends for the account editor and the "New Address Book" and "New
Calendar" dialogs. Each module knows what extensions are supported by
its respective Camel/E-D-S backend.
Matthew Barnes
[1] http://git.gnome.org/browse/evolution/tree/modules
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]