From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1C2yir-0007DN-PX for qemu-devel@nongnu.org; Thu, 02 Sep 2004 17:02:21 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1C2yiq-0007D3-4w for qemu-devel@nongnu.org; Thu, 02 Sep 2004 17:02:21 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1C2yiq-0007Ct-0M for qemu-devel@nongnu.org; Thu, 02 Sep 2004 17:02:20 -0400 Received: from [38.113.3.61] (helo=smtp-out.hotpop.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1C2ydN-0002qB-6k for qemu-devel@nongnu.org; Thu, 02 Sep 2004 16:56:41 -0400 Received: from phreaker.net (kubrick.hotpop.com [38.113.3.103]) by smtp-out.hotpop.com (Postfix) with SMTP id 07E777C79D0 for ; Thu, 2 Sep 2004 20:56:32 +0000 (UTC) Received: from jbrown.mylinuxbox.org (pcp02982829pcs.midval01.tn.comcast.net [68.85.196.73]) by smtp-1.hotpop.com (Postfix) with ESMTP id 2B3B31A00BD for ; Thu, 2 Sep 2004 20:56:29 +0000 (UTC) Date: Thu, 2 Sep 2004 16:56:33 -0400 From: "Jim C. Brown" Subject: Re: [Qemu-devel] Qemu development schedule? Message-ID: <20040902205633.GB21292@jbrown.mylinuxbox.org> References: <000501c48eda$a026ab40$20649c3f@computername> <200408310107.07350.hetz@witch.dyndns.org> <002101c48ee5$46b2e280$20389c3f@computername> <1093908872.26682.76.camel@aragorn> <1C8FBBB0-FB2F-11D8-8B6F-000A95D874F4@mac.com> <1093973009.29476.16.camel@sherbert> <4134DF1A.4010407@bellard.org> <20040901215857.GA21314@jbrown.mylinuxbox.org> <20040902092645.A15294@bbland> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040902092645.A15294@bbland> 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 On Thu, Sep 02, 2004 at 09:26:45AM +0200, Lionel Ulmer wrote: > On Wed, Sep 01, 2004 at 05:58:58PM -0400, Jim C. Brown wrote: > > I am curious, what is wrong with using Xlib directly? Would you accept an > > Xlib patch if it was simple enough to understand? > > Well, the problem with using Xlib directly instead of via SDL is that you > loose easy portability to the Win32 platform So? Fabrice has said that he'll add support got the Win32 GUI directly if some one sends a patch for it ... surely this makes it hard to port to the Linux platform??? The idea is, use XLib when qemu is compiled under a *nix, use Win32 for Windows, the OSX Gui (Aqua?) for Mac OS X, etc. I don't see what the problem here is. Furthermore, there is a patch for Xlib already. So I ask, why not? >(except if you ask people to > install an X server in Windows :-) ). > Not a bad idea imho, tho not optimal. > Lionel > > -- > Lionel Ulmer - http://www.bbrox.org/ > > > _______________________________________________ > Qemu-devel mailing list > Qemu-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/qemu-devel > -- Infinite complexity begets infinite beauty. Infinite precision begets infinite perfection.