qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Michael L Torrie <torriem@chem.byu.edu>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Qemu frontend proposal
Date: Fri, 23 Apr 2004 09:52:59 -0600	[thread overview]
Message-ID: <1082735579.9583.48.camel@isengard> (raw)
In-Reply-To: <200404230913.54616.jm@poure.com>

On Fri, 2004-04-23 at 01:13, Jean-Michel POURE wrote:
> Dear all,
> 
> Fabrice expressed the need for a Qemu frontend. Before working on anything, I 
> would like to discuss about possible plans and receive some feedback.

As good as wxWidgets and other GUI toolkits are, one size does not fit
all.  If you are trying to reach win32, *nix, and OS X, right now only
QT comes close but there is no free version currently available on win32
(well, there is a GPL port of the X11 version to win32 and it's quite
good, but still under heavy development).  GTK 2 looks good on windows
and unix now, but it's a no show under OS X.  The pros and cons of
wxWindows you have already dealt with.

So, from watching various programs that are trying to implement
universal front-ends for programs, I've found that often the best
solution (especially for programs with simpler UI needs like qemu) is to
have a clean separation between the backend and frontend.

With that in mind, a wxWidgets gui is a great idea, so long as it's easy
and clean for someone (if they desired) to create a new GUI with some
other toolkit and interface cleanly with the qemu backend.  In other
words, if all the backend needs is a SDL window handle and then an API
for communicating with the GUI, that is the best, in my opinion.  The
GUI itself should not be an integral part of the qemu backend. 
Currently there is an API of sorts for use by the front end by way of
standard-in, standard-out.  Plugging into this currently is true to the
unix spirit.

Isn't there a win32 frontend currently, and work in a unix port of it?

Michael

> 
> My proposals are:
> 
> 1) Framework : wxWidgets
> 
> wxWidgets is the new name of the wxWindows framework. The latest release 
> wxWidgets 2.5.1 has good Unicode compliance and offers GTK2 and Windows 
> bindings. The wxMac version is still hardly usable.
> 
> Also, wxWidgets offers a wxPython binding.
> 
> 2) Interface builder : wxGlade
> 
> wxWidgets supports an XML format called XRC, which is called at runtime 
> without the need to hard-code the interface.
> 
> There are several applications for building XRC interface. wxGlade is probably 
> the best and very similar to Glade-2.
> 
> Under Debian, I installed wxPython 2.5.1 from the experimental repository and 
> ran wxGlade from CVS version without real problem.
> 
> 3) Collaboration : group work inside the Qemu project
> 
> I would be in favour of working in team inside the Qemy project. My guess 
> would be to discuss the interface first, commit the XRC to Qemu CVS. Then, we 
> can start coding the underlying logic in C++ or in Python.
> 
> This way, we can share ideas and experience. Any feedback is appreciated. Do 
> not hesitate to answer on the list.
> 
> Cheers,
> Jean-Michel
> 
> 
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://mail.nongnu.org/mailman/listinfo/qemu-devel
-- 
Michael L Torrie <torriem@chem.byu.edu>

  parent reply	other threads:[~2004-04-23 15:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-23  7:13 [Qemu-devel] Qemu frontend proposal Jean-Michel POURE
2004-04-23 15:50 ` Kyle Hayes
2004-04-23 15:52 ` Michael L Torrie [this message]
2004-04-23 17:53 ` Jocelyn Mayer
2004-04-23 22:18 ` Fabrice Bellard
2004-04-24  7:21   ` Jean-Michel POURE
2004-04-24 16:26   ` Michael Torrie
2004-04-25 12:29     ` Fabrice Bellard
2004-04-25 12:32       ` Martin Garton

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=1082735579.9583.48.camel@isengard \
    --to=torriem@chem.byu.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).