René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[ENH]: Possible improvements for out-of-the-box interactivity","articleBody":"### Problem\n\nCompared to other visualization frameworks, matplotlib has very limited capability for interacting with the plot. I think we could do a bit better here.\r\n\r\nThere are two obstacles related to interactivity in Matplotlib:\r\n1) By design, we have a one-way processing pipeline from data to a visual representation (pixels or vector primitives). Backtracking which data or Artist is responsible for a visual output is possible, but not quite easy. Additionally, any desired visual change requires a complete re-rendering.\r\n2) We have multiple backends and want to provide consistency. This means, we have non-interactive backends that just can't provide interactivity. The interactivity we provide should work across all interactive backends.\r\n\r\n1 is an architecture limitation, that we cannot easily circumvent. This means, we won't be high-perfoming and won't be able to support complex interactions. 2 also limits the complexity of interactions we can practically implement. OTOH it does not mean we cannot provide any interactivity at all. For example, we do have panning and zooming in interactive backends.\n\n### Proposed solution\n\nLet us consider which small improvements we can reasonably make to improve interactive experience. The following list should track interactivity ideas that seem prossible to implement under the current architecture with limited effort. Please feel free to add:\r\n\r\n- [ ] Data tooltip support #23378\r\n- [ ] Support panning and zooming using mouse scroll wheel #20317\r\n- [ ] Toggling data via legend #16796","author":{"url":"https://github.com/timhoffm","@type":"Person","name":"timhoffm"},"datePublished":"2024-08-12T13:01:12.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":29},"url":"https://github.com/28708/matplotlib/issues/28708"}