From: Kim Lassila <kim.lassila@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] iOS drawterm
Date: Wed, 25 Mar 2020 13:19:01 +0200 [thread overview]
Message-ID: <A7B5E216-61CA-423C-9B3E-511E90F0B7CC@gmail.com> (raw)
In-Reply-To: <ACE75C03-4481-4930-A2CF-6FBE2FAD28EC@9srv.net>
[-- Attachment #1: Type: text/plain, Size: 985 bytes --]
> On Mar 25, 2020, at 8:19 AM, Anthony Sorace <a@9srv.net> wrote:
>
> With iOS getting first-class mouse pointer support, I’m looking at the iOS drawterm port again. Has anyone touched this since the old GSoC project bit rotted out?
Drawterm is quite slow at reading and writing pixels on the screen. I learned this when I started recording screen in Plan 9 (https://github.com/9d0/screencast <https://github.com/9d0/screencast>).
Instead of porting drawterm to different platforms I would like to see vncs improved to support the latest version of the Remote Framebuffer Protocol (RFC 6143). This would allow a standard VNC client to connect to a Plan 9 terminal, support screen resizing, local mouse cursor, and deliver all key strokes and mouse chords accurately. VNC is optimized to work over a large variety of different networks including high latency links and it will therefore offer a better user experience than drawterm, especially over wireless.
Kim
[-- Attachment #2: Type: text/html, Size: 1602 bytes --]
next prev parent reply other threads:[~2020-03-25 11:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-25 6:19 Anthony Sorace
2020-03-25 11:19 ` Kim Lassila [this message]
2020-03-25 12:41 ` [9fans] " Jeremy O'Brien
2020-03-25 16:32 ` Kim Lassila
2020-03-25 17:40 ` ori
2020-03-25 17:25 ` Anthony Sorace
2020-03-25 17:49 ` Ethan Gardener
2020-03-27 12:25 ` Ole-Hjalmar Kristensen
2020-03-25 17:51 ` Skip Tavakkolian
2020-03-27 5:51 ` Anthony Sorace
2020-03-27 12:21 ` Ethan Gardener
2020-03-31 8:52 ` yy
2020-03-31 10:58 ` Ethan Gardener
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=A7B5E216-61CA-423C-9B3E-511E90F0B7CC@gmail.com \
--to=kim.lassila@gmail.com \
--cc=9fans@9fans.net \
/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).