Re: Configuration made simple...
> % /etc/conf/*.xml
> Yeah, this is it. Now let's talk about
> the schema. It should be something like
> <description>Time in
> minutues 'till screensaver starts
> <comment> JSmith 2002-01-01:
> changed to 10</comment>
> <comment>Tom: 2002-02-05:
> prefer to use 15</comment>
What needs to happen it that the configuration definition and the actual configuration are separate. The actual value for the configuration can be stored in the applications default format.
What is required is 3 things:
1) A standard API for accessing configuration information. This means that any configuration editor can be written in any language and not have to worry about the underlying format. This may be already available.
2) Parsers to give access to existing configuration files through the standard API.
3) Some schema to define the possible configuration for any application and an API to this schema. This would include your type and description as well as more complex things like occurance of an option (once, twice, zero_or_more...) and validity checks.
Using the three above, configurators, be they GUI, curses or text based, will be able to read, parse, validate and write config files for as many applications as people write plugins for.
Open to suggestions...