9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Jack Norton <jack@0x6a.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] interesting(?) widgets idea
Date: Wed, 13 Jul 2011 08:43:51 -0500	[thread overview]
Message-ID: <4E1DA117.2030307@0x6a.com> (raw)
In-Reply-To: <201107121726.29100.dexen.devries@gmail.com>

dexen deVries wrote:

> if the user hovers mouse over widget area, it would be understood as intention to activate widgets, triggering their visibility.
>
>...
> in other words, all the widgets (menus included) of an app turned into margins when mouse's /not/ over those widgets.
>
>

eeek!
Am I the only one who doesn't like this idea?  I cannot stand programs
that change their visual representation based upon where the mouse is,
or what the keyboard meta keys are up to, etc...
Microsoft Office comes to mind (and then the hover-only menus fade in
and out like it's 1999).  Stupid goddamn flash/js menus on websites that
expand when you hover over them.... then break when you move the mouse
to the menu item you'd like (rinse and repeat...).
I like acme because it doesn't change its appearance no matter where I
put my mouse, nor does it have menus that appear only when I bark at it.
  The rio menus are unfortunate, but in that context it is the best it
could be I think.  I do admit though, as was mentioned earlier, rio's
'memory' of what I last selected in its menus as the next default is
very unfortunate.  I've gotten used to that though.

The worst... and I mean worst case of hover-only features is the stupid
system tray clock in windows xp.  I never now when it will be gracious
enough to give me that little pop-up that tells me the full date/time.
Or in second place, that little pop-up in windows explorer that gives me
a (bad) summary of folder contents/size.  It's a crap shoot.  Hover-only
stuff is a disease.

-Jack



  parent reply	other threads:[~2011-07-13 13:43 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-11 14:56 Peter A. Cejchan
2011-07-11 15:14 ` simon softnet
2011-07-11 15:25   ` Peter A. Cejchan
2011-07-11 15:21 ` hiro
2011-07-11 15:23   ` hiro
2011-07-11 15:35   ` Peter A. Cejchan
2011-07-11 15:43     ` dexen deVries
2011-07-11 16:12       ` Peter A. Cejchan
2011-07-11 16:56         ` Jacob Todd
2011-07-11 17:21           ` Peter A. Cejchan
2011-07-11 17:25             ` ron minnich
2011-07-11 17:28             ` dexen deVries
2011-07-12  6:15               ` Peter A. Cejchan
2011-07-11 17:28             ` Lyndon Nerenberg
2011-07-11 17:28             ` andrey mirtchovski
2011-07-12  8:23 ` Sergey Kish
2011-07-12  9:18   ` Peter A. Cejchan
2011-07-12 12:18 ` Ethan Grammatikidis
2011-07-12 12:36   ` dexen deVries
2011-07-12 13:00     ` yy
2011-07-12 13:21       ` Jack Norton
2011-07-12 13:40     ` Ethan Grammatikidis
2011-07-12 14:31       ` dexen deVries
2011-07-12 14:56         ` Ethan Grammatikidis
2011-07-12 15:26           ` dexen deVries
2011-07-13  6:02             ` Peter A. Cejchan
2011-07-13  6:12               ` Bruce Ellis
2011-07-14 17:12               ` Yaroslav
2011-07-14 17:22                 ` dexen deVries
2011-07-13 13:43             ` Jack Norton [this message]
2011-07-13 14:16               ` Wes Kussmaul
2011-07-13 14:45                 ` Anthony Sorace
2011-07-15 20:41                   ` Ethan Grammatikidis
2011-07-15 20:34               ` Ethan Grammatikidis
2011-07-15 20:59                 ` Wes Kussmaul
2011-07-12 20:52   ` Akshat Kumar
2011-07-13  6:15   ` Peter A. Cejchan
2011-07-13  6:23     ` Bruce Ellis
2011-07-15 20:45     ` Ethan Grammatikidis

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=4E1DA117.2030307@0x6a.com \
    --to=jack@0x6a.com \
    --cc=9fans@9fans.net \
    /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).