|
From: Todd <tod...@gm...> - 2015-03-04 12:56:26
|
On Wed, Mar 4, 2015 at 6:28 AM, Tony Yu <ts...@gm...> wrote: > > > > On Tue, Mar 3, 2015 at 1:37 PM, Marin GILLES <mrn...@gm...> wrote: >> >> Le 03/03/2015 18:53, Thomas Caswell a écrit : >>> >>> I was thinking of the stand alone repository to just store the style files as the style module handles the loading pretty well. >>> >>> The main motivation for this would be to decouple the release cycle of the styles (which can be very fast) from the library (which needs to be slower). > > <snip> > >> >> Maybe a dumb question, but I'm quite new to this... >> Can this be integrated in mpl afterwards? Or does it needs to be a standalone package that you install on its own? >> If it can be integrated, how? >> Thanks >> Marin Gilles > > > Any stylesheet could easily be integrated afterwards, but the separate repo would allow faster releases, as Thomas suggests above, and also more experimentation. It would probably make sense to integrate just the cream of the crop from the style repo into Matplotlib-proper, but it'd still be easy to use the less popular ones. For example, you wouldn't even have to install the style repo---you can pass a url to `matplotlib.style.use`. > > The separate repo could also incorporate a default comparison page to quickly decide on the most appropriate stylesheet; e.g.: > > https://github.com/tonysyu/matplotlib-style-gallery > > -Tony > > Another advantage of a separate repo is that it would make it easier for multiple projects to participate. The process could be set up so that projects like seaborn, ggplot, and prettyplotlib could keep their stylesheets in the same project, and have the stylesheets project have a release whenever any project needs to update stylesheets. Using a "master is always stable" development model would make that easier. |