Tim Hoffmann

I will come back to this.

I've reduced the PR to moving only two obvious gridspec examples. The rest will be handled in a separate PR.

### Proposal: Use `ax.set_thing()` as a baseline. These are well-known and less experienced people who only learn one interface can discover it easily and can potentially do everything with it....

@tacaswell I've been so bold to push a cleanup commit in the spirit of https://github.com/matplotlib/matplotlib/pull/28653#discussion_r1765659547 > Distinguish variants by desired output instead of calling command. > This gives a better...

I agree that this should be a tuple and not new kwargs. Unfortunately, there's no consistent solution for the order. - `Axes.imshow(extent=)` uses `(left, right, bottom, top)` - `SubplotParams(left, bottom,...

> I think if you are going to do a dictionary, you might as well just do the explicit kwargs? Not quite. The call is comparable complex or lengthy with...

If we use a dict as param it should be described fully in the docstring of the respective param. I know that's not the case for fontdict. You don't get...

## Short summary of options: 1. `pad_inches` supports tuple `(left, right, bottom, top)` (maybe alternative order, but the one given here seems prevalent within matplotlib - though we are not...

It is a major design flaw that `Axes3D` inherits from `Axes`. This brings in lots of functions that were never considered to work for 3D. To make any Artist-creating function...

`stairs` for 3D would basically be analogous to `plot` in 3D. You need to - create a 3D version of the underlying Artist, i.e. a `StepPatch3D` deriving from `StepPatch`. Compare...