From: Anthony Liguori <anthony@codemonkey.ws>
To: Avi Kivity <avi@redhat.com>
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 08:45:49 -0500 [thread overview]
Message-ID: <4AE5A80D.5040404@codemonkey.ws> (raw)
In-Reply-To: <4AE46EA1.7040505@redhat.com>
Avi Kivity wrote:
> On 10/23/2009 03:59 PM, Anthony Liguori wrote:
>> Your answer may be, this is for a developer and they'll be aware of
>> all the short comings/gotchas but this ends up being a rather
>> user-hostile interface. People are never as aware of short
>> comings/gotchas as we'd like them to be. If there was no other way
>> for a developer to do this, I'd be more inclined to find a way to
>> support this but it's just a matter of writing a script or if you
>> really need a short cut, you can do it with standard gnome short cuts
>> or write a very simple vnc client based on gvncviewer (we're talking
>> a dozen lines of added code) to do this for you.
>>
>
> vncviewer based displays may work now, but they are inefficient and
> will likely fall apart if/when we have 3D support.
If it's chromium based (which I suspect it will be), you could certainly
tunnel it via vnc.
> I'd much rather see a real GUI client, perhaps implemented by
> scripting QObjects or QMP.
I'm with you 100% here. I'd rather see our focus put into a proper gui
based on QMP than to tack on features to SDL.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-10-26 13:46 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 [this message]
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
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=4AE5A80D.5040404@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--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 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.