---- Reported by email@example.com 2010-04-13 20:31:24 +0000 ----
This is from http://bugzilla.moblin.org/show_bug.cgi?id=8753
Description From pohly 2009-12-18 01:29:55 PST (-) [reply]
It is a very common complaint that SyncML in most installations only supports
one calendar, address book, task list, memo list per device. This is not a
limitation of the protocol, more like the lowest common denominator that is
Our own sync UI for Moblin follows the same model, although SyncEvolution
itself could handle more than one instance of each data category if the peer
did (evolutionSource config option).
For those cases where the peer doesn't, it would be nice if SyncEvolution could
join data from multiple databases if the peer supports only one database, then
when receiving updates back correctly sorted them into the the right database.
Here's a user giving more background information:
ScheduleWorld has such a feature for calendars, based on the CATEGORY property.
We could adapt a similar system and perhaps even make it so that n:n calendar
synchronization within the same sync session becomes possible.
Another use case for such a join/dejoin are devices which exchange events and
tasks via one single URI (https://bugs.meego.com/show_bug.cgi?id=8752). This has already been implemented and now
needs to be generalized.
---- Additional Comments From firstname.lastname@example.org 2010-08-23 00:13:56 +0000 ----
friesoft <email@example.com> changed:
What |Removed |Added
I agree that this is an important feature, but would prefer to keep "High" priority limited to those issues that need to be worked on next. This one here is not currently one of those, unless someone steps up and wants to work on it.
--- Bug imported by firstname.lastname@example.org 2012-07-29 20:36 UTC ---
This bug was previously known as _bug_ 719 at https://bugs.meego.com/show_bug.cgi?id=719
-- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.
You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/SyncEvolution/syncevolution/issues/155.