matplotlib-devel Mailing List for matplotlib

On Feb 19, 2015 1:39 AM, "Nathaniel Smith" <nj...@po...> wrote:
>
> On Feb 16, 2015 3:39 PM, "Eric Firing" <ef...@ha...> wrote:
> >
> > On 2015/02/16 1:29 PM, Michael Waskom wrote:
> >
> > > Nathaniel's January 9 message in that thread (can't figure out how to
> > > link to it in the archives) had a suggestion that I thought was very
> > > promising, to do something similar to Parula but rotate around the hue
> > > circle the other direction so that the hues would go blue - purple -
red
> > > - yellow. I don't think we've seen an example of exactly what it would
> > > look like, but I reckon it would be similar to the middle colormap
here
> > >
http://earthobservatory.nasa.gov/blogs/elegantfigures/files/2013/08/three_perceptual_palettes_618.png
> > > (from the elegant figures block series linked above), which I've
always
> > > found quite attractive.
> >
> > Certainly it can be considered--but we have to have a real
implementation.
>
> While I hate to promise vaporware, I actually was planning to have a
> go at implementing such a colormap in the next few weeks, based on
> optimizing the same set of parameters that viscm visualizes... FWIW.
>
> Are we planning to make other default appearance changes at the same
> time? The idea of changing the color cycle and/or dot-dash cycle has
> already come up in this thread, and this earlier thread proposed
> several more good ideas [1]:
>
http://thread.gmane.org/gmane.comp.python.matplotlib.devel/13128/focus=13166
>


If the goal is still to put all the appearance-related changes in a single
release (to simplify changes to downstream unit tests), but nobody has
stepped up to make changes except to the colors, might it be possible to
just adopt the default seaborn style (except for colors, of course)?  If
anybody is strongly motivated to make changes they can, but if nobody does
there would still be a good, modern, pleasant-looking style used by default.

It sounds like you are on the right path, and you do raise some interesting
points. I would certainly be open to accepting improvements to the
animation framework to facilitate this work. As for the gray vs. white
backgrounds, I am not all that familiar with how that is handled, but IIRC,
the non-interactive backends obtain the background color from the rcparams.

I would love to see a PR for your efforts so far. An SVG animator would
also be valuable as a way to add unit-tests to the animation framework
since it would be easier to do comparisons, I would think.


On Fri, Feb 27, 2015 at 11:09 AM, tbhartman <tbh...@gm...> wrote:

> I trust this is an appropriate place; this is my first time on this
> listserv.
>
> I want to add the ability to export an animation in SVG format so that I
> have a vectorized animation.  From what I've been able to discern, this
> hasn't been done yet.  I may have many questions related to this, so if
> someone is familiar with this section of the code and would be able to
> answer additional questions in the future, please let me know.
>
> My first hurdle is how to extract each frame of the animation.  I believe I
> need to make a new class and inherit MovieWriter.  However, MovieWriter is
> setup to write an image to a file for each frame, then stitch those images
> together (through a pipe to an external tool).  But in order to add
> animation to the SVG, it will be much easier for me to have an XML tree as
> an object for each frame, rather than an XML file, so that I do not need to
> re-parse the XML.
>
> Here is where I am at:
> * I've modified backend_svg.py:
>   - an XMLBuilder class now builds the tree from the renderer (previously,
> the XML data was written directly through XMLWriter)
>   - currently, I have the svg backend (mostly) backward compatible so that
> I
> can write images to file in the normal way.  I have not run the example
> tests yet, but need to eventually.
>   - I added a draw method to FigureCanvasSVG which returns the XML tree
> * I've modified animation.py:
>   - added SVGWriter class which inherits MovieWriter
>   - SVGWriter modifies setup method so that an external process is not
> started
>   - SVGWriter.grab_frame method grabs the XML tree (rather than printing to
> a file) via FigureCanvasSVG.draw
>   - SVGWriter.cleanup goes through the XML trees and adds 'set' XML
> elements
> to create the animation
>     * basically I copy the main group of each frame to a new XML tree and
> make it's "opacity" CSS attribute 1 for the duration of that frame.  It is
> a
> hack to get the rest working...I'd like to actually go into the tree and
> only change the data that changes in each frame.
>
> I am at the point where I can get an SVG animation out of the moviewriter
> example at:
>
> http://matplotlib.org/examples/animation/moviewriter.html
>
> However, FigureCanvas.draw does not seem the appropriate place for this.
> Case in point, the background is the default gray rather than white (which
> you get if you savefig).  Any thoughts on the best way to do this?
>
> -Tim
>
>
>
>
> --
> View this message in context:
> http://matplotlib.1069221.n5.nabble.com/animation-in-SVG-tp45021.html
> Sent from the matplotlib - devel mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming The Go Parallel Website,
> sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for
> all
> things parallel software development, from weekly thought leadership blogs
> to
> news, videos, case studies, tutorials and more. Take a look and join the
> conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>