> see no reasons why to choose anything else than xml for it. We have tons of
> xml libs that can be used for gui's (think perl, tk, python etc...).
The xml configuration file are too much hard to consult and to modify
directly from a human.
The idea to use additional library and therefore to add obligatory
prerequirement to qemu, is not an idea that have appeals for me.
> Certainly better every dude writing it's own XuPeRpArSeR that will be
> broken and compatible after a major change in qemu ...
> Another choice would be the pure rc (just 'item = value' lines) without
> any supersmart blocks.
My program and library can manage from the basic ' key value'
to the configuration file of xfree/xorg (and multiple keys, groups with name
in one key) without particular problems.
As an example:
Qemu set up a function of callback, calls one function of my library for
demands one group (or some groups) and one key (or some keys), my library,
using the callback function it gives back the value (or some values).
Then qemu it will make what he must make, and I do not see particular problems
of incompatible with a major change in qemu.
> xml style or rc style, please no hack in betweeen :)
All depends from functions that are wanted to be added at qemu, without the
group not it goes beyond simpler configurations.
Qemu-devel mailing list