Ticket #1709 (closed enhancement: fixed)
Colors used for block highlighting (current running block vs. error-reporting)
|Reported by:||rgs||Owned by:||walter|
|Component:||Turtleart||Version:||Git as of bugdate|
|Severity:||Unspecified||Keywords:||error handling highlighting block|
To enhance visual feedback; it would be nice to have a different color for block highlighting depending on the case.
Known cases where highlighting is used:
1) to show running block
2) when a syntax (or runtime) error is found, to show at which block the error was encountered (and the code path is shown by highlighting the calling blocks in the upper levels of the stack as well).
<walterbender> rgs_: well... right now I precompute the highlight sprites... I suppose I could precompute a 3rd layer... but I worry about performance...
One approach could be, in order to keep performance problems away, to precompute the highlighted blocks used to show the running block and to compute on the fly for the error-reporting case. This makes sense because performance is less important when doing error-reporting (then when running code).
On the other hand, in the future we might want to expose a way to turn on/off highlighting (for the running and error-reporting case). But we should at least have 3 or 4 months of feedback from the field before taking the path of overloading the UI.
Another consideration is what color to use for each case where highlighting is used. One option would be to infer the colors from your Sugar avatar. Another would be to have something static (i.e.: blue for the running block and red for the stacktrace when doing error-reporting).