qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "John R." <jhoger@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: wxWidgets and C: was Re: [Qemu-devel] QEMU GUI
Date: Sun, 9 Jul 2006 17:03:12 -0700	[thread overview]
Message-ID: <dd8f98f40607091703m537898d0m927c77c5a0904b@mail.gmail.com> (raw)
In-Reply-To: <44B022EC.9060305@gmx.de>

On 7/8/06, Oliver Gerlich <olig9@gmx.de> 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.

> 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'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++.

-- John.

  reply	other threads:[~2006-07-10  0:03 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-21 18:11 [Qemu-devel] QEMU GUI Fabrice Bellard
2006-06-21 19:42 ` Mike Kronenberg
2006-06-22 19:32   ` gbeauchesne
2006-06-22 19:32   ` gbeauchesne
2006-06-28 23:03     ` Joe Lee
2006-06-29 13:19       ` Daniel P. Berrange
2006-06-29 21:05         ` Joe Lee
2006-06-29 21:47           ` Daniel P. Berrange
2006-06-22 15:06 ` Luca Barbato
2006-07-01 22:47   ` Chris Wilson
2006-07-05 20:51     ` Luca Barbato
2006-07-08  2:14       ` Chris Wilson
2006-07-08  2:46         ` Johannes Schindelin
2006-07-08  6:34           ` M. Warner Losh
2006-07-08 14:34             ` wxWidgets and C: was " Jim C. Brown
2006-07-08 15:02               ` Joe Lee
2006-07-08 15:13                 ` Jim C. Brown
2006-07-08 16:34                   ` Kevin F. Quinn
2006-07-08 21:26               ` Oliver Gerlich
2006-07-10  0:03                 ` John R. [this message]
2006-07-10  0:10                   ` Jim C. Brown
2006-07-11  7:44                   ` David Fraser
2006-07-11 12:40                     ` Jason Gress
2006-07-11 13:17                       ` Linas Žvirblis
2006-07-11 14:52                         ` Oliver Gerlich
2006-07-11 15:29                           ` Linas Žvirblis
2006-07-12  8:17         ` Luca Barbato
2006-07-12 13:15           ` [Qemu-devel] Insert module into kernel Tieu Ma Dau
2006-07-12 13:36             ` Paul Brook
2006-07-13  8:11               ` Tieu Ma Dau
2006-06-22 15:18 ` [Qemu-devel] QEMU GUI Christian MICHON
2006-06-30 10:28   ` Dan Sandberg
2006-06-22 21:50 ` Anthony Liguori
2006-06-23  0:18   ` Kevin F. Quinn
2006-06-23  1:53     ` Anthony Liguori
2006-06-23  7:17       ` Kevin F. Quinn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=dd8f98f40607091703m537898d0m927c77c5a0904b@mail.gmail.com \
    --to=jhoger@gmail.com \
    --cc=jhoger@pobox.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).