Re: [matplotlib-devel] Documentation: New plot directive

[Darren D. <dar...@co...>]

On Friday 13 June 2008 9:54:58 pm you wrote:
> On Fri, Jun 13, 2008 at 3:20 PM, Darren Dale <dar...@co...> 
wrote:
> > I just deleted the static_figs directory from svn, and moved the contents
> > into pyplots. The generated figures were committed to svn as well, so
> > they should not be auto-generated. This way we can consistently use the
> > nice plot directive to include all of our figures. I think there should
> > be no problems with this transition, but if you see one, please let me
> > know.
>
> I think we can make it work, but there are some minor hurdles.  It is
> a little brittle in my view to include auto-generated PNGs alongside
> svn pngs because it makes cleaning hard (we currently have the same
> problem in the _static dir with the mathtext pngs).

How often does cleaning need to be done? Can "svn up" be a part of the 
cleaning process?

> The other problem 
> is that when I went to implement your svg suggestion, which is a good
> one (ditto for ps links), I bumped into some not implemented errors
> since we don't have draw_tex for svg and some latex runtime problems
> when I tried to build the ps since I don't have the right fonts.  All
> of this can be worked around, but it will take a little work.  I have
> to run now...
>
> We could have a little extra meta data stored, tagging certain files
> that should not be auto-generated for certain extensions....
> Perhaps we should introduce a new plot directive option, much like
> include-source, which  could be used to suppress auto-gen, or exclude
> certain targets.
>
> .. plot:: tex_unicode_demo.py
>
>    :include-source:
>    :no-autogen:
>
> .. plot:: tex_unicode_demo.py
>
>    :include-source:
>    :exclude-backends: svg, gdk
>
> I'll ponder this over the weekend.

May I suggest a third alternative, :exclude-formats: instead of backends.

Darren