What steps will reproduce the problem?
This is a refactoring task.
We currently have multiple state graph visualizations (for the editor, stats
and history tabs) and are about to add another one for gadgets. It would be
nice to find a clean way of doing this that doesn't involve adding a bunch of
optional bells and whistles (for shading, sub-labels, etc.) to the core graph
visualization for each use of the state graph.
Original issue reported on code.google.com by s...@google.com on 21 May 2015 at 2:11
Original issue reported on code.google.com by
s...@google.com
on 21 May 2015 at 2:11