From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Support redirect -curses over a character driver
Date: Thu, 06 Mar 2008 15:19:25 -0600 [thread overview]
Message-ID: <47D05FDD.2000808@codemonkey.ws> (raw)
In-Reply-To: <47CF96BE.2090908@qumranet.com>
Avi Kivity wrote:
> Anthony Liguori wrote:
>>
>> Yes. I was actually thinking of tunneling the curses data but
>> another option would be a more proper character-based encoding. The
>> advantage of that is that you could also send over fonts.
>>
>
> curses is very un-vnc-like, it's a single stream an you need all of it
> to get something meaningful. Much more in the spirit of vnc is to
> encode 'character tiles', and to allow coalesced updates like the
> regular vnc protocol.
Yes, my main interest in curses was to avoid having to deal with
character mapping. I was planning on just using vte terminal to render
the data. Maybe doing a proper encoding is the right thing to do though.
> Ah, CGA as in color graphics adapter. Why not add the encoding to vnc
> and use the regular -vnc option? if both viewer and server support
> the feature, and if the display is in text mode, it would be used
> automatically.
Yes, this is what I want. I still want to be able to connect to it via
telnet though independent of VNC.
Regards,
Anthony Liguori
prev parent reply other threads:[~2008-03-06 21:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-05 2:34 [Qemu-devel] [PATCH] Support redirect -curses over a character driver Anthony Liguori
2008-03-05 11:58 ` Ian Jackson
2008-03-05 14:22 ` Anthony Liguori
2008-03-05 17:33 ` Avi Kivity
2008-03-05 19:05 ` Anthony Liguori
2008-03-05 19:21 ` Avi Kivity
2008-03-05 19:38 ` Anthony Liguori
2008-03-06 7:01 ` Avi Kivity
2008-03-06 21:19 ` Anthony Liguori [this message]
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=47D05FDD.2000808@codemonkey.ws \
--to=anthony@codemonkey.ws \
--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).