From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FzjLy-0004dg-Pz for qemu-devel@nongnu.org; Sun, 09 Jul 2006 20:10:22 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FzjLx-0004Zs-1Q for qemu-devel@nongnu.org; Sun, 09 Jul 2006 20:10:22 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FzjLw-0004ZP-L5 for qemu-devel@nongnu.org; Sun, 09 Jul 2006 20:10:20 -0400 Received: from [128.8.10.163] (helo=po1.wam.umd.edu) by monty-python.gnu.org with esmtp (Exim 4.52) id 1FzjMu-0006dU-RH for qemu-devel@nongnu.org; Sun, 09 Jul 2006 20:11:20 -0400 Received: from jbrown.mylinuxbox.org (jma-box.student.umd.edu [129.2.250.193]) by po1.wam.umd.edu (8.12.11.20060308/8.12.11) with ESMTP id k6A0ABGi010347 for ; Sun, 9 Jul 2006 20:10:15 -0400 (EDT) Date: Sun, 9 Jul 2006 20:10:09 -0400 From: "Jim C. Brown" Subject: Re: wxWidgets and C: was Re: [Qemu-devel] QEMU GUI Message-ID: <20060710001009.GA4091@jbrown.mylinuxbox.org> References: <44AC2667.8030008@gentoo.org> <20060708.003444.-399284312.imp@bsdimp.com> <20060708143413.GA20596@jbrown.mylinuxbox.org> <44B022EC.9060305@gmx.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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 Sun, Jul 09, 2006 at 05:03:12PM -0700, John R. wrote: > On 7/8/06, Oliver Gerlich wrote: > > >Is wxC still under active development? The CVS version seems to be quite > >old, and I also couldn't find any documentation. > > > > Well it wouldn't be the first unmaintained batch of code added to > QEMU... Slirp is the example that comes to mind. In fact I think the > QEMU developers are the de facto maintainers of the Slirp codebase. > I believe that it is still being used in other language bindings such as Eiffel, Haskell, or Ocaml. > >So I think we should either just use GTK, or make Qemu ready for > >integration of C++ GUI code (and use one of the common GUI toolkits), or > > It seems pretty clear that C++ is a non-starter. > > >add an interface for external GUIs (and run the GUI as an external > >process, written in Python or Perl or the like). > > > > This is already possible via command line options and accessing the > monitor via perl expect or python expect. Of course an API would be > easier to use and less likely to break. I'd certainly prefer an > out-of-process GUI to admitting C++. > I agree with you here. > I'm not sure what the issue is with just using GTK. That's what the > nonpareil HP calculator emulator uses for the same reason: Eric > dislikes C++. > Mainly that GTK works only on X and Windows, and that it lacks native Windows widgets. > -- John. > > > _______________________________________________ > 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.