On Mon, 2013-12-02 at 15:01 +0200, Alberto Mardegan wrote: > One question (please bear in mind that I don't know much about SE, so I > might be missing something here): why do we need to configure the > account in SyncEvolution?
Primarily because the necessary code hasn't been written yet. > Couldn't SE simply enumerate all the enabled accounts it supports, and > synchronize them? Yes, the permanently running syncevo-dbus-server could host such a listener and trigger the necessary actions. However, what exactly those actions are needs to be defined and/or configured. For example, should it also create local databases? In EDS or Akonadi? Should it sync all remote databases that it gets access to, without asking the user? At the technical level, some more things need to be sorted out. What shall happen when a sync is running and the corresponding account gets removed? Currently SyncEvolution prevents that by only allowing config changes when no sync runs. Should there still be a sync and target config? We might be able to get all information from the account system and then could pretend to have a traditional config which never really exists on disk. The advantage of a real configuration is that some additional config settings (log level, backup) might only be possible there. However, the ~/.config dir of the sync config is also (ab)used for storing meta data about the sync. Where would that data live then? -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ SyncEvolution mailing list [email protected] https://lists.syncevolution.org/mailman/listinfo/syncevolution
