All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Ongoing changes to the displaying code
Date: Fri, 09 Jan 2009 11:24:42 -0600	[thread overview]
Message-ID: <4967885A.2020908@codemonkey.ws> (raw)
In-Reply-To: <18791.34404.878201.724561@mariner.uk.xensource.com>

Ian Jackson wrote:
> Anthony Liguori writes ("Re: [Qemu-devel] Ongoing changes to the displaying code"):
>   
>> David Turner wrote:
>>     
>>> For my specific needs, VNC and a separate GUI application are totally 
>>> overkill. However, it is true that QEMU itself absolutely doesn't 
>>> require to support any GUI jazz (you should probably let that to 
>>> forks/GUI wrappers instead).
>>>       
> ...
>   
>> What specifically, do you consider to be overkill?  Are you afraid of 
>> the performance overhead of VNC?  Is the lack of VNC clients a problem 
>> (assuming you don't want a gtk dependency)?
>>     
>
> I think it's fair enough for people to prefer SDL to VNC for a number
> of reasons.  But why not just allow them to embed the qemu SDL window
> in their application ?  This is definitely possible in X although I'm
> not sure exactly how to do it with SDL.
>   

If you search the mailing lists, I went down this route before I 
originally wrote the VNC server.  XEmbed has some serious limitations 
surrounding how events are propagated between windows.  I convinced 
myself that you couldn't do what you really wanted to do through this 
mechanism.

Of course, with the right VNC extension to support a shared memory 
transport, I still contend VNC can be just as efficient as SDL.

Regards,

Anthony Liguori

> Ian.
>
>
>   

  reply	other threads:[~2009-01-09 17:24 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-09  1:52 [Qemu-devel] Ongoing changes to the displaying code Daniel Gutson
2009-01-09  2:50 ` Anthony Liguori
2009-01-09  3:04   ` Anthony Liguori
2009-01-09  9:28     ` David Turner
2009-01-09 15:20       ` Anthony Liguori
2009-01-09 16:53         ` David Turner
2009-01-09 17:16         ` Ian Jackson
2009-01-09 17:24           ` Anthony Liguori [this message]
2009-01-09 17:42             ` Riku Voipio
2009-01-09 18:59               ` Anthony Liguori
2009-01-10  0:01                 ` Jamie Lokier
2009-01-10  1:39                   ` Anthony Liguori
2009-01-15  8:53                 ` Mark McLoughlin
2009-01-12 15:25             ` Ian Jackson
2009-01-09 17:26           ` David Turner
2009-01-09 19:02             ` Anthony Liguori
2009-01-12 15:31             ` Ian Jackson
2009-01-11  8:22     ` Avi Kivity
2009-01-12 15:33       ` Ian Jackson
2009-01-12 15:57         ` Avi Kivity
2009-01-09 12:04 ` Stefano Stabellini

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=4967885A.2020908@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --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.