stylesheet can have any number of rules.

The initial syntax is designed only for `artist` primitives. It does

not address the question of how to set properties on `container` types

(whose properties may themselves be `artists` with settable

properties), however, a future solution to this could simply be nested

Selectors

Matplotlib primitives

This will form the initial selectors which stylesheets can use.

``FigureManagerBase`` and ``ShowBase``.

1. ``FigureManagerBase`` has **three** jobs at the moment:

1. The documentation describes it as a *``Helper class for pyplot

mode, wraps everything up into a neat bundle''*

2. But it doesn't just wrap the canvas and toolbar, it also does

2. ``ShowBase`` has two jobs:

1. It has the job of going through all figure managers registered

in ``_pylab_helpers.Gcf`` and telling them to show themselves.

2. And secondly it has the job of performing the backend specific

3. Now that ``FigureManagerBase`` has no backend specifics in it, to

rename it to ``FigureManager``, and move to a new file

``backend_managers.py`` noting that:

|FigureManagerBase(canvas, num) |FigureManager(figure, num) |``WindowBase(title)``|Notes |

| | | | |

|destroy |calls destroy on all |destroy | |

| |components | | |

|full_screen_toggle |handles logic |set_fullscreen | |

| | | |does nothing. |

| | | |subclasses of FigureManagerBase |

|mainloop |begin | |

| | |automagically|

| | |when no more |

| | |instances of |

| | |the subclass |

| | |exist |

| | |to |

| | |Gcf.show_all |