From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FrFv6-0004kv-3O for qemu-devel@nongnu.org; Fri, 16 Jun 2006 11:07:36 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FrFv4-0004kE-Ed for qemu-devel@nongnu.org; Fri, 16 Jun 2006 11:07:35 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FrFv4-0004k9-Af for qemu-devel@nongnu.org; Fri, 16 Jun 2006 11:07:34 -0400 Received: from [64.233.162.201] (helo=nz-out-0102.google.com) by monty-python.gnu.org with esmtp (Exim 4.52) id 1FrG4i-0001MA-9U for qemu-devel@nongnu.org; Fri, 16 Jun 2006 11:17:32 -0400 Received: by nz-out-0102.google.com with SMTP id z3so466102nzf for ; Fri, 16 Jun 2006 08:07:33 -0700 (PDT) Message-ID: <46d6db660606160807j46328efcj317a0eff3a76dfb5@mail.gmail.com> Date: Fri, 16 Jun 2006 17:07:32 +0200 From: "Christian MICHON" Subject: Re: [Qemu-devel] VMware Player In-Reply-To: <20060616170215.56be4715@c1358217.kevquinn.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <1150406229.3016.10.camel@mjolnir> <20060616092146.5c9e8ced@c1358217.kevquinn.com> <20060616124524.GA27422@miranda.arrow> <20060616170215.56be4715@c1358217.kevquinn.com> 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 you're putting c++ inside the qemu source tree when it is not needed (yet). if SDL is common to most guest screens: I agree with you that the gui/toolkit should overlay the SDL. Yet Fabrice mentionned months ago this was not his intention, so we should respect it and (hopefully) close this long thread. On 6/16/06, Kevin F. Quinn wrote: > On Fri, 16 Jun 2006 13:45:24 +0100 > Stuart Brady wrote: > > > On Fri, Jun 16, 2006 at 09:21:46AM +0200, Kevin F. Quinn wrote: > > > > > WxWidgets (www.wxwidgets.org) provides a nice way out of this - > > > provides a uniform API for the application developer, and local > > > look-and-feel for each platform. WxWidgets can sit on gtk, motif, > > > x11, win32, mac, cocoa (doesn't appear to be a qt backend yet, but > > > no reason there couldn't be). > > > > Yes, there should be abstraction between the UI and the VM, but I > > think that the approach taken by xine, gstreamer, cdrecord, > > cdparanoia, etc. is much cleaner. You could still write a frontend > > with WxWidgets... > > > > I think it would be best if QEMU didn't depend on any particular > > toolkit, and that includes WxWidgets. > > I was suggesting WxWidgets as a way to avoid writing separate gui > frontends for each platform (that's what WxWidgets is for). I wasn't > suggesting WxWidgets be embedded into Qemu (or the other way around for > that matter). If you want a pretty controller app and you want to > avoid cross-platform issues WxWidgets does a lot of the work for you > (much more than just gtk for example). In particular I was responding > to the statement > > > Face it, putting a GUI on something like QEMU is going to require at > > least a one per desktop/platform effort. > > I don't see any reason to hack up qemu just to put a pretty face on > it. VNC support already provides an easy way to place the guest screen > wherever you want if you don't like the SDL window (although I think > SDL remains the best choice for the guest screen). > http://code.technoplaza.net/wx-sdl/ talks about combining WxWidgets and > SDL, although I don't know if that's useful. > > -- > Kevin F. Quinn > > > _______________________________________________ > Qemu-devel mailing list > Qemu-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/qemu-devel > -- Christian