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).
···
On Tue, Mar 3, 2015 at 12:07 PM,
Marin GILLES <mrngilles@…287…>
wrote:
Sure, I’ll be careful about that.
I'm going to go try and design some new interesting
ones.
Maybe adding some styles specific to some plot types
could be useful.
Also some styles specific for some applications
(geoscience, biology)?
If you have any other ideas, please let me know.
– Marin GILLES
It would be good to have styles for "paper" and
“presentation” modes. The former would have smaller ticks,
labels, linewidths, other axis elements that goes into a
journal publication, while the latter with much magnified
elements to be clearly visible on a screen from the back
of a room.
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
···
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).
On Tue, Mar 3, 2015, 12:35 Marin GILLES
<mrngilles@…287… >
wrote:
Le 03/03/2015 18:15, Gökhan Sever a écrit :
On Tue, Mar 3, 2015 at 12:07
PM, Marin GILLES <mrngilles@…287…>
wrote:
Sure, I’ll be careful about that.
I'm going to go try and design some new
interesting ones.
Maybe adding some styles specific to some plot
types could be useful.
Also some styles specific for some applications
(geoscience, biology)?
If you have any other ideas, please let me know.
– Marin GILLES
It would be good to have styles for "paper" and
“presentation” modes. The former would have
smaller ticks, labels, linewidths, other axis
elements that goes into a journal publication,
while the latter with much magnified elements to
be clearly visible on a screen from the back of a
room.
Indeed it would be a
very good idea.
I've seen that already in the seaborn lib I guess.
– Marin GILLES
*PhD student CNRS
* Laboratoire Interdisciplinaire
Carnot de Bourgogne (ICB)
UMR 6303 CNRS - Université de Bourgogne
9 av Alain Savary, BP 47870
21078, Dijon (France) (+33)6.79.35.30.11
✉ marin.gilles@...4632...
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/](http://goparallel.sourceforge.net/)_______________________________________________
Matplotlib-users mailing list
Matplotlib-users@lists.sourceforge.net
[https://lists.sourceforge.net/lists/listinfo/matplotlib-users](https://lists.sourceforge.net/lists/listinfo/matplotlib-users)
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.:
-Tony
···
On Tue, Mar 3, 2015 at 1:37 PM, Marin GILLES <mrngilles@...287...> 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
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.
···
On Wed, Mar 4, 2015 at 6:28 AM, Tony Yu <tsyu80@…287…> wrote:
On Tue, Mar 3, 2015 at 1:37 PM, Marin GILLES <mrngilles@…287…> 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).
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.:
(+33)6.79.35.30.11