qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fabrice Bellard <fabrice@bellard.org>
To: jm@poure.com, qemu-devel@nongnu.org
Cc: Rudi Lippert <Rudi@LYRIKpage.de>
Subject: Re: [Qemu-devel] Qemu workstation
Date: Mon, 05 Apr 2004 21:31:43 +0200	[thread overview]
Message-ID: <4071B41F.3040201@bellard.org> (raw)
In-Reply-To: <200404051155.31051.jm@poure.com>

Hi,

I am interested by a GTK GUI for QEMU and I think it should be commited 
in the main QEMU CVS.

Some notes about the GUI:

- Avoid using SDL or SDL wrappers: it is simpler to use plain GTK or GDK 
to draw the VGA frame buffer.

- I am not sure that handling multiple VMs running at the same time is 
very useful (some architectural changes are needed in QEMU). But 
switching easily between VM configurations seems interesting.

- The VM description management must be integrated in the QEMU core. I 
plan to work on it soon (Renzo Davoli sent patch I need to study).

- The VM console should be available in a separate TAB for the hackers !

- Of course there should be commands to eject/insert medias, to change 
the hard disk images and to update the VM configuration (ideally a 
simple dialog for dummies and a more technical one to change IRQs, IO 
ports, number of interfaces).

Fabrice.

Jean-Michel POURE wrote:
> Le lundi 5 Avril 2004 11:30, Rudi Lippert a écrit :
> 
>>another question: are there sources available for the linux frontend? many
>>people on this list will also test the frontend, which would certainly
>>speed up its development.
>>€0.06
> 
> 
> Dear Rudi,
> 
> I contacted Alex on Morphix mailing list about this issue. My post is:
> http://www.morphix.org/modules/newbb/viewtopic.php?topic_id=1239&forum=3&jump=1
> 
> Cheers,
> Jean-Michel
> 
> 
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://mail.nongnu.org/mailman/listinfo/qemu-devel
> 

  reply	other threads:[~2004-04-05 19:39 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-05  8:47 [Qemu-devel] Qemu workstation Jean-Michel POURE
2004-04-05  9:10 ` John R. Hogerhuis
2004-04-05  9:30   ` Rudi Lippert
2004-04-05  9:55     ` Jean-Michel POURE
2004-04-05 19:31       ` Fabrice Bellard [this message]
2004-04-05 21:49         ` Jamie Burns
2004-04-06 12:17           ` Richard Zidlicky
2004-04-06 13:28             ` Brad Campbell
2004-04-06 20:23               ` Filip Navara
2004-04-07  4:34                 ` Brad Campbell
2004-04-07  7:59                   ` Filip Navara
2004-04-07  8:24                     ` Brad Campbell
2004-04-07  8:47                       ` Grzegorz Kulewski
2004-04-07 17:50                         ` Richard Zidlicky
2004-04-07  9:40                       ` Filip Navara
2004-04-06 14:00             ` Jamie Burns
2004-04-06 19:00           ` Fabrice Bellard
2004-04-05  9:38   ` Jean-Michel POURE
2004-04-05 10:23     ` John R. Hogerhuis
  -- strict thread matches above, loose matches on Subject: below --
2004-04-05 15:19 Mike Nordell
2004-04-05 20:40 ` Filip Navara
2004-04-05 21:05   ` John R. Hogerhuis
2004-04-05 21:15     ` Filip Navara

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=4071B41F.3040201@bellard.org \
    --to=fabrice@bellard.org \
    --cc=Rudi@LYRIKpage.de \
    --cc=jm@poure.com \
    --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).