Jason Grout wrote: > I've recently been working with Karl-Dieter on shifting our axes and > gridline functionality over to the corresponding matplotlib functions, > and exposing the matplotlib object a bit better. I think we are to the > point where we can use comments and a vote on a new strategy for placing > axes. Since this affects some core functionality that is used by lots > of people (especially by lots of non-developers), testing and feedback > is crucial. > > You can try this patch out by applying the second patch at #5448: > http://trac.sagemath.org/sage_trac/raw-attachment/ticket/5448/trac-5448-matplotlib-axes-gridlines.patch
I should mention a few problems with this patch currently: 1. if the axis is on the top or the right, axis labels are messed up (they appear on the bottom or right, respectively). This is possibly a bug in matplotlib. We expect some sort of resolution in the next few days. 2. Lines and scatter plot circles are clipped because the line width and circle radius are not taken into account when adjusting axis limits. Should we automatically change axis limits just a bit to include the line width and circle radius, or should we just not clip these? Not clipping them looks bad when you have frame axes, since then part of your line extends beyond the frame. Not clipping also looks bad when you artificially limit your axes (i.e., using ymin and ymax), since the line is drawn anyway outside of the axes. Does anyone find anything else??? Jason -- Jason Grout --~--~---------~--~----~------------~-------~--~----~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
