qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Christian MICHON <christian.michon@gmail.com>
To: Qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Embed QEmu screen on a custom window
Date: Thu, 26 May 2005 15:22:37 +0200	[thread overview]
Message-ID: <46d6db66050526062218c8c5de@mail.gmail.com> (raw)
In-Reply-To: <4295C47B.6070209@gmx.de>

> I think Miguels patch is quite useful. It makes it possible to use
> native Windows controls and Windows API calls to display a nice GUI for
> Qemu, without adding much code to Qemu itself. Actually I've been
> working on something similar for XFree (with XEmbed) to embed Qemu into
> a GUI written with Perl and GTK :) (it partially works already, but
> focusing and mouse grabbing doesn't work quite well yet). Btw. I
> remember at least two people working on this XEmbed thing as well.
> IMHO adding a GUI built with SDL would be much more difficult than using
> native GUI toolkits. And doesn't the Cocoa patch aim at a native MacOsX
> GUI in the end?

All of these are very useful patches indeed. But there's at least 4 gui toolkit
available for SDL, which could ensure:

- a single developpement and a uniform look
- no need for a bigger space on screen (the controls could be like OSD)
- independent of hw/os architecture (the original aim somehow of qemu?)

I agree this is poking inside qemu itself, which can be considered
"a bad thing" (tm). I'm looking at the 4 gui toolkits I mentionned.

- http://www.paragui.org/
- http://guichan.sourceforge.net/
- http://agar.csoft.org/index.html.en
- http://aedgui.sourceforge.net/

Let's open the discussion in a separate thread.

Christian

  reply	other threads:[~2005-05-26 13:29 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-26 11:42 [Qemu-devel] [PATCH] Embed QEmu screen on a custom window Miguel Angel Fraile
2005-05-26 12:10 ` Christian MICHON
2005-05-26 12:43   ` Oliver Gerlich
2005-05-26 13:22     ` Christian MICHON [this message]
2005-05-26 20:03   ` Fabrice Bellard
2005-05-26 20:32     ` gtk [was Re: [Qemu-devel] [PATCH] Embed QEmu screen on a custom window] Jim C. Brown
2005-05-26 21:09       ` Christian MICHON
2005-05-26 22:22         ` Mark Williamson
2005-05-27  6:07       ` Jim C. Brown
2005-05-27 10:59         ` [Qemu-devel] gtk2 driver Sebastien Bechet
2005-05-27 15:28           ` [Qemu-devel] " Jim C. Brown
2005-05-27 18:06             ` Jim C. Brown
2005-05-27 22:29               ` Jim C. Brown
2005-05-26 21:07     ` [Qemu-devel] [PATCH] Embed QEmu screen on a custom window Christian MICHON
2005-05-26 21:55       ` Fabrice Bellard
2005-05-27 14:39       ` Pierre d'Herbemont
2005-05-28 13:17         ` Christian MICHON
2005-05-28 14:10           ` Oliver Gerlich
2005-05-28 15:35             ` Joe Batt
2005-05-26 21:39     ` Jernej Simončič
  -- strict thread matches above, loose matches on Subject: below --
2005-05-26 15:14 Christian Bourque
2005-05-26 19:24 ` Christian MICHON
2005-05-28 12:37 ` Jerome Warnier
2005-05-27 10:50 Miguel Angel Fraile
2005-05-28  7:13 Sylvain Petreolle

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=46d6db66050526062218c8c5de@mail.gmail.com \
    --to=christian.michon@gmail.com \
    --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).