From: jamesramm [jamessr...@gmail.com]
Sent: Friday, September 05, 2014 7:00 AM
To: matplotlib-devel@lists.sourceforge.net
Subject: Re: [matplotlib-devel] MEP26: Artist-level stylesheets
It would be great if we can see the code for the style system.
However, for integration into M
It would be great if we can see the code for the style system.
However, for integration into MPL, rather than something which 'sits on top'
of the existing API (I presume you are therefore working with getter/setter
functions), the MEP I'm proposing is also trying to achieve the seperation
of the
, August 10, 2014 12:40 AM
To: matplotlib-devel@lists.sourceforge.net
Subject: Re: [matplotlib-devel] MEP26: Artist-level stylesheets
I have updated MEP26 to include discussion on 'decoupling' the style from
artists and having a generic Style class.
(copied over from the github issue):
I have updated MEP26 to include discussion on 'decoupling' the style from
artists and having a generic Style class.
(copied over from the github issue):
I have been thinking that a good way to get stylesheets in, would be if the
'style' of an artist was entirely independent.
I.E a single propert
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 syntax, you could do
fun stuff like:
Axes:
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 { ... }"
As a side note, SVG already has specs which extend css to apply to 2D graphics:
www.w3.org/TR/SVGTiny12/styling.html
so we don't need to entirely re-inventing the wheel.
On Mon, Jul 21, 2014 at 9:48 AM, jamesramm wrote:
> R Hattersley wrote
> I'm not sure what it is about CSS syntax that isn't
R Hattersley wrote
> I'm not sure what it is about CSS syntax that isn't up to the job.
> Forexample, SVG works with standard CSS syntax
> (seehttp://www.w3.org/TR/SVG/styling.html#StylingWithCSS). Perhaps we just
> havea different view of what constitutes CSS vs. HTML/SVG/whatever.The
> example in
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
>
Nelle Varoquaux wrote
>> 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" (or perhaps "Axis.y .label").
>>
>
> I actually think we need to focus on something e
Hi James,
> Thanks for sharing the MEP - it's a really interesting idea, and the MEP
> itself looks like a good start.
>
It is indeed a very interesting idea, and a challenging one! Thanks for
tackling this problem.
> I'd strongly encourage you to stick with standard CSS syntax/behaviour
> ins
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"
12 matches
Mail list logo
