On Tue, May 19, 2009 at 12:00 PM, Jae-Joon Lee <lee.j.j...@gmail.com> wrote:
> I think there is no functionality difference between subplot2grid and
> SM Window. And the syntax of the subplot2grid seems much more cleaner,
> especially when you have large number of cells. So, I'm +1 for
> subplot2grid in this regard.
>
> One thing I like about my option 3 is that it can have some benefit
> from the array indexing. For example,
>
>
> >
> >> +-------+---+
> >> | | |
> >> | ax1 |ax3|
> >> | | |
> >> +-------+---+
> >> | ax2 |
> >> +-----------+
> >
>
>
> ax2 = subplot(grid_spec(3,3)[2,:])
>
> Any suggestions?
I'll admit that I wasn't too sure about this when you first introduced it,
but it's growing on me. I could foresee this usage:
#Make grid
ax_grid = grid_spec(3,3)
ax1 = subplot(ax_grid[:2, :2])
#do plot 1
ax2 = subplot(ax_grid[2, :])
#do plot 2
ax3 = subplot(ax_grid[:2, 2])
#do plot3
What I like about this is that it uses fewer keyword arguments and doesn't
add another function with overlapping functionality to the API, but adds
functionality to the function that already handles subplots. I also like
that it makes use of a syntax (slicing) that pretty much everyone has to be
familiar with. I could also see that the grid_spec could cache some
calculations (slight performance benefit) as well as (maybe?) handle what
happens when overlapping axes are requested from the grid.
My 0.02.
Ryan
--
Ryan May
Graduate Research Assistant
School of Meteorology
University of Oklahoma
Sent from Norman, Oklahoma, United States
------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables
unlimited royalty-free distribution of the report engine
for externally facing server and web deployment.
http://p.sf.net/sfu/businessobjects
_______________________________________________
Matplotlib-users mailing list
Matplotlib-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-users
