I can join this Thursday if we start with the discussion on timers.
If we can start 1 hour earlier (14:00 UTC, 9 am ET, 23:00 in Japan) that would
be even better.
-Michiel.
On Mon, 1/13/14, Michael Droettboom wrote:
Subject: [matplotlib-devel] Mee
I'm fine with starting the meeting an hour early. How about others?
Mike
On 01/14/2014 04:57 AM, Michiel de Hoon wrote:
> I can join this Thursday if we start with the discussion on timers.
> If we can start 1 hour earlier (14:00 UTC, 9 am ET, 23:00 in Japan) that
> would be even better.
> -Mic
That would actually work a little bit better for me... I just have to
remember to get into work a little bit earlier.
Ben
On Tue, Jan 14, 2014 at 11:36 AM, Michael Droettboom wrote:
> I'm fine with starting the meeting an hour early. How about others?
>
> Mike
>
> On 01/14/2014 04:57 AM, Michie
I'll probably not be able to swing 6am on the west coast, but other folks
are more important for this call, I think :)
Jake
On Tue, Jan 14, 2014 at 8:51 AM, Benjamin Root wrote:
> That would actually work a little bit better for me... I just have to
> remember to get into work a little bit e
Jake: I'd definitely like to get you into one of these calls at some
point. If you're able to pop in late, that would still be great -- or
we can save that for another date. Trying to get Japan, three NA
timezones and the UK all together is challenging ;)
In any event, with Thomas, Ben, Mich
Thanks - we'll make it happen at some point.
Perhaps I can give the seed for a discussion: the stuff I've been doing
with mpld3 is a lot of fun, but it's fundamentally limited by the fact that
I have to dig around the internals of the figure object to find the
relevant information to construct a p
On 1/14/14, 1:30 PM, Jacob Vanderplas wrote:
> Ugly hacks aside, I think all of this points to a general desire for a
> new type of backend-like hook that can export dynamic plot elements in
> data coordinates, and static plot elements in figure coordinates. An
> enhancement in that direction coul
I'm sure it's obvious, but the backend API was never really designed
with this in mind. It was designed for "dumb" things like screens and
printers that know about simple primitives like lines and text, but not
much else. From that, I don't think it makes much sense to change or
even extend t
On Tue, Jan 14, 2014 at 12:04 PM, Michael Droettboom wrote:
>
> I hope all of the above makes sense...
>
Definitely makes sense: what I've built-up in mpld3 is essentially
something that mimics this sort of visitor pattern, though it misses some
things because of the draw-time difficulties you me
> What I'd love to see is some enhancement of the backend framework where
> there are some extra flags and information passed to the renderer: i.e. for
> each draw command, we need to know whether the drawn object should be linked
> to static figure coordinates or to dynamic axes/data coordinates.
I have another long-simmering feature request along these lines: if
Matplotlib were to evolve a formal DOM-like figure structure like mentioned
above, it would be cool if this structure retained more semantic
information about the visualization itself. By this, I mean that many
high-level commands
11 matches
Mail list logo
