Hi James,
Thanks for sharing the MEP - it's a really interesting idea, and the MEP
itself looks like a good start.
I'd strongly encourage you to stick with standard CSS syntax/behaviour
instead of extending it. For example, the selector of "Axes.ylabel" would
be more consistent as "Axes .ylabel"
On 20 July 2014 14:23, jamesramm wrote:
> We cannot stick with the 'standard' CSS syntax by necessity, simply because
> the standard CSS selectors and properties are defined from HTML and do not
> match with matplotlib.
> I.E we want to select by artist type, which doesn't exist in HTML and use
>
On 21 July 2014 14:48, jamesramm wrote:
> You've just noted it: Line2D isn't a CSS selector
CSS doesn't define any particular element names - it just operates on
element names in a document tree. So a standard CSS parser will work just
as well with "line2d { ... }" as it would with "h1 { ... }"
On 21 July 2014 17:40, R Hattersley wrote:
> In the case of two Axes, the CSS version would be:
>
> Axes#axes1 {
> border: 1px solid black;
> }
>
> Axes#axes2 {
> border: 2px dashed green;
> }
>
>
Or if you want to borrow from more advanced selector sy
You need an extra "matplotlib" ... https://waffle.io/matplotlib/matplotlib
On 17 January 2015 at 19:29, Thomas Caswell wrote:
> Hey all,
>
> We have set up waffle.io to try and help manage our issues:
> https://waffle.io/matplotlib/
>
> If you have commit rights, you should be able to move the c
