On 3/27/06, Shane Stixrud <shane@xxxxxxxxxxxxx> wrote:
>
> If for every "key": its default, possible values (on, off string, float
> etc..) is readily accessible and for every key there is a simple
> description much of this complexity is eliminated.
>
Yes, I think this is what's missing: if for each config file there was
a schema things would be better. For example I've pasted below a clip
from a schema of a web microsite generator I'm working on. This not
only describes the data, it allows me to make a web based editor on
the fly, by specifying the appropriate widget to edit an item an and
help text.
Joe.
<global-schema>
<field id="theme" datatype="enum" name="Theme">
<option id="autumn" name="Autumn" />
<option id="spring" name="Spring" />
<option id="winter" name="Winter" />
<option id="test" name="Test" />
</field>
<field id="title" datatype="string" name="Title"
helptext="The title of the website. It is used
in the header of very page." />
<field id="slogan" datatype="string" name="Slogan"
helptext="A slogan or strap line which appears
under the site title on every page."/>
<field id="left_image" datatype="image" name="Left block image."
helptext="The left block image. 300x200 pixels." />
<field id="custom_css" datatype="string" name="Custom CSS"
widget="widget:textarea;rows:8;cols:60"
helptext="Custom CSS" />
</global-sc
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
