From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GZufA-00014G-L2 for qemu-devel@nongnu.org; Tue, 17 Oct 2006 15:31:44 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GZuf9-00012Y-SI for qemu-devel@nongnu.org; Tue, 17 Oct 2006 15:31:44 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GZuf9-00012N-Mb for qemu-devel@nongnu.org; Tue, 17 Oct 2006 15:31:43 -0400 Received: from [199.232.41.67] (helo=mx20.gnu.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1GZuf9-0003mA-Ir for qemu-devel@nongnu.org; Tue, 17 Oct 2006 15:31:43 -0400 Received: from [84.96.92.56] (helo=smTp.neuf.fr) by mx20.gnu.org with esmtp (Exim 4.52) id 1GZuf8-0004Cs-O4 for qemu-devel@nongnu.org; Tue, 17 Oct 2006 15:31:42 -0400 Received: from [84.102.211.62] by sp604003mt.gpm.neuf.ld (Sun Java System Messaging Server 6.2-5.05 (built Feb 16 2006)) with ESMTP id <0J7A00DFEOWMAV40@sp604003mt.gpm.neuf.ld> for qemu-devel@nongnu.org; Tue, 17 Oct 2006 21:31:35 +0200 (CEST) Date: Tue, 17 Oct 2006 21:32:29 +0200 From: Fabrice Bellard Subject: Re: [Qemu-devel] Re: [RFC] qemu-gui based on wxWidgets and libvncclient In-reply-to: <453302D1.3040500@cs.utexas.edu> Message-id: <45352FCD.6060300@bellard.org> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT References: <1160670903.5105.3.camel@myubuntu.brain-dump.org> <453302D1.3040500@cs.utexas.edu> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Anthony Liguori wrote: > I have no experience with libvncclient. I think the general idea of > using VNC to create an external QEMU GUI is a good one. Previously, I > had posted some patches for a shmem GUI that used a custom control > channel. After hacking on that for a little bit based on some feedback, > I've come full circle and am now under the view that extending VNC is a > better long term approach. > > So, I've reserved some pseudo-encodings and a client message type and am > now working on some VNC extensions to enable better QEMU integration. > > My current client code is available at: > > http://hg.codemonkey.ws/vnc-gui/ > > The VNC extensions are still a work in progress but documentation is here: > > http://tocm.wikidot.com/vncextensions I think this is a good idea. First one detail: for Pointertypechange, it would be better to use the value 32768 as 0 instead of 32767 or to use a 16 bit two complement value. Another point is that you should consider adding audio support. I can help you on that (maybe malc would be interested too !). A simple format could be 4 bit ADPCM at fixed frequency. Optionally A more advanced codec such as Vorbis could be used. Regards, Fabrice.