Re: [SyncEvolution] Overview of sythesis field mapping needed - need to determine specific case HTTP server and N900

As people following my notes already know, I am doing some testing trying to gain confidence in the specific configuration of HTTP server and N900 It is desirable to do this in the most efficient manner possible and not repeat effort. Towards this end, I wish to understand how the synthesis engine xml configuration files work. There is a quite complete, but totally overwhelming, pdf file on the synthesis web site. What seems to be missing is a sort of quick overview - in particular the recent syncevolution release notes refer to re-organizing the xml config files to make each file be reserved for a particular role An overview of the directories placed on the wiki would be quite helpful. I see directories for datatype files, and remote rules, and scripts. One thing, I am trying to figure out is how the mapping is defined... I suspect it is all considered in an incoming context, and I need to go to each client directory to find the appropriate xml. For example, for syncevolution the syncevo/configs directory seems to be the place to start looking. There is a remoterules directory. In this context what is remote - client or server side? Where would I find the maemo version of this? Are their any special cases for maemo yet? I only use a small number of fields but want to check they are all preserved- that will save a bit of testinghttp://syncevolution.org/development/pim-data-synchronization-why-.... --Jeff