9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Jack Johnson" <knapjack@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Colors and other fun
Date: Wed, 27 Jun 2007 14:49:17 -0700	[thread overview]
Message-ID: <6e35c0620706271449g674e22a6l308f111e21710dfd@mail.gmail.com> (raw)
In-Reply-To: <8ccc8ba40706271251s7a4f85fewf245d550a873faf9@mail.gmail.com>

On 6/27/07, Francisco J Ballesteros <nemo@lsub.org> wrote:
> The 90% times I use overlapping windows is just to switch between some windows
> that I want to have most of screen space (while used).
>
> Despite being a mosaic (instead of windows), I still would like to
> pick one window, zoom it  so that it gets more screen space, and
> then zoom out to get the screen as it was.

I'm a Mac user, and my regular machine is a 12" iBook.  Everyone asks
how I survive with such a small screen, and my answer is Expose.

My real desk is messy.  My windowspace is messy.  But, with my
windowspace I have a hot corner: the upper right activates Expose
across all applications.  I throw the cursor up to the corner, pick my
nearly full-screen window by it's content from among the choices, and
keep going.  One mouse move and one click.

I used to think virtual Post-It notes were idiotic.  Now I love them.
I have a dozen on my virtual desk, never lose any, can instantly see
all of them simultaneously and just as instantly obscure them all when
my locus of attention changes.

Though options like the Windows taskbar or the rio menu exist, picking
a window from its visual cues seems to be faster than making the
(quick) context switch from working to reading the window titles to
working again.    Even with terminal windows the context of it's last
state gives me instant clues as to its content, where the name of the
window provides little.

I also find that, like the tiled window scenario, I rarely resize my
windows anymore.  Expose made the iffy idea of overlapping windows
much more efficient.

All still relatively 2D.  There's a lot left to explore before we
start adding dimensions for the gloss.  I still believe a tiled
workspace is superior, but who says we can't naturalize or optimize
the use of that space?  The acme-inspired larswm has a feature where
you can swap windows in the tiled space, so you can have a relatively
large workpane and swap in your current window/task without hiding
your current task.  Without better cues (and here, I suppose animation
would work, but who wants the overhead) the result is functional but a
little jarring.  Also, there are times when the other columns don't
help you with the task at hand, and it would be nice to have them
easily adapt to your current needs.

Francisco's workflow of wanting or needing to maximize the use of the
available pixels for the task at hand is a common one, and somewhere
out there is likely a great solution for incorporating that workflow
style in a tiled environment (namely acme).  In the past, both with
Oberon and with acme I found myself vertically expanding workspaces in
a larger left-hand pane and keeping the right-hand column for
text/tools/scratchpads/commands, but depending on the stacking of the
left-hand workspaces changing context between tasks could be
cumbersome.

Acme-addicts, what's your workflow like?  How many of you are on
pixel-challenged monitors?

-Jack


  reply	other threads:[~2007-06-27 21:49 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-27  9:37 pavlovetsky
2007-06-27 10:08 ` Lucio De Re
2007-06-27 15:07   ` Rob Pike
2007-06-27 18:26     ` Bakul Shah
2007-06-27 18:35       ` Kris Maglione
2007-06-27 19:09         ` Bakul Shah
2007-06-27 19:24           ` David Leimbach
2007-06-27 19:39             ` Gabriel Diaz
2007-06-27 20:35               ` Bakul Shah
2007-06-27 21:20                 ` Jack Johnson
2007-06-29  2:16                   ` Bakul Shah
2007-06-27 19:51             ` Francisco J Ballesteros
2007-06-27 21:49               ` Jack Johnson [this message]
2007-07-02  8:55           ` Douglas A. Gwyn
2007-06-28  4:42     ` Anant Narayanan
2007-06-28  4:50       ` andrey mirtchovski
2007-06-28 17:30     ` Dave Eckhardt
2007-06-27 15:59 ` andrey mirtchovski
2007-06-27 16:23   ` Lorenzo Fernando Bivens de la Fuente
2007-06-27 17:55     ` Steve Simon
2007-06-27 18:03       ` erik quanstrom
2007-06-27 18:22         ` Rob Pike
2007-06-28 15:26         ` Steve Simon
2007-06-27 18:03       ` Kris Maglione
2007-06-27 18:59 Russ Cox
2007-06-27 19:13 ` Tim Wiess
2007-06-27 21:25 ` Charles Forsyth
2007-06-27 15:41   ` john
2007-06-27 21:56     ` erik quanstrom
2007-06-27 16:18       ` john
2007-06-27 22:06       ` Kris Maglione
2007-06-27 21:48 ` Markus Sonderegger

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=6e35c0620706271449g674e22a6l308f111e21710dfd@mail.gmail.com \
    --to=knapjack@gmail.com \
    --cc=9fans@cse.psu.edu \
    /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).