From: Daniel Gutson <dgutson@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Ongoing changes to the displaying code
Date: Thu, 08 Jan 2009 17:52:20 -0800 [thread overview]
Message-ID: <4966ADD4.5090102@codesourcery.com> (raw)
Hi,
I'm doing some development related with the displaying bits, and wanted
to give an early notice for syncing purposes (specially in terms of
Stefano's work).
The development I'm doing intends to add a GUI, which the following
abilities:
- show more than one DisplayState in a single VT (I think this was
previously referred as 'DS multiplexing'), capable of being a mix of
graphic/text (see below)
- add a skin to each VT
- provide "buttons" with associated actions (such as keyboard input)
- define all these attributes from an XML file
- in the case of VNC, the ability to show a different VT in each
connection.
In order to achieve those features, I am doing the following changes:
- TextConsole (aka QEMUConsole) is a layer above DisplayState which
uses it for rendering glyphs. The GUI takes care about 'graphics',
whereas TextConsole use it to show the glyphs, get keys, and do text
terminal stuff (such as scrolling). No more GRAPHIC_CONSOLE, just fixed
or non-fixed size text consoles.
- Displaying backends no longer have input logic or grabbing/displaying
pointer/mouse logic. That's been moved to the GUI bits, so the backends'
responsibility is to render pieces of screen. (thus being simplified).
- use of libpng
- use of libxml (soon)
- I also added an 'fb render engine', intended to provide common
functionality to frame buffer devices, such as:
- draw lines handling differences of depths,byte orders,pixel orders,
and color orders between guest and host
- rotation/flipping
- palette handling
What I'm NOT addressing is:
- text consoles rotation
- ability to show the same VT in more than one displaying backend at
the same time (i.e. SDL and VNC).
I'm still working hard to get all the bits together, and should be ready
no later than Feb.
Daniel.
--
Daniel Gutson
"Don't trust a computer you can't throw out a window"
next reply other threads:[~2009-01-09 1:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-09 1:52 Daniel Gutson [this message]
2009-01-09 2:50 ` [Qemu-devel] Ongoing changes to the displaying code Anthony Liguori
2009-01-09 3:04 ` Anthony Liguori
2009-01-09 9:28 ` David Turner
2009-01-09 15:20 ` Anthony Liguori
2009-01-09 16:53 ` David Turner
2009-01-09 17:16 ` Ian Jackson
2009-01-09 17:24 ` Anthony Liguori
2009-01-09 17:42 ` Riku Voipio
2009-01-09 18:59 ` Anthony Liguori
2009-01-10 0:01 ` Jamie Lokier
2009-01-10 1:39 ` Anthony Liguori
2009-01-12 15:25 ` Ian Jackson
2009-01-15 8:53 ` Mark McLoughlin
2009-01-09 17:26 ` David Turner
2009-01-09 19:02 ` Anthony Liguori
2009-01-12 15:31 ` Ian Jackson
2009-01-11 8:22 ` Avi Kivity
2009-01-12 15:33 ` Ian Jackson
2009-01-12 15:57 ` Avi Kivity
2009-01-09 12:04 ` Stefano Stabellini
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=4966ADD4.5090102@codesourcery.com \
--to=dgutson@codesourcery.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).