On Sun, Jul 09, 2006 at 05:03:12PM -0700, 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. >
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. _______________________________________________ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel