9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Jeremy Jackins <jeremyjackins@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] rio wishlists
Date: Thu, 23 Jan 2020 16:59:48 -0800	[thread overview]
Message-ID: <CAOr72mh2Eukj-0AZ1bfxtCWVtv12KKbfSXUKRR0ECLrZ740_UA@mail.gmail.com> (raw)
In-Reply-To: <782e4a81-fa3a-426c-967a-64c75be3f161@www.fastmail.com>

> The catch is mostly technical: it requires fast good-enough image scaling, and I think it probably requires it in the kernel.

What about pre-rendering the down-scaled images? For example, whenever
the number of windows (or their sizes) change, rio recalculates the
appropriate miniature image sizes so that all windows can
simultaneously fit on the screen, then pre-renders each of them in a
background thread. Once this is complete there isn't any work to do
except display them when the "exposé" function is called.

On Thu, 23 Jan 2020 at 15:51, Ethan Gardener <eekee57@fastmail.fm> wrote:
>
> On Thu, Jan 23, 2020, at 6:12 PM, Marshall Conover wrote:
> > > Alternative: Implement Exposé for Rio. *flees* :D
> >
> > If this is the feature where you do some mouse gesture/button click
> > and all the windows shrink and appear on the screen at once, so that
> > you can select one, which is then foregrounded, I unironically would
> > support this behaviour. I've come to heavily rely upon it over the
> > last few months at work, and it scratches the same itch as tiling
> > window managers without feeling oppressive.
>
> Yes, that's what I meant. I sometimes find it useful, although it requires I stop and refocus. (I've yet to find the perfect window selection mechanism.)
>
> > If others don't protest
> > too loudly/ want to support the idea, I may consider putting a bounty
> > on it.
>
> The catch is mostly technical: it requires fast good-enough image scaling, and I think it probably requires it in the kernel. Ah... I just had a thought: cropping rather than scaling the windows might be better. Text windows would probably be easier to identify by part of their text. Acme and Sam would be identifiable by their colors and maybe text. Perhaps crop text windows around the text cursor or prompt, and others to the top left? Not sure how well that would work for mothra or page.


  reply	other threads:[~2020-01-24  1:00 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <134490038A9377D966659F986F257F34@ewsd.inri.net>
2020-01-17 14:43 ` [9front] Bounties Ethan Gardener
2020-01-17 16:05   ` kvik
2020-01-17 21:55     ` Silas McCroskey
2020-01-18  0:23       ` rio wishlists Lyndon Nerenberg
2020-01-18  0:40         ` [9front] " Stanley Lieber
     [not found]           ` <CAFSF3XNfdhb+ViOBmVMQ+5+PnSjCeD+9a9p9e4Ug0EX9==aZvw@mail.gmail.com>
2020-01-18  8:19             ` hiro
2020-01-18  9:53               ` Steve Simon
2020-01-18 10:19                 ` hiro
2020-01-21  8:54               ` Ethan Gardener
2020-01-21  8:57         ` Ethan Gardener
2020-01-21  9:49           ` hiro
2020-01-22 16:30             ` Ethan Gardener
2020-01-22 16:47               ` hiro
2020-01-23 15:09                 ` Ethan Gardener
     [not found]                   ` <CAK0pxsHVpyae1+teTSOAFp=nBoq_r7-aKexh_X=hEDe7hUcReA@mail.gmail.com>
     [not found]                     ` <CAK0pxsFDk=C_+37tKzU=U-TMQLTPcW6MOQ1sgKNBrYhWrj4Bwg@mail.gmail.com>
2020-01-23 18:12                       ` Marshall Conover
2020-01-23 21:23                         ` hiro
2020-01-23 22:42                           ` Julius Schmidt
2020-01-24  0:39                             ` Ethan Gardener
2020-01-24  0:44                               ` Ethan Gardener
2020-01-23 23:50                         ` Ethan Gardener
2020-01-24  0:59                           ` Jeremy Jackins [this message]
2020-01-24 10:04                             ` hiro
2020-01-21  8:37     ` [9front] Bounties Ethan Gardener
2020-01-22 17:04     ` Ori Bernstein

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=CAOr72mh2Eukj-0AZ1bfxtCWVtv12KKbfSXUKRR0ECLrZ740_UA@mail.gmail.com \
    --to=jeremyjackins@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).