On Mo, 2010-12-20 at 10:07 +0000, Patrick Ohly wrote: > This setup with two configs leads to two usability problems: > * How can such a config be created from a template? "syncevolution > --configure foo" would be nice.
Not implemented and not planned for 1.2. Needs more time and thought. > * How can properties of both contexts be modified in a single > command? This is necessary for the single configure command > above and for running a sync. > > Related to this is the question: > * How can multiple source properties be set in a single command? > Not being able to do that has made the instructions for > configuring SyncEvolution as a server unnecessarily complex. [...] > So perhaps the following syntax would be better: > > [<source>/]<property>[@<config>]=<value> (syntax II) > > The ordering of source, property and config is more natural: > addressbook/evolutionsource=My Address Book > syncURL@foo=local://@foo This is implemented. > Make --sync-property/--source-property optional > =============================================== > > A purely cosmetic change. It has irked me for a long time that the > command line was not able to determine automatically what username=foo > means. Also implemented. -- 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] http://lists.syncevolution.org/listinfo/syncevolution
