>>>>> "Martin" == Martin Spacek <[EMAIL PROTECTED]> writes:
Hey martin, thanks for all these changes.
Martin> to inconsistent behaviour: barh() draws bars vertically
Martin> centered on the y values (ala matlab 6.0), while bar()
Martin> draws bars aligned according to their left edge (not ala
Martin> matlab). I prefer the edge aligning behaviour. It's easy
Martin> to convert from one behaviour to the other, but I had to
Martin> duplicate all the error checking code before conversion,
Martin> which bloated it back up.
Most people prefer the center aligning behavior, at least those who
complained on the list about bar, so when I wrote barh I adopted
this. I tried to fix bar in the process, but ended up running into
some bugs when I tested John Gill's table demo, and so left it as edge
aligned and haven't revisited it since. So my weak preference would
be to have the two functions consistent and center aligned, but he who
does the work usually gets the biggest vote. Maybe others can chime
in.
Martin> And lastly... I find it odd that barh() has the width and
Martin> bottom args (formerly x and y) in that order: barh(width,
Martin> bottom). The general matlab convention is that the first
Martin> argument is the positions, and the second arg is the
Martin> values. So it would make more sense to me to have
Martin> barh(bottom, width). That way, you could switch back and
Martin> forth between bar() and barh() and get the expected
Martin> behaviour without having to switch around the
Martin> arguments. In fact, that's exactly how barh() in matlab 6
Martin> interprets the first two arguments: arg1 is the vertical
Martin> positions, and arg2 is the lengths of the bars at those
Martin> positions. Same goes for matlab's bar() function. As it is
Martin> now in matplotlib, the first and second arguments are
Martin> interpreted differently for bar() and barh()
I was following the convention that the x arg goes first and the y
second, but I'm not wed to this. I don't mind breaking existing code
if this order seems more natural, and since we are mostly emulating
the matlab conventions in bar and barh, it makes some sense to strive
for consistency. Perhaps you could patch the CHANGELOG and
API_CHANGES file along with the rest which explains the changes.
JDH
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
