From: "Jim C. Brown" <jma5@umd.edu>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] quick gtk2.c update
Date: Wed, 22 Jun 2005 08:31:34 -0400 [thread overview]
Message-ID: <20050622123134.GA25705@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <001401c576e1$0ef280a0$334d21d1@organiza3bfb0e>
On Tue, Jun 21, 2005 at 11:14:50PM -0500, jeebs@yango.us wrote:
> > They should only get this library if they don't already have a copy
> > installed.
>
> Which will be practically every qemu user.
>
[ Technically not true. Most qemu users are Linux users, and most Linux users
have GTK. :) Sorry, I couldn't resist. ]
All your other arguments about GTK basicly break down to this. If only qemu
wants GTK, then your arguments make sense. However, if there are a lot of users
which use other GTK applications besides qemu, then your arguments do not apply.
A standard Joe Schmoe Windows user probably would not know what GTK is or ever
even hear the name mentioned. That user would have little if any FOSS software
and may not even be aware about FOSS in general. I won't argue about using
xchat, gaim, evolution, etc for this user. The person probably bought
all the applications that this person would ever use. This person is also
unlikely to need to run multiple OSes at once, and even if this person did,
the product used would probably be VMware or Virtual PC or some other commercial
product. Certainly not qemu, which AFAIK lacks corporate backing or commercial
support (unlike Linux which has dozens of companies funding development and
offering support). I am not saying that this can't change. I'm also not arguing
against trying to change this. I'm just saying that GTK vs no-GTK doesn't make
a difference here for qemu.
A Windows user who does use qemu will probably be very familar with OSS software.
That user may scoff at high priced programs and get software that is just as good
for free. That user may run Evolution instead of Outlook, gaim instead of AIM
Messenger, etc. That user will probably have GTK installed.
I realise that these two examples represent extremes of a continum, and that more
users better fit the first example. However, GTK is more well known than qemu
is, and one of GTK 2's goals is to be portable and easy to use on Windows.
> By bundling the libraries with qemu, and keeping them in the qemu directory,
> you can guarantee that the user has versions that work right and are
> compatible with qemu. No -mms-whatever struct issue or anything else.
>
No, that will always be an issue. But my latest patch fixed it, so qemu windows
users at least shouldn't see it anymore.
> > There is no GUI yet. I could easily make a crappy one in, say, 20 minutes.
> > It'd work fine, but it may not be a lot of fun to use. For that matter, it
> > may not be that useful.
>
> Well, maybe not 'gui', but something that tells the user they are indeed
> running the GTK version and not the SDL version.
>
You're right, thats probably a good idea. On linux, you get some GTK warnings
in the console - so its pretty clear if you are using GTK or not. That's my
excuse. ;D How would you like me to fix this? Alter the title of the window
so it says "Qemu GTK" ? Show that GTK is on in the monitor interface, maybe
an "info gtk" that returns if gtk is on or not and what version is being used?
--
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.
next prev parent reply other threads:[~2005-06-22 12:41 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-19 19:09 [Qemu-devel] quick gtk2.c update Jim C. Brown
2005-06-19 22:25 ` Sebastien Bechet
2005-06-20 0:01 ` Jim C. Brown
2005-06-19 22:57 ` jeebs
2005-06-19 23:53 ` Jim C. Brown
[not found] ` <002c01c57535$60064fb0$334d21d1@organiza3bfb0e>
2005-06-20 1:59 ` Jim C. Brown
2005-06-21 2:27 ` jeebs
2005-06-21 2:39 ` Jim C. Brown
2005-06-21 2:58 ` jeebs
2005-06-21 4:28 ` Jim C. Brown
2005-06-21 10:45 ` Jernej Simončič
2005-06-21 16:27 ` jeebs
2005-06-21 17:20 ` Jernej Simončič
2005-06-21 19:40 ` jeebs
2005-06-21 20:22 ` Jernej Simončič
2005-06-21 21:19 ` jeebs
2005-06-21 22:24 ` Jim C. Brown
2005-06-21 22:45 ` jeebs
2005-06-21 23:58 ` Jim C. Brown
2005-06-22 4:14 ` jeebs
2005-06-22 5:15 ` Damien Mascord
2005-06-22 9:31 ` Jernej Simončič
2005-06-22 12:31 ` Jim C. Brown [this message]
2005-06-22 9:16 ` Jernej Simončič
2005-06-22 13:17 ` Jim C. Brown
2005-06-22 18:36 ` Jim C. Brown
2005-06-22 18:53 ` Jim C. Brown
2005-06-22 20:59 ` Jim C. Brown
2005-06-23 2:26 ` jeebs
2005-06-24 0:32 ` Jim C. Brown
2005-06-26 16:13 ` Jim C. Brown
2005-06-27 17:11 ` jeebs
2005-06-27 18:15 ` Jim C. Brown
2005-06-22 13:22 ` Jim C. Brown
2005-06-22 3:53 ` Herbert Poetzl
2005-06-22 12:41 ` Jim C. Brown
2005-06-21 21:52 ` Jim C. Brown
2005-06-21 19:45 ` Jim C. Brown
2005-06-21 20:32 ` [Qemu-devel] Build environment image Tim Walker
2005-06-24 17:19 ` Tim Walker
2005-06-24 17:48 ` John R. Hogerhuis
2005-06-24 18:24 ` Christian MICHON
2005-06-24 18:41 ` John R. Hogerhuis
2005-06-24 18:41 ` Christian MICHON
2005-06-24 19:09 ` jeebs
2005-06-24 19:13 ` jeebs
2005-06-24 20:25 ` John R. Hogerhuis
2005-06-24 20:52 ` jeebs
2005-06-28 18:39 ` Jim C. Brown
2005-06-24 21:30 ` Tim Walker
2005-06-24 21:55 ` John R. Hogerhuis
2005-06-24 22:46 ` [Qemu-devel] " Ronald
2005-06-24 18:07 ` [Qemu-devel] " Christian MICHON
2005-06-21 10:42 ` [Qemu-devel] quick gtk2.c update Jernej Simončič
2005-06-21 12:36 ` Jim C. Brown
2005-06-21 16:30 ` jeebs
2005-06-21 17:25 ` Jernej Simončič
2005-06-21 10:39 ` Jernej Simončič
2005-06-21 10:32 ` Jernej Simončič
-- strict thread matches above, loose matches on Subject: below --
2005-06-27 21:19 Christian Bourque
2005-06-27 21:37 ` Brad Campbell
2005-06-28 1:04 ` Jim C. Brown
[not found] ` <a6ee49d305062720121d6fcc4e@mail.gmail.com>
[not found] ` <a6ee49d30506272028f772930@mail.gmail.com>
[not found] ` <20050628033526.GA23166@jbrown.mylinuxbox.org>
[not found] ` <a6ee49d3050628075662b7ec4c@mail.gmail.com>
2005-06-28 18:46 ` 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=20050622123134.GA25705@jbrown.mylinuxbox.org \
--to=jma5@umd.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).