qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Kevin Wolf <kwolf@redhat.com>,
	Mulyadi Santosa <mulyadi.santosa@gmail.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH] new SDL keyboard shortcuts to start and stop VM
Date: Mon, 26 Oct 2009 18:08:33 +0200	[thread overview]
Message-ID: <4AE5C981.3060307@redhat.com> (raw)
In-Reply-To: <4AE5C513.2030609@codemonkey.ws>

On 10/26/2009 05:49 PM, Anthony Liguori wrote:
>> Many applications minimize to the system tray without needing two 
>> processes.
>
>
> Minimizing or hiding the window are different use cases.  Now, I'm not 
> 100% convinced this use-case is absolutely required but historically, 
> it's always come up in discussions of improving the qemu gui.
>
> Imagine the following:
>
> A user starts a VM at a physical box.  Everythings fine but he wants 
> to return to his workstation so he closes the window.  He goes back to 
> his workstation and connects to a VNC server (on a different X 
> server).  He wants to now bring up the guest's display.

Users don't have boxes.  They have computers.  They don't want to open 
VNC clients and type in meaningless numerical addresses.  They do want 
GUIs which fit with the OSes theme, cut'n'paste, printing, and shared 
storage, all easily configurable.

(and before someone tells me I don't know what users want - users don't 
read qemu-devel, either).

> This cannot be achieved with a gui in the same process as qemu.  Is it 
> necessary to support?  I don't know.

In the priority list this is about 3000 places below having nice buttons 
to eject and insert a CDROM.  A user with a "box" would probably want to 
run the guest on a server (and use vnc, etc.).

> I'd love to just replace the SDL display with GTK + Cairo.  I'm even 
> somewhat inclined to suggest linking to python so that the gui can be 
> written in python...

Best would be to just export a QObject binding to scripting languages, 
which could then be used to implement GUIs outside the qemu source 
base.  The only tricky part is how to deal with the display.  Can we 
expose the display as a special QDict?

-- 
error compiling committee.c: too many arguments to function

  reply	other threads:[~2009-10-26 16:08 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-18 16:24 [Qemu-devel] [PATCH] new SDL keyboard shortcuts to start and stop VM Mulyadi Santosa
2009-10-19 22:20 ` Anthony Liguori
2009-10-20  3:16   ` Mulyadi Santosa
2009-10-20  7:58     ` Gerd Hoffmann
2009-10-20  8:12     ` Daniel P. Berrange
2009-10-20 10:40   ` Kevin Wolf
2009-10-20 16:59     ` Anthony Liguori
2009-10-20 17:08     ` Daniel P. Berrange
2009-10-20 22:14       ` Mulyadi Santosa
2009-10-21  7:27       ` Kevin Wolf
2009-10-21 13:52         ` Glauber Costa
2009-10-21 16:04           ` Mulyadi Santosa
2009-10-21 16:24             ` Glauber Costa
2009-10-21 16:44               ` Mulyadi Santosa
2009-10-21 16:48                 ` Glauber Costa
2009-10-21 18:35                 ` Jamie Lokier
2009-10-22 14:40                   ` Luiz Capitulino
2009-10-22 15:02                     ` Kevin Wolf
2009-10-22 16:32                       ` Luiz Capitulino
2009-10-22 15:40                     ` Anthony Liguori
2009-10-22 16:38                       ` Luiz Capitulino
2009-10-22 18:32                         ` Anthony Liguori
     [not found]                           ` <m33a5bj851.fsf@neno.mitica>
2009-10-23  7:40                             ` [Qemu-devel] " Kevin Wolf
2009-10-23 11:23                               ` Mulyadi Santosa
2009-10-23 11:45                                 ` Kevin Wolf
2009-10-23 13:59                                   ` Anthony Liguori
2009-10-23 14:36                                     ` Kevin Wolf
2009-10-25 15:28                                     ` Avi Kivity
2009-10-25 15:44                                       ` Luiz Capitulino
2009-10-26 13:45                                       ` Anthony Liguori
2009-10-26 14:13                                         ` Avi Kivity
2009-10-26 15:04                                           ` Anthony Liguori
2009-10-26 15:07                                             ` Avi Kivity
2009-10-26 15:49                                               ` Anthony Liguori
2009-10-26 16:08                                                 ` Avi Kivity [this message]
2009-10-26 16:17                                                   ` Anthony Liguori
2009-10-27  9:11                                                   ` Gerd Hoffmann
2009-10-27  9:28                                                     ` Avi Kivity
2009-10-21 16:55           ` [Qemu-devel] " Anthony Liguori
2009-10-21 17:01             ` Mulyadi Santosa
2009-10-21 17:04             ` Glauber Costa
2009-10-21 18:08               ` Anthony Liguori
2009-10-22  7:58                 ` Kevin Wolf
     [not found] <E1N2mhd-0003dq-N6@pih-inmx13.plus.net>
2009-10-28  3:11 ` [Qemu-devel] " Gervase Lam

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=4AE5C981.3060307@redhat.com \
    --to=avi@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=kwolf@redhat.com \
    --cc=mulyadi.santosa@gmail.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).