create interactive_* methods

[ianhi]

It would be cool to have interactive_[imshow, pcolormesh, hist,...].
First list:
has a set_data method

• pcolormesh (see https://stackoverflow.com/a/31490420/835607)

• colorbar

  • this is just a pcolormesh internally

• hist (partially in create interactive_hist #73)

  • Optimal implementation will use feat: StepPatch matplotlib/matplotlib#18275 (will give set_data)

• imshow - create imshow function #107

  • needs docs (Make mpl_interactions pyplot-like #119)

• axvline and axhline (axhline and axvline #126)

  • Make mpl_interactions pyplot-like #119 makes these actually useful bc they can paired with other interactive elements
  • https://github.com/matplotlib/matplotlib/blob/fc18cccbb9122ad6d7fc6156ec8f6c455e408d8c/lib/matplotlib/axes/_axes.py#L777

no set_data method

• scatter - add Scatter + tests #102
  • Has set_offsets
• seaborn distplot
• fill between
  each should get their own interactive_[...]_factory and interactive_[...] function
• errorbar
• contour(f)
  • see https://stackoverflow.com/questions/16915966/using-matplotlib-animate-to-animate-a-contour-plot-in-python
  • also see my implementation here https://discourse.matplotlib.org/t/best-way-to-animate-a-contour/22073

Pretty much all of the functions in pyplot could be possibly be included, but the above are probably the most useful.

[ianhi]

These don't all need to be created at once. Some such imshow and pcolormesh make sense to combine into one PR but otherwise they will be probably be made slowly over time

[ianhi]

I think that the factory pattern will allow these to be easily composable but I should make sure of that

[ianhi]

maybe axhline and axvline? but these both return line2D objects so it would for sure mess with relimming

[ianhi]

@TomNicholas I just added contour and colorbar to the list inspired by your comments on t-makaro/animatplot#5

If you're interested I'd be happy to accept a PR for either of them or for anything else.