Re: [Opensync-devel] Could we have several versions of a plugin configuration file?

[Henrik /K. <he...@ka...>]

Juha Tuomala wrote:
> On Mon, 9 Nov 2009, Henrik /KaarPoSoft wrote:
>> A member of a group has a configuration file.
>>
>> Would it be possible to implement some mechanism, which would allow us
>> to have more than one default configuration file per plugin?
>>
>> This would make sense, if different versions of a plugin supports
>> different AdvancedOptions, different Resources, etc.
> Correct me if I'm wrong, if I say that:
> - the file is in XML format
> - X in XML stands for eXtensible
> - tools reading the XML don't care about stuff they don't understand.
> - thus the XML, the configuration file is always backwards compatible?
> - thus the same file can be used regardless of versions?
The challenge is not so much the syntax. Even the schema is the same for 
all plugin configuration files. And a Frontend would probably let the 
OpenSync library do the parsing anyway.

The challenge I am thinking of is this: How can a Frontend present a 
nice GUI to configure ANY OpenSync plugin?

Maybe I am wrong, but the way I do it in blueZync is to look at the 
advanced options and creating GUI for those, and look at the resources 
and create GUI for the resources defined in the default config file.

Obviously a Frontend may have specific knowledge of specific plugins and 
create an even better GUI, but it would be nice if a Frontend could 
automatically create a GUI for any OpenSync plugin automatically.

/Henrik