9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: dexen deVries <dexen.devries@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] interesting(?) widgets idea
Date: Tue, 12 Jul 2011 17:26:28 +0200	[thread overview]
Message-ID: <201107121726.29100.dexen.devries@gmail.com> (raw)
In-Reply-To: <20110712155612.5b174266@lahti.ethans.dre.am>

Ethan got me thinking there :-)

consider a window consisting of text area and some widgets around it.
instead of making the widgets as small as possible, render as margins when not needed.

most, or all, window's widgets would be rendered as solid background color (functionally margins) when user is reading or typing text.
when user wants to activate any widget, actual menus, scrollbars, statusbar etc. would be drawn.

if the user hovers mouse over widget area, it would be understood as intention to activate widgets, triggering their visibility.

some symmetry of the left/right and perhaps top/bottom would be called for.
one downside is that the widgets would literally `flash' in and out of user's vision, possibly irritating or tiring him.


in other words, all the widgets (menus included) of an app turned into margins when mouse's /not/ over those widgets.


-- 
dexen deVries

[[[↓][→]]]

For example, if the first thing in the file is:
   <?kzy irefvba="1.0" rapbqvat="ebg13"?>
an XML parser will recognize that the document is stored in the traditional ROT13 encoding.

(( Joe English, http://www.flightlab.com/~joe/sgml/faq-not.txt ))



  reply	other threads:[~2011-07-12 15:26 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 [this message]
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
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=201107121726.29100.dexen.devries@gmail.com \
    --to=dexen.devries@gmail.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).