From: Giuseppe Della Bianca <bepi@adria.it>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu and configuration file?
Date: Wed, 4 Jan 2006 22:22:09 +0100 [thread overview]
Message-ID: <200601042222.09682.bepi@adria.it> (raw)
In-Reply-To: <43BB6224.9020507@vision.ee>
]zac[
> 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...).
]zac[
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.
Gdb
next prev parent reply other threads:[~2006-01-04 21:30 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-31 20:20 [Qemu-devel] qemu and configuration file? Giuseppe Della Bianca
2006-01-03 21:49 ` Giuseppe Della Bianca
2006-01-03 22:02 ` Paul Brook
2006-01-03 22:27 ` Flavio Visentin
2006-01-03 23:31 ` Johannes Schindelin
2006-01-04 2:34 ` André Braga
2006-01-04 21:48 ` Jim C. Brown
2006-01-04 21:39 ` Giuseppe Della Bianca
2006-01-04 5:50 ` martin
2006-01-04 6:44 ` martin
2006-01-04 21:20 ` Giuseppe Della Bianca
2006-01-04 8:52 ` Flavio Visentin
2006-01-04 21:22 ` Giuseppe Della Bianca
2006-01-04 21:50 ` Johannes Schindelin
2006-01-04 22:58 ` Mike Kronenberg
2006-01-04 22:54 ` Flavio Visentin
2006-01-05 20:24 ` Giuseppe Della Bianca
2006-01-04 9:40 ` Jernej Simončič
2006-01-04 21:21 ` Giuseppe Della Bianca
2006-01-04 18:44 ` Mike Kronenberg
2006-01-04 21:22 ` Giuseppe Della Bianca [this message]
2006-01-04 23:41 ` Jernej Simončič
2006-01-04 23:52 ` Mike Kronenberg
2006-01-05 0:04 ` Jernej Simončič
2006-01-05 0:28 ` Mike Kronenberg
2006-01-05 10:49 ` Jernej Simončič
[not found] ` <1136325437.27117.3.camel@fred.ofc.soliddesign.net>
2006-01-04 21:39 ` Giuseppe Della Bianca
2006-01-04 21:50 ` Jim C. Brown
2006-01-05 20:18 ` Giuseppe Della Bianca
2006-01-04 22:07 ` Johannes Schindelin
2006-01-05 20:23 ` Giuseppe Della Bianca
2006-01-04 23:42 ` Jernej Simončič
2006-01-05 15:47 ` Jim C. Brown
2006-01-05 20:35 ` Giuseppe Della Bianca
2006-01-07 13:34 ` Giuseppe Della Bianca
2006-01-07 16:00 ` Flavio Visentin
2006-01-08 13:29 ` Giuseppe Della Bianca
2006-01-08 14:59 ` Johannes Schindelin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200601042222.09682.bepi@adria.it \
--to=bepi@adria.it \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).