This is just a vague thought and may not fit into our paradigm at all, but consider that dc/d3 is completely dynamic and you can even set parameters such as the scale on the fly.
So wouldn't it be nice to have a mode that allowed to edit the code and watch the diagram change without reloading? Allowing the d3 transitions to help us see the change?
There are two ways I imagine this could work. One, a function is imbued with client-side state so that when you change parameters, it knows to send the results to the same display widget on the client.
Two is more ggplot-like: have some sort of special operators like what it confusingly calls 'layers' but that modify the original plot, instead of creating a new one. Sort of a += to their +.
From @gordonwoodhull on September 23, 2013 18:28
This is just a vague thought and may not fit into our paradigm at all, but consider that dc/d3 is completely dynamic and you can even set parameters such as the scale on the fly.
So wouldn't it be nice to have a mode that allowed to edit the code and watch the diagram change without reloading? Allowing the d3 transitions to help us see the change?
There are two ways I imagine this could work. One, a function is imbued with client-side state so that when you change parameters, it knows to send the results to the same display widget on the client.
Two is more ggplot-like: have some sort of special operators like what it confusingly calls 'layers' but that modify the original plot, instead of creating a new one. Sort of a += to their +.
Copied from original issue: att/rcloud#113