From: Anthony Sorace <a@9srv.net>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] iOS drawterm
Date: Thu, 26 Mar 2020 22:51:12 -0700 [thread overview]
Message-ID: <EBA3081A-6BF3-49EE-9B67-010AE784A818@9srv.net> (raw)
In-Reply-To: <CAJSxfmLapUO-D-Rt34LffGsr5nFyZEmFxPMWpxtdKgcGMt2imA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1442 bytes --]
I mean, c’mon, now it practically *needs* drawterm...
https://www.instagram.com/p/B-OctqFhNnB/?igshid=rmqsml1hwqck
> On Mar 25, 2020, at 10:53, Skip Tavakkolian <skip.tavakkolian@gmail.com> wrote:
>
>
>
> rummaging around /mnt/term when using drawterm might be enlightening.
>
>> On Wed, Mar 25, 2020 at 4:20 AM Kim Lassila <kim.lassila@gmail.com> wrote:
>>
>>
>>> 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).
>>
>> 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
>>
>
> 9fans / 9fans / see discussions + participants + delivery options Permalink
[-- Attachment #2: Type: text/html, Size: 2936 bytes --]
next prev parent reply other threads:[~2020-03-27 5:52 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 ` [9fans] " Kim Lassila
2020-03-25 12:41 ` 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 [this message]
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=EBA3081A-6BF3-49EE-9B67-010AE784A818@9srv.net \
--to=a@9srv.net \
--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).