Eric Firing wrote: > Michael Droettboom wrote: >> That's right, Eric. I think having resolution be an attribute of the >> artist (and not the projection) is the "path" of least resistance >> here. To clarify, however, the interpolation (more specifically, >> whether to interpolate) should remain a function of the projection, >> not the path. That's the important point that lead to it ending up >> in the wrong place in the first place. If we aim to keep the >> generalization that all grid lines are the same kind of object >> regardless of the projection, and therefore set a high resolution >> parameter on all the grid lines, we wouldn't want this to slow down >> the standard rectilinear axes. As long as the standard axes don't >> obey the parameter, then would should be fine. It's somewhat >> confusing, but I also am seeing this the resolution parameter on >> artists as more of an implementation detail than a public API. If >> someone wants to interpolate their data, IMHO that should be the >> user's responsibility, since they know the best way to do it. This >> functionality isn't really about data points, IMHO. > > Mike, > > Thanks for taking care of this so quickly. > > Although I agree that _interpolation_steps is a low-level, > implementation-dependent attribute (which might not be the right > specification if interpolation were changed to take advantage of > Bezier curves, for example), I think that some sort of > "follow_curvilinear_coordinates" public Artist attribute would be > desirable. For example, one might want to plot a set of arcs, or > arc-shaped patches (warped rectangles) on a polar plot. It would be > nice to be able to do this using lines, line collections, rectangle > patches, or rectangle collections, by adding a single kwarg to set > that attribute. Then it would be up to each Artist to use that > attribute to set _interpolation_steps or whatever implementation > mechanism is in place. Possibly it does not make sense as a general > Artist attribute but should be restricted to a subset, but it is > probably simpler to put it at the Artist level and then selectively > apply it. Agreed with all of the above -- all the infrastructure is now in place to do this. I was most concerned with fixing the bug (seeming lack of gridlines) first, and then getting this improvement in later (probably not till next week).
Cheers, Mike -- Michael Droettboom Science Software Branch Operations and Engineering Division Space Telescope Science Institute Operated by AURA for NASA ------------------------------------------------------------------------------ Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://www.creativitycat.com _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
