This is one of a series of issues, one for each visualizer, to make sure they are "alpha-ready". The main aspects of this overhaul are:
Does the visualizer handle/request canvas size/aspect ratio gracefully and appropriately for the new ui?
Is the visualizer pushing as much validation down to the per-parameter checks as possible?
Is it doing the appropriate level of resetting/recomputation in presketch vs setup?
Is it using descriptions, warnings, and errors appropriately, and not changing the user's input out from under their keystrokes? (Note that if a human interaction entails a change in another parameter -- for example, if you were binning terms and there were 10K terms then setting bin size to 10 might change number of bins to 1000, while changing the number of bins to 100 would change the bin size to100 -- that's OK; we just don't want to seem to be ignoring or contradicting their immediate keystrokes; instead, we inform the person what's at issue with what they entered.
Is it sufficiently and appropriately responsive to events and input? Does it handle resizes as gracefully as can be in the current scheme?
In some cases, there are accumulated small previously-existing issues that should be addressed as well.
gwhitney
commented
3 weeks ago
This is one of a series of issues, one for each visualizer, to make sure they are "alpha-ready". The main aspects of this overhaul are:
Does the visualizer handle/request canvas size/aspect ratio gracefully and appropriately for the new ui?
Is the visualizer pushing as much validation down to the per-parameter checks as possible?
Is it doing the appropriate level of resetting/recomputation in presketch vs setup?
Is it using descriptions, warnings, and errors appropriately, and not changing the user's input out from under their keystrokes? (Note that if a human interaction entails a change in another parameter -- for example, if you were binning terms and there were 10K terms then setting bin size to 10 might change number of bins to 1000, while changing the number of bins to 100 would change the bin size to100 -- that's OK; we just don't want to seem to be ignoring or contradicting their immediate keystrokes; instead, we inform the person what's at issue with what they entered.
Is it sufficiently and appropriately responsive to events and input? Does it handle resizes as gracefully as can be in the current scheme?
In some cases, there are accumulated small previously-existing issues that should be addressed as well.