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 <[EMAIL PROTECTED]> 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 _______________________________________________ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel