9front - general discussion about 9front
 help / color / mirror / Atom feed
From: "Ethan Gardener" <eekee57@fastmail.fm>
To: 9front@9front.org, ori <ori@eigenstate.org>
Subject: Re: [9front] rio: resize flash patch
Date: Wed, 25 Nov 2020 12:34:51 +0000	[thread overview]
Message-ID: <99094179-80c9-40b1-8187-6c95fc2fcb4d@www.fastmail.com> (raw)
In-Reply-To: <edfb69e5-da89-6b4c-7522-9c08c87b6f9b@gmail.com>

On Wed, Nov 25, 2020, at 12:21 AM, Amavect wrote:
> 
> I have thought about what the Right Thing should be. Neither mouse nor 
> wctl should be related to the act of drawing to the screen. That's 
> /dev/draw's responsibility. But rio's design is to not exactly stand 
> between the program and /dev/draw, so rio can't know anything.

Since Rio is responsible for governing the size and position of the windows implemented by the draw device, I have no problem at all with Rio supplying the redraw messages. Since Rio multiplexes the mouse and implements wctl, I think these seem reasonable channels for the messages.

As for which file the resize and reposition messages should be sent over; wctl or mouse, it currently comes over both of them. I'm happy with that. The wctl data is good for scripts which might want to re-run mc. The data over the mouse channel saves mouse-reading programs from having yet another file open. You may recall each open file requires a process under Plan 9.

General thought: designs which "feel right" can be unecessarily inefficient, complex and/or difficult to use. I liked Plan 9 for its pragmatic approach to problems: it doesn't take "this feels right" seriously; it does what works.


  parent reply	other threads:[~2020-11-25 12:35 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-22  4:36 Amavect
2020-11-22  5:33 ` [9front] " ori
2020-11-22  6:18   ` Amavect
2020-11-22 10:33     ` hiro
2020-11-22 16:57   ` cinap_lenrek
2020-11-22 17:10     ` Amavect
2020-11-24 23:35       ` ori
2020-11-25  0:21         ` Amavect
2020-11-25  9:38           ` hiro
2020-11-25 12:34           ` Ethan Gardener [this message]
     [not found]             ` <379baa18-a67f-de65-98b5-d7e08cbb5101@gmail.com>
     [not found]               ` <19260358-767b-4746-a3ff-4ce456a646c5@www.fastmail.com>
     [not found]                 ` <CAFSF3XN_vLb89F=CCzXLkiQvYFFHYm72aSbc1NRkPBtDqwPzFA@mail.gmail.com>
2020-11-29 20:55                   ` Ethan Gardener
2020-11-29 22:15                     ` cinap_lenrek
2020-11-29 22:55                       ` Stuart Morrow
2020-11-29 23:35                         ` cinap_lenrek
2020-11-30  0:10                           ` Stuart Morrow
2020-11-30  0:13                             ` Stuart Morrow
2020-11-30  0:21                             ` Alex Musolino
2020-11-30  1:48                               ` ori
2020-11-30  2:17                                 ` Stanley Lieber
2020-11-30  9:19                                 ` hiro
2020-11-30 18:26                                 ` Ethan Gardener
2020-11-29 22:26                 ` umbraticus
2020-11-29 22:50                   ` Ethan Gardener
2020-11-22 17:14     ` ori
2020-11-22 20:40   ` hiro
2020-11-22 21:18     ` ori
2020-12-03  2:17     ` magma698hfsp273p9f
2020-11-23 21:16 ` Ethan Gardener
2020-11-23 22:06   ` Amavect
2020-11-23 23:17     ` 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=99094179-80c9-40b1-8187-6c95fc2fcb4d@www.fastmail.com \
    --to=eekee57@fastmail.fm \
    --cc=9front@9front.org \
    --cc=ori@eigenstate.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).