|
From: Tony S Yu <to...@MI...> - 2008-07-01 04:13:42
|
On Jun 30, 2008, at 10:10 PM, John Hunter wrote: > I'd love for you to take the lead on this. Given my (and other > developers) constraints on time, we'll have only limited time to help, > but hopefully we can give you some pointers when you get stuck. I don't know if I'm the best person to be taking this on, but if no one else is interested, then I'd be happy to take a shot at it. > >> Current Limitations: >> ================ >> * the frame can only be placed on the borders of the axes (mainly >> because I >> don't know how to move the tickers anywhere else). > > Look at how the transforms are set in the axis.Axis class for the > tickers - the ticks and labels have "blended transforms" which blend > data coords and axes coords. That reminds me: does it make more sense to have the frame as an attribute/child of each axis (just as ticks are attributes of each axis)? It seemed more appropriate to me, but I just used the `frame` in axes because it was already defined. > It would be extremely useful if > you could develop and extensible API for axis handling (so one could > incorporate some of these Tufte extensions and related ideas at the > *user* level even if they are not built in, though we'd probably > supply some by default or by example) I didn't really expect the Tufte-style frames to be incorporated into the core; Incidentally, my initial goal was just to play around with these Tufte-style frames, not to write a Frame class. > Keep us posted! Will do. Thanks for your comments. -Tony |