From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by ewsd; Wed Nov 25 07:35:15 -0500 2020 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 4DD115C0185; Wed, 25 Nov 2020 07:35:13 -0500 (EST) Received: from imap35 ([10.202.2.85]) by compute4.internal (MEProxy); Wed, 25 Nov 2020 07:35:13 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.fm; h= mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type; s=fm1; bh=/0sfP1Sit6dqnwOM0zJvyi2TmGJsi2n e9GLI/m04kD0=; b=q/01xi1MAxHjsPQUcy04REcgc0qHN02mbosE+D4Ho100EGA K/ZBbIIQ6B26lOeiyFkRkQYtR4Ci2ujDhfU6+/khCCF4a+Jr0wsDvUtfHSJkRdl8 Yaav8O3AANsOPNrpVxAbZPlsdeyskSG5YV/Cco99yqBp4q+i3PupDa625llrwaQl zvwrgH5BbhMeabznU/KYZn/4Up8TwyYZvVuK5JVIQ7nNL19KZ840qFqpMqA/cYll MRknh6DXC/FrbPU0Mx2qRBgkOb/HTqDZY1Su7m/enkzLSDNlyWqpVHZXN9qlMWU1 B1B8Xq2tcRDLB01R1yRLVOlNaxMUzLHkc+pM6pQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=/0sfP1 Sit6dqnwOM0zJvyi2TmGJsi2ne9GLI/m04kD0=; b=BXRx4mcSmbSyf08k3W0RmZ ak9gho2DPAMMGjunO6yloPKahYICfNzSX1LErrYYuCi7N7AKV/GWFKE6wHv62MGQ RtPyNRLWPMeZUeDpnaHZ09y85YwYzL1mCI9g1zDk5Xt2Dv9t+CpWYxpAeBCMPTA2 bBbcwdcQmQBmAhUrzi0dTLbVinEKBFmM/r9mB2bvPzhnGXIweNsxYNKqs6hTB5rO wEZ4w78aqUeaeRT2bSwMsEwU7jvnQ2iqe7G6veGi253Rp8pnoARfhc/Xt9MIhaud UD2iqpK+Uek/bWA9/uG+WKY3HGsG6lW9wfHNi++mjbyoK4qcCYpKJNrtvJUcwSiQ == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrudehtddggedvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtsehttd ertderredtnecuhfhrohhmpedfgfhthhgrnhcuifgrrhguvghnvghrfdcuoegvvghkvggv heejsehfrghsthhmrghilhdrfhhmqeenucggtffrrghtthgvrhhnpeffvddtheegkeeffe fgueefjedutedvgffgffekgfejhfetkeegveejvdefueeuieenucevlhhushhtvghrufhi iigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegvvghkvggvheejsehfrghsthhmrg hilhdrfhhm X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id D75DE14C0180; Wed, 25 Nov 2020 07:35:10 -0500 (EST) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.3.0-622-g4a97c0b-fm-20201115.001-g4a97c0b3 Mime-Version: 1.0 Message-Id: <99094179-80c9-40b1-8187-6c95fc2fcb4d@www.fastmail.com> In-Reply-To: References: <288D9AF57CE80B394F1E5B40EA69B2D4@eigenstate.org> Date: Wed, 25 Nov 2020 12:34:51 +0000 From: "Ethan Gardener" To: 9front@9front.org, ori Subject: Re: [9front] rio: resize flash patch Content-Type: text/plain List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: mobile information metadata session module 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.