--- Comment #7 from pohly <patrick.ohly(a)intel.com> 2009-11-20 02:23:18 PST ---
(In reply to comment #6)
(In reply to comment #5)
> I suggest to solve this problem by referencing other *source* configurations
> instead of *backends*. Then these other source configurations are defined
> normally. A sync where a supersource is active is treated like a sync where
> each of the involved normal sources is active (database dumps, reporting, ...).
> The configuration could look like this:
> type = virtual:text/calendar
> evolutionsource = calendar,todo
Do you mean add another dummy source folder reference other sources to be
This simplifies my problem but adding duplicated configuration(in
case calendar, todo, and calendar+todo are mostly duplicated). This is not very
nice and may confuse user. For example is it meaningful to fire a sync with a
Nokia phone asking two-way sync for calendar and slow-sync for todo? Mostly
this does not work.
[calendar+todo] is indeed mutually exclusive with both [calendar] and [todo].
This is something that users need to know. Depending on how we implement this
"virtual" backend, this semantic can be checked by SyncContext.
In the sync-UI, we can hide the complexity for the default case.
Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.