http://code.google.com/apis/chart/
Cheers :)
f
-
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourcefor
On Thursday 06 December 2007 10:40:16 am John Hunter wrote:
> I'd like to shoot for another point release next week 0.91.2 to get
> something out that is stable and free of most of the known bugs. Lets
> hold off contributing anything significant in terms of new features
> (minor features easy to
I have a question regarding the plots that are generated in Matplotlib
I was wondering if Matplotlib does autoscaling as well as makes sure
that the number of samples of data to pixels ratio is always an
integer. This is important when you zoom into the plot or readjust
the plot because then it
Darren Dale wrote:
> I just committed changes to the py2exe functions in __init__.py, which had
> references to the old matplotlibdata directory instead of the newer
> mpl-data.\
Thanks!
py2app is broken too. I haven't looked into it yet, but I think it uses
a "recipe" instead of the py2exe f
John Hunter wrote:
> On Dec 6, 2007 12:14 PM, Michael Droettboom <[EMAIL PROTECTED]> wrote:
>> It seems to me that most of the machinery about selecting which
>> numerical package to import can be removed, correct? This is mainly in
>> numerix/__init__.py. The rcParam can be kept around, but mayb
I just committed changes to the py2exe functions in __init__.py, which had
references to the old matplotlibdata directory instead of the newer
mpl-data. This should address bug 1827685, but I don't use py2exe (or
windows) and need someone to test the changes and suggest further
improvements if
And, another goal for layout (if it has not already been achieved) might
be to make it easy to end up with a tight bounding box. That is, to end
up with the plot nicely filling the allotted space, to the extent that
it can given specified aspect ratio. One of the repeated complaints
about mpl
On Dec 6, 2007 12:14 PM, Michael Droettboom <[EMAIL PROTECTED]> wrote:
> It seems to me that most of the machinery about selecting which
> numerical package to import can be removed, correct? This is mainly in
> numerix/__init__.py. The rcParam can be kept around, but maybe we
> should warn if it
It seems to me that most of the machinery about selecting which
numerical package to import can be removed, correct? This is mainly in
numerix/__init__.py. The rcParam can be kept around, but maybe we
should warn if it's not set to numpy since it ain't gonna do what you
asked...
It's not jus
On Dec 6, 2007 8:03 AM, Michael Droettboom <[EMAIL PROTECTED]> wrote:
> It's an open question whether autolayout may start ignoring the adjust
> requests or not as a backward compatibility measure. I still consider
> this stuff a long way off until it's usable in general.
My feeling is that it i
I'd like to shoot for another point release next week 0.91.2 to get
something out that is stable and free of most of the known bugs. Lets
hold off contributing anything significant in terms of new features
(minor features easy to test and unlikely to break code are OK), and
concentrate of clearing
That should continue to work. It will create more space than you
probably want, though, since it will add the manually-added space and
the automatically-added space together.
It's an open question whether autolayout may start ignoring the adjust
requests or not as a backward compatibility meas
re autolayout; how does this affect gcf().subplots_adjust(hspace=1.),
which is how I would make room (where hspace can be adjusted)?
-
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From t
Jeff Whitaker wrote:
> Michael Droettboom wrote:
>> It may be now be tricky to call apply_aspect correctly. With the
>> recent auto-layout changes, it's required to be called after the text
>> layout has been done, but before it has been drawn. What is your use
>> case for calling it outside o
Michael Droettboom wrote:
> It may be now be tricky to call apply_aspect correctly. With the
> recent auto-layout changes, it's required to be called after the text
> layout has been done, but before it has been drawn. What is your use
> case for calling it outside of that? Do you need to set
Michael Droettboom wrote:
> It may be now be tricky to call apply_aspect correctly. With the
> recent auto-layout changes, it's required to be called after the text
> layout has been done, but before it has been drawn. What is your use
> case for calling it outside of that? Do you need to set
It may be now be tricky to call apply_aspect correctly. With the recent
auto-layout changes, it's required to be called after the text layout
has been done, but before it has been drawn. What is your use case for
calling it outside of that? Do you need to set and then use the
aspect-adjusted
Mike: I see that ax.apply_aspect now has a 'position' argument. To
maintain backward compatibility, may I suggest that you make it a kwarg,
with default value None, and then add
if position is None:
position = self._originalPosition
at the top of apply_aspect?
-Jeff
--
Jeffrey S. Whita
18 matches
Mail list logo
