- From: Ted Mielczarek <ted.mielczarek@gmail.com>
- Date: Tue, 23 Nov 2004 13:55:07 -0500
On Tue, 23 Nov 2004 09:29:54 -0800, Brad Fults <brad at mipscomputation.com> wrote: > The point is that whether or not showing search result relevance or a user's > quota usage is 90% of the cases where an indicator is needed, there is no > reason > to limit a widget at design time to 90% of its actual scope. There are > certainly > needs for an indicator widget where there are varying degrees of importance > and/or levels of values within the indicator, hence the "slice". > > Putting levels as arbitrary as "good", "bad", and "medium" is irresponsible > and > doesn't take into account other valid uses for the widget, nor future > considerations. Yes, but if no vendor ever implements the last 10% of the spec because it's so complicated, nobody will get to use it anyway. A spec that hits 90% of the use cases and is easier to implement will garner more support from vendors than a spec that hits 100% of the use cases and is impossible to implement. -Ted
Received on Tuesday, 23 November 2004 10:55:07 UTC