Gustavo Sverzut Barbieri <[EMAIL PROTECTED]> writes:

> I'm starting this thread to discuss a XML Structure to be used as
> Freevo internal config files.
> 
> I suggest brainstorming before we start the structure. So I begin:
> 
> - 2 part document:
>    * "Model": here we define data types, grouping, limits, validations,
> warnings, info, description. Something like the comments we have in our
> config files, but in parseable way, so we can (someday) auto-generate
> the interface and handle data based on this.
>       # Maybe this is needed just to build GUI and validate data?
>       # Maybe this can hold the default values?

Sounds to me like XML Schema.


>    * "Contents": the data filled in by user based on the previous item.
> This will be something like our files (freevo_conf, local_config) right
> now. 
>       # Maybe we need 2 contents, one with the defaults and one with
> user settings. just like freevo_conf & local_conf? This make parsing
> easy, we just need to parse both files and override settings.

XML Schema can provide the default values. 
The user settings would be stored in th XML-file (using the XML Schema).

generateDS.py seems like the module for this job. 
(I have never used it myself)

http://www.rexx.com/~dkuhlman/#SECTION002390000000000000000


-- 
Eirik Meland

A: Top posters.
Q: What is the most annoying thing on Usenet?


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Freevo-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freevo-devel

Reply via email to