[whatwg] Status bars and progress indicators

[Ian Hickson]

On Thu, 23 Sep 2004, Brad Fults wrote:
> 
> > Regardless of the word that ends up being used I think the element 
> > should also have property to tell which value is "GOOD" and which is 
> > "BAD".
> 
> This is the point where we have overstepped the bounds of the element's 
> semantic flexibility. I believe there should be a 
> <progress>/<progressmeter> simply because there is a very common need 
> for exactly that widget. Other indicators such as gauges for quotas, 
> usage, heat levels, etc. should be put in a generic indicator element 
> that can be styled to the author's wishes.
> 
> Whether it be <indicator>, <pie> or whatever,
> 
> <indicator id="engineTemp">
>   <slice id="engineTempCold" min="0" max="140" />
>   <slice id="engineTempGood" min="141" max="220" />
>   <slice id="engineTempHot" min="221" />
> </indicator>
> ...
> indicator#engineTemp { indicator-style-type: vertical-bar }
> indicator#engineTemp slice#engineTempCold { background-color: #00f }
> indicator#engineTemp slice#engineTempGood { background-color: #0f0 }
> indicator#engineTemp slice#engineTempHot { background-color: #f00 }

This seems like overkill for what is essentially just a little bar to show 
the relevant of a search result or the percentage use of someone's quota.


> I'm not in love with the element names here, but I think this structure 
> is necessary for the type of element that some of you are describing. 
> Such notions of "good" and "bad" are completely arbitrary and could just 
> as well be "shoes", "Bolivia", and "jumping".

On a gauge it is very common to see a line beyond which the indication is 
"bad" (or "low", or "high", whichever). I don't think I've ever seen a 
gauge with a level beyond which the result was "shoes" or "Bolivia".

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'