From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33)
	id 1BsodC-0003GM-B3
	for qemu-devel@nongnu.org; Thu, 05 Aug 2004 16:14:30 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33)
	id 1BsodA-0003GA-Qk
	for qemu-devel@nongnu.org; Thu, 05 Aug 2004 16:14:30 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.33) id 1BsodA-0003G7-NH
	for qemu-devel@nongnu.org; Thu, 05 Aug 2004 16:14:28 -0400
Received: from [207.217.120.84] (helo=gull.mail.pas.earthlink.net)
	by monty-python.gnu.org with esmtp (Exim 4.34) id 1BsoZB-0001o9-1L
	for qemu-devel@nongnu.org; Thu, 05 Aug 2004 16:10:21 -0400
Received: from 0-1pool56-60.nas3.oklahoma-city1.ok.us.da.qwest.net
	([63.156.56.60] helo=computername)
	by gull.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 1BsoZ9-00077d-00
	for qemu-devel@nongnu.org; Thu, 05 Aug 2004 13:10:19 -0700
Message-ID: <001101c47b28$26c353e0$3c389c3f@computername>
From: "syeng" <syeng@yango.us>
Date: Thu, 5 Aug 2004 15:09:09 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Subject: [Qemu-devel] Suggestions for Windows version of Qemu
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

1) The source should be included, and optionally installed.  Or at least
made available as a single package with whatever patches needed, etc.  Both
the official release, and the daily builds on FreeOSZoo.

2) There should be a "whats new" or changelog or something included so we
can know what's new.  Especially important for the daily builds.

3) The command line utils, such as qemu-img.exe, mkqemuimage.exe, etc.,
should prompt the user for the options, if there aren't any on the command
line.  And there wont be when the user clicks on the program instead of
using a command line.

4) Instead of using a command line for everything, perhaps use a .INI file
for the settings?  (Or perhaps.txt might be easier for people to edit.)
There are several public domain ini managers around and qemu probably
wouldn't need anything fancy anyway.