9front - general discussion about 9front
 help / color / mirror / Atom feed
From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] Mouse clipping patch
Date: Wed, 14 Jul 2021 14:17:07 +0200	[thread overview]
Message-ID: <CAFSF3XO=FLyf+=qN=dVH=1q0hjYSVV2_fd63VHLVHKUdmSGnyw@mail.gmail.com> (raw)
In-Reply-To: <CABB-WO8SYYU8CPRB5Cr9py1sKwenNtFEBJ9_Zw+NM7E2swchWQ@mail.gmail.com>

yes i like the idea and all that, but the reality is that rio is
already *not* transparent. and this is the case in multiple ways, both
architectural and in the user interface.

once you allow recursion, the mind has to start counting higher
numbers, which the mind is not good at. recursion is not easy to think
about and thus not transparent.

and more to the point, Window focus, hold mode, DEL key are all
examples for actions that follow as a result of a mouse or keyboard
trigger, yet for the user it's not always clear which (sub?)window it
will affect.

in case of subsubsubrio i'm sure most here already have noticed that
it's very hard to figure out which window will actually be active. to
me what happens most often is that a subrio (so a mostly grey window)
gets activated, whereas i wanted a window inside (a white, from my
point of view a REAL window) to be activated.

sure we have active-window-borders, but they stay in "active" color
even if the parent subrio gets defocused!

clearly the visual cues do not suffice for deeper layering.

On 7/14/21, Stuart Morrow <morrow.stuart@gmail.com> wrote:
> On 14/07/2021, hiro <23hiro@gmail.com> wrote:
>> i still don't see it. either rio consumes the commands or it forwards
>> them. i don't see anything inbetween.
>> where is the complication?
>
> It's not a complication in terms of code, it's that it's an
> untransparent interface.  If we think that window management : the
> windows :: the line discipline : the shell, then keyboard-driven wm is
> like when the line discipline used to interpret # and @.
>
> There's nothing obvious about Unix commands, which one you want for
> what you're trying to do. But knowing the command is *all* the
> difficulty - there's no further difficulty in the "transmit the
> command from the user to the shell" layer, it's just "for each letter
> in the command, type that letter on the keyboard".
>
> The outermost layer needs to be transparent, perhaps so that stuff on
> the other side of it can get more leeway to be confusing.
>

  reply	other threads:[~2021-07-14 22:56 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-12 19:50 José Miguel Sánchez García
2021-07-13  2:36 ` ori
2021-07-13  2:45   ` ori
2021-07-13 14:03     ` Stuart Morrow
2021-08-11  0:56       ` Stuart Morrow
2021-07-13  3:14   ` José Miguel Sánchez García
2021-07-13  8:25     ` hiro
2021-07-13 10:27       ` José Miguel Sánchez García
2021-07-13 14:05         ` Stuart Morrow
     [not found]           ` <CAFSF3XPhDeKiKXdsL0Abnderm45Uc2GCPYsi6ygSaBkf7gDBmA@mail.gmail.com>
2021-07-13 15:09             ` José Miguel Sánchez García
2021-07-13 15:34               ` José Miguel Sánchez García
2021-07-14 12:04                 ` Stuart Morrow
2021-07-15  2:06                   ` Xiao-Yong Jin
2021-07-13 15:11             ` Stuart Morrow
2021-07-13 16:16               ` José Miguel Sánchez García
2021-07-13 16:27                 ` Stuart Morrow
2021-07-13 17:42                   ` José Miguel Sánchez García
2021-07-13 21:20                     ` hiro
2021-07-13 21:57                     ` ori
2021-07-14 11:55                       ` Stuart Morrow
2021-07-13 17:26                 ` Xiao-Yong Jin
2021-07-13 17:45                   ` Stuart Morrow
2021-07-13 18:29                   ` José Miguel Sánchez García
2021-07-13 21:32                     ` hiro
2021-07-13 21:22                   ` Benjamin Purcell
2021-07-13 16:21               ` hiro
2021-07-13 16:29             ` ori
2021-07-14  8:42               ` hiro
2021-07-14 11:52                 ` Stuart Morrow
2021-07-14 12:17                   ` hiro [this message]
2021-07-15  3:13                     ` ori
2021-07-14 12:53                   ` José Miguel Sánchez García
2021-07-15  7:36                     ` hiro
2021-07-14 14:26                 ` ori
2021-07-13 15:27           ` kvik
2021-07-13 16:28             ` ori
2021-07-13 12:00     ` José Miguel Sánchez García
2021-07-13 12:43   ` kvik
2021-07-13 13:36     ` hiro
2021-07-13 13:40       ` hiro
2021-07-14 22:57 ` ori
2021-07-15  7:40   ` hiro

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='CAFSF3XO=FLyf+=qN=dVH=1q0hjYSVV2_fd63VHLVHKUdmSGnyw@mail.gmail.com' \
    --to=23hiro@gmail.com \
    --cc=9front@9front.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).