matplotlib-devel Mailing List for matplotlib

On Tue, Mar 25, 2008 at 06:04:41PM -0500, bryce hendrix wrote:
> How stable is the API? We (Enthought) use endo, a custom tool build on 
> top of docutils, to generate our docs currently. We have talked about 
> changing tools in the past, but the need to extend the tools to 
> understand Traits has held us back.
Sphinx is not automated API documentation, like Endo or Epidoc. It is for
manual writing of documentation. It does not compete with Endo or Epidoc,
but complements them by taking a set of rst files and compiling both a
set of searchable web pages, and an indexed pdf for print.
Gaël

Fernando Perez wrote:
> Hey guys,
>
> sorry for the silence, mostly on travel. I just wanted to mention
> that the sphinx machinery seems quite nice, in particular it produces
> both high-quality pdf and client-side searchable html. This is great,
> because it measn that the entire doc set is automatically searchable
> for the users in a convenient manner, even when running offline and
> without the need for any special server config (and in a more
> civilized fashion than brute-forcing grep searches).
>
> Also, Sympy (led by Ondrej), ipython, mayavi2 and at least
> neuroimaging.scipy.org have all committed to using this system, and we
> hope in the future numpy and scipy will follow suit (at least Jarrod
> Millman and Stefan van der Walt, who are doing lots of work on those,
> are fully on board with the idea). It would be really nice if all
> these projects could offer unified, consistent docs to their users,
> and having MPL jump along would be great.
> 
How stable is the API? We (Enthought) use endo, a custom tool build on 
top of docutils, to generate our docs currently. We have talked about 
changing tools in the past, but the need to extend the tools to 
understand Traits has held us back.
Thanks,
Bryce

Hey guys,
sorry for the silence, mostly on travel. I just wanted to mention
that the sphinx machinery seems quite nice, in particular it produces
both high-quality pdf and client-side searchable html. This is great,
because it measn that the entire doc set is automatically searchable
for the users in a convenient manner, even when running offline and
without the need for any special server config (and in a more
civilized fashion than brute-forcing grep searches).
Also, Sympy (led by Ondrej), ipython, mayavi2 and at least
neuroimaging.scipy.org have all committed to using this system, and we
hope in the future numpy and scipy will follow suit (at least Jarrod
Millman and Stefan van der Walt, who are doing lots of work on those,
are fully on board with the idea). It would be really nice if all
these projects could offer unified, consistent docs to their users,
and having MPL jump along would be great.
Cheers,
f

Hi,
I think that "collection._alpha = self.alpha" (or something better)
are missing in ContoutSet.__init__, because _alpha from collections
(Line or Poly) overrides the alpha value the color of
"collection.set_color(color)" found in method "changed" of ContourSet.
Therefore, alpha doesn't work for contours (filled or not).
Nota: If "collection.set_alpha" is used, it fails with line contouring
because self._edgecolors is an empty list.
I hope it can help.
-- 
Stephane Raynaud

On Tue, Mar 25, 2008 at 7:38 AM, Darren Dale <dar...@co...> wrote:
> There was some discussion a while back concerning upcoming changes to the mpl
> documentation: moving the docs into the trunk and updating the website. I
> can't find the thread now, could anyone summarize the current thinking?
> Ondrej Certik recently implemented a sphinx-based documentation for ipython1
> (see http://ipython.scipy.org/doc/ipython1/html/ and
> http://ipython.scipy.org/doc/ipython1/ipython1.pdf), I wonder if we should
> consider doing the same for matplotlib.
I'm definitely up for this or something close to it. We definitely
want rest based docs which live in svn alongside the src distribution.
 If something like sphinx on top of it makes for better documents, I'm
all for it. You may have seen that over the weekend I added a couple
of API rst documents to the doc subdir, with some basic make.py
support for building them into PDFs. If you or anyone would like to
take a stab at getting a sphinx implementation going, have at it.
JDH

For those of you wondering "what is sphinx?" this will save you a few
seconds of searching: http://sphinx.pocoo.org/
The output looks really nice.
Darren Dale wrote:
> There was some discussion a while back concerning upcoming changes to the mpl 
> documentation: moving the docs into the trunk and updating the website. I 
> can't find the thread now, could anyone summarize the current thinking? 
> Ondrej Certik recently implemented a sphinx-based documentation for ipython1 
> (see http://ipython.scipy.org/doc/ipython1/html/ and 
> http://ipython.scipy.org/doc/ipython1/ipython1.pdf), I wonder if we should 
> consider doing the same for matplotlib.
> 
> I haven't had nearly as much time to contribute to matplotlib as I did when I 
> was still in grad school, but I think I will have some free time starting in 
> May and would like to contribute some more over the summer. Now is probably a 
> good time to start considering summer projects.
> 
> Darren
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

There was some discussion a while back concerning upcoming changes to the mpl 
documentation: moving the docs into the trunk and updating the website. I 
can't find the thread now, could anyone summarize the current thinking? 
Ondrej Certik recently implemented a sphinx-based documentation for ipython1 
(see http://ipython.scipy.org/doc/ipython1/html/ and 
http://ipython.scipy.org/doc/ipython1/ipython1.pdf), I wonder if we should 
consider doing the same for matplotlib.
I haven't had nearly as much time to contribute to matplotlib as I did when I 
was still in grad school, but I think I will have some free time starting in 
May and would like to contribute some more over the summer. Now is probably a 
good time to start considering summer projects.
Darren