From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1N2S7k-0001an-EL for qemu-devel@nongnu.org; Mon, 26 Oct 2009 12:08:48 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1N2S7f-0001Xb-99 for qemu-devel@nongnu.org; Mon, 26 Oct 2009 12:08:47 -0400 Received: from [199.232.76.173] (port=43549 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N2S7d-0001XG-Tg for qemu-devel@nongnu.org; Mon, 26 Oct 2009 12:08:42 -0400 Received: from mx1.redhat.com ([209.132.183.28]:58131) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1N2S7d-0002co-Cz for qemu-devel@nongnu.org; Mon, 26 Oct 2009 12:08:41 -0400 Message-ID: <4AE5C981.3060307@redhat.com> Date: Mon, 26 Oct 2009 18:08:33 +0200 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [Qemu-devel] Re: [PATCH] new SDL keyboard shortcuts to start and stop VM References: <5d6222a80910210924j62505b7dtf298754ce65f1c99@mail.gmail.com> <20091021183503.GA27677@shareable.org> <20091022124036.5df991f3@doriath> <4AE07D06.4080205@codemonkey.ws> <20091022143833.51c48260@doriath> <4AE0A535.3000607@codemonkey.ws> <4AE15DFD.6050203@redhat.com> <4AE1974E.5010303@redhat.com> <4AE1B6A6.3060507@codemonkey.ws> <4AE46EA1.7040505@redhat.com> <4AE5A80D.5040404@codemonkey.ws> <4AE5AEA4.6020500@redhat.com> <4AE5BA62.9040007@codemonkey.ws> <4AE5BB32.4080801@redhat.com> <4AE5C513.2030609@codemonkey.ws> In-Reply-To: <4AE5C513.2030609@codemonkey.ws> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Kevin Wolf , Mulyadi Santosa , qemu-devel@nongnu.org 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