From: Anthony Liguori <aliguori@cs.utexas.edu>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [RFC] qemu-gui based on wxWidgets and libvncclient
Date: Sun, 15 Oct 2006 22:56:01 -0500 [thread overview]
Message-ID: <453302D1.3040500@cs.utexas.edu> (raw)
In-Reply-To: <1160670903.5105.3.camel@myubuntu.brain-dump.org>
Marc André Tanner wrote:
> Hi,
>
> During the last few weeks i was playing around with the idea to
> implement a GUI for qemu and so this is what i came up with.
Cool. You should checkout virt-manager. It has much the same mission
as what you describe.
> Since i am still pretty new to C/C++ development (in fact i would call
> this my first real world C++ application) and not familiar with qemu
> internals i decided to implement the GUI independent of qemu itself. So
> from a technically point of view i just call qemu with arguments to
> redirect the monitor to stdio and to export the display to vnc (-monitor
> stdio -vnc display). I then try to capture and embed the vnc display
> within the GUI that's where libvncclient[1] comes in.
I have no experience with libvncclient. I think the general idea of
using VNC to create an external QEMU GUI is a good one. Previously, I
had posted some patches for a shmem GUI that used a custom control
channel. After hacking on that for a little bit based on some feedback,
I've come full circle and am now under the view that extending VNC is a
better long term approach.
So, I've reserved some pseudo-encodings and a client message type and am
now working on some VNC extensions to enable better QEMU integration.
My current client code is available at:
http://hg.codemonkey.ws/vnc-gui/
The VNC extensions are still a work in progress but documentation is here:
http://tocm.wikidot.com/vncextensions
Regards,
Anthony Liguori
> It's this last step which doesn't yet work as expected. It is extremely
> slow and/or crashes after some time. But since i am not that experienced
> in both multi threaded gui and wxWidgets programming i am stuck.
>
> So i hope someone from the list can help me here, the two most important
> files for this issue are vncpanel.cpp and vncdisplaythread.cpp.
>
> My current development snapshot can be found at
> http://www.brain-dump.org/projects/qemu-gui/doku.php/download
> but don't expect it to actually work it's still buggy and in pre alpha
> state.
>
> Any comments, ideas, patches and so on are highly appreciated.
>
> At this point i would like to thank Johannes Schindelin for his help
> with the integration of libvncclient.
>
> Thanks,
>
> Marc
>
> [1] http://libvncserver.sourceforge.net/
next prev parent reply other threads:[~2006-10-16 3:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-12 16:35 [Qemu-devel] [RFC] qemu-gui based on wxWidgets and libvncclient Marc André Tanner
2006-10-12 21:25 ` Martin Bochnig
2006-10-16 3:56 ` Anthony Liguori [this message]
2006-10-17 19:32 ` [Qemu-devel] " Fabrice Bellard
2006-10-18 1:29 ` Anthony Liguori
2006-10-18 10:21 ` Johannes Schindelin
2006-10-18 11:17 ` malc
2006-10-18 14:06 ` Anthony Liguori
2006-10-19 8:52 ` Oliver Gerlich
2006-10-19 18:05 ` Fabrice Bellard
2006-10-19 19:01 ` Stefan Weil
2006-10-20 9:00 ` VNC audio extension, was " Johannes Schindelin
2006-10-19 16:08 ` Jorge Luis Zapata Muga
2006-10-17 21:10 ` Marc André Tanner
2006-10-17 21:23 ` Daniel P. Berrange
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=453302D1.3040500@cs.utexas.edu \
--to=aliguori@cs.utexas.edu \
--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).