On 10/26/2009 03:45 PM, Anthony Liguori wrote:
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.
But you wouldn't want to. You'd probably get decent throughput at the
expense of greater cpu consumption. Much better to have qemu talk to drm.
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.
Maybe slightly less than 100%. I meant a native GUI in the same process
as qemu, but talking to QObjects through a scripting language.
--
error compiling committee.c: too many arguments to function
