From: Benjamin R. <ben...@ou...> - 2010-06-05 17:41:35
|
Ah, that makes sense. The features of axes_grid1 are very good and I think they make matplotlib very appealing to those who need advanced graphing features. To encourage the use of axes_grid1, shouldn't the examples on the website get updated to reflect this? Would the examples still work with a simple search-and-replace? Thanks for your insight, Ben Root On Sat, Jun 5, 2010 at 12:09 PM, Jae-Joon Lee <lee...@gm...> wrote: > axes_grid was originally started as a supporting module for my other > project. > And it contained mix of unrelated modules (but served for my purpose). > Some of the modules in axes_grid has interfaces not compatible with > matplotlib's own axes. > ( > http://matplotlib.sourceforge.net/mpl_toolkits/axes_grid/users/overview.html#axisline > ) > > axes_grid1 is more like a subset of axes_grid where those incompatible > interfaces are gotten rid of (actually they became a separate package, > axisartist). > > Again, for new project, use axes_grid1 and/or axisartist. > > Regards, > > -JJ > > > On Thu, Jun 3, 2010 at 11:17 PM, Benjamin Root <ben...@ou...> wrote: > > > > > > On Thu, Jun 3, 2010 at 12:22 PM, Jae-Joon Lee <lee...@gm...> > wrote: > >> > >> On Thu, Jun 3, 2010 at 12:52 PM, Benjamin Root <ben...@ou...> wrote: > >> > Well, the link is still not back, so I will probe you a bit further. > >> > You > >> > say that axes_grid is provided for backward compatibility, does that > >> > mean > >> > that I should be using axes_grid1 for new code? I have noticed > >> > differences > >> > in behavior if I import axes_grid versus axes_grid1. For example, my > >> > colorbar labels wouldn't appear unless I used axes_grid1. > >> > > >> > Ben Root > >> > > >> > >> Yes, axes_grid1 is recommended for new code. > >> The "axes_grid" in the svn actually imports the "axes_grid1" and > >> "axisaritst" modules. > >> > >> With axes_grid1, I tried to fix some compatibility issue that > >> axes_grid had with the original matplolib. And I guess the colorbar > >> label issue was one of them. With axes_grid, the colorbar labels are > >> invisible by default, but they are visible in axes_grid1. > >> > >> Regards, > >> > >> -JJ > > > > Thanks, that helps clear up some things for me. I am curious if > axes_grid1 > > is intended to be a final name. When looking at the docs, it almost > seems > > like axes_grid1 is some supporting module while axes_grid is the main > > module, just from a naming convention point-of-view. But, that's just my > > first impression of seeing those modules in that folder. > > > > Ben Root > > > |