Re: wxWidgets and C: was Re: [Qemu-devel] QEMU GUI
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
Re: wxWidgets and C: was Re: [Qemu-devel] QEMU GUI
Jason Gress wrote: 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? I did not check the source code, but it looks just like any other self-made bitmap-based SDL menu I have seen. It is like inventing yet another GUI toolkit. I am new around here, so I am a bit confused. What is this GUI all about? Is it about (a) replacing SDL with something else for drawing the contents of the window, or (b) providing GUI for configuring virtual machine options, just like numerous front-ends already do? I assume this is (a), as it is beyond me why would anyone want to do (b), when there already are front-ends for Windows, KDE, GTK+, Java, MacOS, etc. ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: wxWidgets and C: was Re: [Qemu-devel] QEMU GUI
Linas Žvirblis wrote: Jason Gress wrote: 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? I did not check the source code, but it looks just like any other self-made bitmap-based SDL menu I have seen. It is like inventing yet another GUI toolkit. I am new around here, so I am a bit confused. What is this GUI all about? Is it about (a) replacing SDL with something else for drawing the contents of the window, or (b) providing GUI for configuring virtual machine options, just like numerous front-ends already do? I assume this is (a), as it is beyond me why would anyone want to do (b), when there already are front-ends for Windows, KDE, GTK+, Java, MacOS, etc. Personally, I'd be interested to have a GUI for controlling a running Qemu instance: change CD-ROM, add/remove USB devices, save/restore VM snapshots (though this would also require to save/restore disk snapshots), and eg. provide buttons to switch between guest Virtual Terminals. Furthermore, I'd like to get information like guest CPU usage and guest hard disk access; this would probably require that the GUI is integrated into Qemu. Whether actual graphics output is done via SDL or GTK or something else is probably not that important. Configuration could still be done with the current command line flags, but if one of the many config GUIs could be integrated into Qemu, that might be useful as well. Regards, Oliver ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: wxWidgets and C: was Re: [Qemu-devel] QEMU GUI
Oliver Gerlich wrote: Personally, I'd be interested to have a GUI for controlling a running Qemu instance: change CD-ROM, add/remove USB devices, save/restore VM snapshots (though this would also require to save/restore disk snapshots), and eg. provide buttons to switch between guest Virtual Terminals. Already exists at http://qemuctl.sourceforge.net/. I am not sure if it is developed anymore, but I am going to integrate it into my own project, in the nearest future. Furthermore, I'd like to get information like guest CPU usage and guest hard disk access; this would probably require that the GUI is integrated into Qemu. Not if this data is available via monitor. And I certainly want it to be, as this is one of the coolest features. Configuration could still be done with the current command line flags, but if one of the many config GUIs could be integrated into Qemu, that might be useful as well. None of them (at least the ones I know) are written in C, so integrating them _into_ QEMU is not really possible. And I absolutely fail to see the reason for doing so. If there is a need for an official GUI, choose one, write yet another, but, please, do not enforce things on users. The current situation works quite well for projects like cdrtools so why should it not work for QEMU? ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: wxWidgets and C: was Re: [Qemu-devel] QEMU GUI
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. 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. ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: wxWidgets and C: was Re: [Qemu-devel] QEMU GUI
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
wxWidgets and C: was Re: [Qemu-devel] QEMU GUI
For the record, we can use wxWidgets in qemu even though we can not use C++ in qemu (something that I would be strongly against). http://wxc.sourceforge.net/ Requiring this as a dependency would make it easier to deal with issues such as C++ ABI compatibility by avoiding the direct use of C++. There's a QtC that I considered using for a Qt GUI for qemu. -- 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
Re: wxWidgets and C: was Re: [Qemu-devel] QEMU GUI
Jim C. Brown wrote: For the record, we can use wxWidgets in qemu even though we can not use C++ in qemu (something that I would be strongly against). http://wxc.sourceforge.net/ Requiring this as a dependency would make it easier to deal with issues such as C++ ABI compatibility by avoiding the direct use of C++. There's a QtC that I considered using for a Qt GUI for qemu. How about WX using Python - Is that an option? -joe ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: wxWidgets and C: was Re: [Qemu-devel] QEMU GUI
On Sat, Jul 08, 2006 at 11:02:31AM -0400, Joe Lee wrote: Jim C. Brown wrote: For the record, we can use wxWidgets in qemu even though we can not use C++ in qemu (something that I would be strongly against). http://wxc.sourceforge.net/ Requiring this as a dependency would make it easier to deal with issues such as C++ ABI compatibility by avoiding the direct use of C++. There's a QtC that I considered using for a Qt GUI for qemu. How about WX using Python - Is that an option? -joe Good question. I'm not aware of a way to call Python code from inside of C. I suppose if we could compile it into a shared library of some sort, that would do the trick. (I'm assuming the Python lib would compile into something that was callable externally using the C ABI, not the C++ ABI. If it's the latter then using Python would still be a bad idea.) I'm of the opinion that it would just be easier to use wxc directly instead of trying to use a Python binding in a C project, though. -- 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
Re: wxWidgets and C: was Re: [Qemu-devel] QEMU GUI
On Sat, 8 Jul 2006 11:13:52 -0400 Jim C. Brown [EMAIL PROTECTED] wrote: Good question. I'm not aware of a way to call Python code from inside of C. See http://docs.python.org/ext/ext.html However doing this just means yet another language dependency. -- Kevin F. Quinn signature.asc Description: PGP signature ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: wxWidgets and C: was Re: [Qemu-devel] QEMU GUI
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jim C. Brown schrieb: For the record, we can use wxWidgets in qemu even though we can not use C++ in qemu (something that I would be strongly against). http://wxc.sourceforge.net/ Requiring this as a dependency would make it easier to deal with issues such as C++ ABI compatibility by avoiding the direct use of C++. There's a QtC that I considered using for a Qt GUI for qemu. Is wxC still under active development? The CVS version seems to be quite old, and I also couldn't find any documentation. Generally it might be quite difficult to find a GUI toolkit with C bindings (besides GTK), as most toolkits seem to be targeted at an object-oriented language, and many go into the direction of script languages and rapid application development. 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 add an interface for external GUIs (and run the GUI as an external process, written in Python or Perl or the like). Regards, Oliver -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEsCLoTFOM6DcNJ6cRAp4dAJwPa7JW7JJzBkg3GnsP+XskTVtAPwCgzpr1 W9RuT6XdO66GtD8evBXfDKc= =inA8 -END PGP SIGNATURE- ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
