From: Jason Gress <jasong@ccgr.org>
To: qemu-devel@nongnu.org
Subject: Re: wxWidgets and C: was Re: [Qemu-devel] QEMU GUI
Date: Tue, 11 Jul 2006 07:40:21 -0500 [thread overview]
Message-ID: <200607110740.25142.jasong@ccgr.org> (raw)
In-Reply-To: <44B356D7.9040704@sjsoft.com>
I know this is a lot different than the discussion so far, but has anyone
considered keeping SDL and using an SDL GUI similar to ZSNES? Take a look
(for those not familiar) at http://www.zsnes.com and grab a download. Many
Linux distro package managers have it also. You don't need a SNES ROM to
look at the GUI. It looks like it would be hard to borrow even though it's
GPL (parts are in ASM...) but I thought I'd bounce the idea off of the list.
Jason
On Tuesday 11 July 2006 02:44, David Fraser wrote:
> John R. wrote:
> > 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.
>
> I don't think so. I think the real goal here should be to decide: what
> are the required features for a Qemu GUI that meets a broad range of
> needs, and what would be the fastest and most maintainable way to code
> them? Surely the integration with the Qemu backend would still be
> decoupled enough that you could compile Qemu without the GUI using only
> C if you wanted to?
>
> David
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
next prev parent reply other threads:[~2006-07-11 12:40 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.
2006-07-10 0:10 ` Jim C. Brown
2006-07-11 7:44 ` David Fraser
2006-07-11 12:40 ` Jason Gress [this message]
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=200607110740.25142.jasong@ccgr.org \
--to=jasong@ccgr.org \
--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).