Tim Hoffmann

> I just rebased and somehow that broke Circle and Appveyor 😕 Try rebasing again? 🤷

🚀 @rcomer for digging through the details!

The initial description says > **NOTE: This PR has been superseded by** #28454 Is there still something relevant here, or can we close and move the discussion to #28454.

Can you please try to summarize the mapping logic for multivariate and 2D colormaps. I cannot follow the architecture between the implementation details and mixing with ScalarMappable logic. The current...

**Disclaimer: This contains some fundamental thoughts beyond the concrete MultiVar case, but since MultiVar requires significant architecture changes any, I believe it's worth looking at the whole picture.** I have...

Thanks for the detailed answer, I'll have a closer look later. Re: 3. Multiple mappables with one colorbar: I'm referring to https://matplotlib.org/stable/gallery/images_contours_and_fields/multi_image.html. T.b.d. maybe this can be slightly simplified nowadays,...

My main point is that variation and complexity grow significantly as soon as we dive into these advanced mappings. I suspect generalizing (ScalarMappable -> Mappable) does not cut it. Instead,...

Not completely thought through, but AFAICS `ColorableArtist` has a very minimal interface, defining the `mapper` attribute and possibly a data access backchannel so that we can do autoscaling and solve...

> > We will continue to have a mixin that provides the current ScalarMappable to the two current use cases (_AxesImage and Collection). > > This is not quite clear...

> Would you then like to depreciate the `ScalarMappableShim` at some point Realistically: no. They are used too much to justify burden the users with a migration. We may discourage...