stuff to try and finish before the workshop:

• We should use __call__ on graphic feature to get the actual data  #91
• docs
• demo with the following, a gridplot and an ImageWidget
  • gridplot:
    • behavior side and front, heatmap, stacked lineplot, single lineplot which shows only the current selection, stacked lineplot where each line is a trial of the selected component, PCA, downstream analysis
  • imagewidget:
    • mcorr, RCM, etc. with contours that interact with the stacked lineplot, single lineplot and heatmap
• high level interactivity, Interactivity attempt 4 #93
  • very high level interactivity API #39
• autoscale camera for data w.r.t. data bounds
  • done in added camera auto-scaling, examples work :D #80
• See how "big_camera" settings work as the default with not-so-large near & far planes, notes from meeting with pygfx devs #62
  • setting PlotArea.controller.distance = 0 seems to have fixed it, it was merged in added camera auto-scaling, examples work :D #80
• Heatmap with tiling pygfx.Image, Handling large images pygfx/pygfx#360
• API renaming where necessary
• better handling of color args to Graphic objects
  • indexable graphic attributes #78
  • need to make new PR after very high level interactivity API #39 to make this work with Collections, LineStack #76 (comment)
• LineStack
• Make LineCollection better
• very long LineGraphic object that changes position with a slider. Can just make a widget which takes an existing IntSlider as an argument and automatically connects the observe to itself. Exclude in scene bbox calculation, or put it in a diff scene. Make it an overlay of 2 lines, thick with low alpha and thin with high alpha on top.
• LinearSelector and/or RectangleSelector, see for ideas: notes from meeting with pygfx devs #62
• histogram widget for images (needs RectangleSelector) - we have vmin vmax sliders for now