From: "Jim C. Brown" <jma5@umd.edu>
To: mikeonthecomputer@gmail.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: QEMU 0.7.2
Date: Mon, 12 Sep 2005 23:54:25 -0400 [thread overview]
Message-ID: <20050913035425.GA22080@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <79bf9848050912203756f08d98@mail.gmail.com>
On Mon, Sep 12, 2005 at 08:37:39PM -0700, Mike Swanson wrote:
> I'm just wondering... is it any trouble to draw QEMU using Xlib?
>
No. Somone released a file called nosdl.c which did that, though it was for a really
old version of qemu it may still work. (The way it was written was sort of a
hack, though.)
AFAIK the sole objection to using Xlib is because you can't write a GUI using it
(well technically you could, but clearly using GTK or Qt is better for that
task). Fabrice wants a fully integrated GUI into qemu, so he probably won't accept
Xlib patches.
> I'd prefer that over any conventional toolkit. There are many
> instances where I'm not running any GTK or QT applications on my
> desktop, and I'd appreaciate it if I didn't have load either of them
> only to run QEMU. >_>
> --
> Mike
>
I agree with you there. (In fact, I may take the nosdl.c and write an up2date
version if I can find the time.)
--
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.
next prev parent reply other threads:[~2005-09-13 4:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-04 17:27 [Qemu-devel] QEMU 0.7.2 Fabrice Bellard
2005-09-05 9:58 ` [Qemu-devel] " Christian Walther
2005-09-05 10:48 ` Andreas Mohr
2005-09-05 10:59 ` Christian MICHON
2005-09-08 14:18 ` Jim C. Brown
2005-09-12 22:55 ` Karl Magdsick
2005-09-13 0:33 ` Anthony Liguori
2005-09-13 2:56 ` Jim C. Brown
2005-09-13 3:37 ` Mike Swanson
2005-09-13 3:47 ` Anthony Liguori
2005-09-13 3:54 ` Jim C. Brown [this message]
2005-09-13 3:45 ` Anthony Liguori
2005-09-13 13:07 ` Jim C. Brown
2005-09-13 2:43 ` Jim C. Brown
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=20050913035425.GA22080@jbrown.mylinuxbox.org \
--to=jma5@umd.edu \
--cc=mikeonthecomputer@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.