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

[Jakub M. <ja...@o2...>]

Some comments from the "beginner's" point of view:

> Frontends may use the default configuration file to show a nice GUI.
> This could include GUI for AdvancedOptions, and GUI for selecting
> specific Resources.
>
> Would it be possible to implement some mechanism, which would allow us
> to have more than one default configuration file per plugin?

I guess there can be only one "default" file ;)
Isn't it possible for the GUI to use only the necessary options from all 
that are declared in the file?


> As an example: Future versions of mozilla-sync may support only vformat,
> whereas the current version supports xml-format.
> It would be great if OpenSync could carry different configuration files
> for this, and select the correct one depending on the actual blueZync it
> is connecting to.
>
> I could of course create just one default configuration file with both
> Formats, but a GUI would not be able to figure out that this particular
> version of the external plugin will only support one of them.

Maybe, as a temporary solution, just make thin new version of a plugin exist 
as a new plugin, with another configuration file. Then, there's no need to 
change the Opensync logic. Does it make any sense?


> I have never figured out what the plugin's get_version is used for.
> Could it be used here?

This is a good point. I found a statement:
"The format/conversion and main plugin modules that are part of a plugin now 
each have a function int get_version(void). At the moment this function must 
return 1. "
Is this "MUST" still so importart?


Bloosky
ja...@o2...