Tim Hoffmann

I understood that. A tutorial for this may be nice, but it's not my scope here. One a side-note: IMHO the "various out of the box things" are quite limited...

> who are you trying to target w/ these out-of-the box interactivity improvements end-users, who just expect a little more interactivity. > my suggestions these suggestions are infrastructure behind the...

> I don't see why anyone would use the web backend (the agg backend web frontend is too slow). To set perspective: I believe it's typically fast enough for one-time...

> 1. making basic cleanups to ipympl and particularly the icons and widgets to make what's already there be cleaner, nicely laid out, and "reasonable looking" in a web browser...

I fully agree that the current structure and naming is confusing. I never remember where the different parts are. I think the `colors` module should only contain basic color tooling...

I fully agree that the current structure is confusing. I can never remember where I find the individual parts. I suggest the following refactoring: - `colors.py` should be reduced to...

`colormapping` should be a package containing submodules, i.e.: ``` matplotlib/ ... colors.py colormapping/ __init__.py norms.py colorizer.py colormaps.py ... cm.py ``` I'm inclined to keep content out of `colormpping/__init__.py`. That means...

I see the point in suggesting to collect everything under colors. It would also have the advantage that norms and colormap classes would not change their location. These are strong...

To keep things simple and better separated, I suggest to start with the separate `colormapping` namespace approach. Until release we can always move things around without too much effort (consciously...

> I don't see what the problem with having a top-level norms.py is. While I agree that 99.99% of the time they are used for colormapping, they are just mathematical...