[DO NOT MERGE] Animations

[rreusser]

A long-running PR to manage progress on animations.

Demo at: https://rreusser.github.io/animation-experiments
Demo source at: https://github.com/rreusser/animation-experiments

[monfera]

@rreusser Looks very nice 🏆

[rreusser]

@monfera Thanks! Just realizing the extent to which I'm only scratching the surface of getting all aspects of this working end to end, but it's a start!

[ncammarata]

Not sure the best way to add this, but I'm very excited by the idea of using animations in my plot.ly plots!

[john-soklaski]

Wow, this looks great. I love the new demos!

[rreusser]

Thanks @john-soklaski! Just got to the step where I need to revisit the tests and figure out what's failing. 😬 A couple more fun ones here:

https://rreusser.github.io/gaussian-mixture-estimator/
https://rreusser.github.io/kmpp/

[rreusser]

Have managed to extend most of scatter traces to persist and transition SVG elements. Here's a demo that includes keys, error bars, points, lines, and fills:

https://rreusser.github.io/animation-experiments/#error-bars-4

The fill/line transitions technically work fine, but they're ugly when the points don't match up just right, so Q:

What are the top priorities?

• fix up lines and fills (reordering fill points or using this trick)
• transition scales and work in some layout properties
• polar plots are totally different and will take work even just to prevent them from totally not working
• declarative structure for setting up frames and a slider or similar to transition between
• per-frame annotations or layout properties (like zooming in on a region in a particular frame)

[rreusser]

Based on quick slack discussion, next up: scale transitions

[etpinard]

@rreusser how are these different to trace.uid ?

Is there a case, in general, where multiple traces would share the same key ?

[rreusser]

trace.uid is a single key per trace. key is an array of keys for every data point in a trace. So if some data points drop out, object constancy is maintained, i.e. https://rreusser.github.io/animation-experiments/#error-bars-4 (if you can ignore the fill/line issue for a moment, the points are matched by key instead of by array index)

[etpinard]

Ha I see. Thanks for the clarification.

Maybe key should default to the calcdata indices of the first plot call?

[rreusser]

So it would default to integer keys, but anything keyable is permissible? (e.g. key=['Argentina', 'Afghanistan', ...])

Edit: Wait, isn't this what d3 does implicitly? If it's not keyed, then it really doesn't need to construct or use keys at all, right?

[etpinard]

but anything keyable is permissible?

Yeah. That sounds right.