All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: QEMU 0.7.2
Date: Mon, 12 Sep 2005 22:45:29 -0500	[thread overview]
Message-ID: <43264B59.8090808@us.ibm.com> (raw)
In-Reply-To: <20050913025614.GB21668@jbrown.mylinuxbox.org>

Jim C. Brown wrote:

>On Mon, Sep 12, 2005 at 07:33:26PM -0500, Anthony Liguori wrote:
>  
>
>>What's more, it seems like the easiest way, given the 
>>way QEMU currently works, to have an advanced GUI that can manage 
>>multiple instances of QEMU (using tabs or something like that).
>>
>>    
>>
>
>I'm working on something like that (though I stole the idea from Q, the Mac OS X
>Cocoa GUI for qemu). The way it works, one master qemu process creates the
>actual window (with full GUI and etc), as well as a VM for one guest. In order
>to handle multiple guests, subprocesses are spawned (so one VM per process) but
>they display to the GUI of the master process. (Actually, this is implemented
>using GtkSocket and GtkPlug.) Currently you'll only be able to see one guest
>at a time (though you can switch among them at any time), but I plan on adding
>support for using multiple windows later (all windows would be owned and controlled by
>the same master process).
>  
>
If I understand this correctly, you have multiple processes displaying 
to the same widget?

Seems like it would be a lot easier if each process had it's own 
Socket/Plug pair and then just make use of something like GtkNotebook.

>>There can then be separate GTK/QT guis without QEMU having to support 
>>both widget sets. 
>>    
>>
>
>Or either (except some minimal GDK and the GtkPlug). There are definite
>advantages to going this route.
>  
>
Yeah, I do like this approach quite a bit.  My only concern would be the 
performance of XShmImage vs whatever SDL is using.

Regards,

Anthony Liguori

  parent reply	other threads:[~2005-09-13  4:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-04 17:27 [Qemu-devel] QEMU 0.7.2 Fabrice Bellard
2005-09-05  9:58 ` [Qemu-devel] " Christian Walther
2005-09-05 10:48   ` Andreas Mohr
2005-09-05 10:59   ` Christian MICHON
2005-09-08 14:18   ` Jim C. Brown
2005-09-12 22:55     ` Karl Magdsick
2005-09-13  0:33       ` Anthony Liguori
2005-09-13  2:56         ` Jim C. Brown
2005-09-13  3:37           ` Mike Swanson
2005-09-13  3:47             ` Anthony Liguori
2005-09-13  3:54             ` Jim C. Brown
2005-09-13  3:45           ` Anthony Liguori [this message]
2005-09-13 13:07             ` Jim C. Brown
2005-09-13  2:43       ` Jim C. Brown

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=43264B59.8090808@us.ibm.com \
    --to=aliguori@us.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.