Re: A Proposal For The Addition Of Color-Reactiveness To The GNOME Desktop

[Gary V Vaughan <gvaughan oranda demon co uk>]

[snip]

On 19 May, Bowie Poag shouted:
Bowie> 
Bowie> +--
Bowie> | ----------------------------------------------------
Bowie> | Example Behavior Set #1:
Bowie> |
Bowie> | Key:  A = Aqua    C = Clear   O = Orange  B = Blue
Bowie> |       Y = Yellow  V = Violet  R = Red     G = Green
Bowie> |      
Bowie> |
Bowie> | State               Color Transition Table
Bowie> | ------------------  --------------------------------
Bowie> | Idle                CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC \
Bowie> | Sleeping            BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB  \
Bowie> | Low CPU Usage       VVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV   > Solid Colors.
Bowie> | Moderate CPU Usage  RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR  /
Bowie> | Heavy CPU Usage     OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO /
Bowie> | Severe CPU Usage    YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY
Bowie> | Attention           GGGGGGGGCCCCCCCCGGGGGGGGCCCCCCCC \  See how you can
Bowie> | Error               RRCCRRCCRRCCRRCCRRCCRRCCRRCCRRCC  > set the behavior
Bowie> | Busy                ACCCACCCACCCACCCACCCACCCACCCACCC /  to blink stuff?
Bowie> | ------------------  --------------------------------
Bowie> +-- 
Bowie> 
Bowie>  This is what the behavior set would look like if you wanted to:
Bowie> 
Bowie>  Clear color for Idle
Bowie>  Blue for Sleeping
Bowie>  Violet for Low CPU Usage
Bowie>  Red for Moderate CPU Usage
Bowie>  Orange for Heavy CPU Usage
Bowie>  Yellow for Severe CPU Usage
Bowie>  Slow Blinking Green/Clear for Attention
Bowie>  Fast Blinking Red/Clear for Error
Bowie>  Normal Blinking Aqua/Clear for Busy

On Wed, May 20, 1998 at 09:57:56AM -0400, raster@redhat.com wrote:
raster> kewl. You took the visual into account.. I suggest sound be run in
raster> parallel :) (ie defin a sound to make for a state - of course most
raster> states will have none - but bad error states for example may have a
raster> little "bzzt bzzt".

[snip]

raster> yes it's genuinely useful - but taken to the point of being much too
raster> specific here - he generalization of it leads to the app advertising
raster> its state via lets say properties to someone else who will, if
raster> intrested pcik up these hints and draw something.. these hints on state
raster> shoudl be definied by a standard ie standard states are:
raster> 
raster> 0 Inactive
raster> 1 Calculating
raster> 2 Awaiting Data
raster> 3 Error 1  (2 for blinking)
raster> 4 Error 2  (2 for blinking)
raster> 5 Require user information
raster> 6 Struggling (for cpu , ram or bandiwidth - take your pick)
raster> 7 Reading Files
raster> 8 Overloaded
raster> 9 --- Unused
raster> 10 0% done
raster> 11 10% done
raster> 12 20% done
raster> 13 30% done
raster> etc.

Yeah!  Imagine those netscape downloads as they progress:

    state --	10% done,	20% done ...	 90% done,	100% done
    lamp  -- 	{RRRRC}+, 	{RRRCC}+ ...	{RCCCC}+, 	{CCCCC}+

and when they have focus (or mouseover):
    sound -- 	bip....bip,	bip..bip,...	beeep.beeep,	boooooooooo


Cheers,
	Gary V Vaughan
-- 
  ___              _   ___   __              _             
 / __|__ _ _ ___ _| | / / | / /_ _ _  _ __ _| |_  __ _ ___ 
| (_ / _` | '_|// / |/ /| |/ / _` | || / _` | ' \/ _` | _ \
 \___\__,_|_|\_, /|___(_)___/\__,_|\_,_\__, |_||_\__,_|//_/
PGP Key from/___/                      /___/               
http://www.cl.cam.ac.uk/PGP/pks-commands.html#extract      
http://pgp.ai.mit.edu/~bal/pks-commands.html#extract

PGP signature