On Nov 26, 2014 10:04 PM, Nathaniel Smith n...@pobox.com wrote:
On Wed, Nov 26, 2014 at 9:30 AM, Todd toddr...@gmail.com wrote:
On Sat, Nov 22, 2014 at 12:22 AM, Nathaniel Smith n...@pobox.com wrote:
- Default line colors: The rgbcmyk color cycle for line plots doesn't
appear to be based
On Thu, Nov 27, 2014 at 9:54 AM, Todd toddr...@gmail.com wrote:
On Nov 26, 2014 10:04 PM, Nathaniel Smith n...@pobox.com wrote:
The main differences in requirements are:
- for the color cycle, you want isoluminant colors, to avoid the issue
where one line is glaring bright red and one is
On Wed, Nov 26, 2014 at 1:30 AM, Todd toddr...@gmail.com wrote:
About this, I am not expert so forgive me if this is nonsensical.
However, it would seem to me that these requirements are basically the same
as the requirements for the new default colormap that prompted this whole
discussion.
On 26 Nov 2014, at 07:53 pm, Chris Barker chris.bar...@noaa.gov wrote:
On Wed, Nov 26, 2014 at 1:30 AM, Todd toddr...@gmail.com wrote:
About this, I am not expert so forgive me if this is nonsensical. However,
it would seem to me that these requirements are basically the same as the
On Wed, Nov 26, 2014 at 9:30 AM, Todd toddr...@gmail.com wrote:
On Sat, Nov 22, 2014 at 12:22 AM, Nathaniel Smith n...@pobox.com wrote:
- Default line colors: The rgbcmyk color cycle for line plots doesn't
appear to be based on any real theory about visualization -- it's just
the corners of
On 22 Nov 2014 02:22, Benjamin Root ben.r...@ou.edu wrote:
Some of your wishes are in progress already:
https://github.com/matplotlib/matplotlib/pull/3818
There is also an issue open about scaling the dashes with the line width,
and you are right, the spacing for the dashes are terrible.
Nice!
On 2014/11/22, 9:06 AM, gary ruben wrote:
A few thoughts to add to the excellent ones to date, to do with colorbar
behaviour.
My general comment would be that if the axis tick formatter defaults are
changed not to forget about the colorbar as I typically find it needs
more tweaking than the
I'd like to propose an update to the default boxplot symbology: all black
Q: How much more black could the boxplots be?
A: None. None more black.
(sorry, ben)
On Fri, Nov 21, 2014 at 7:18 PM, Benjamin Root ben.r...@ou.edu wrote:
With regards to defaults for 2.0, I am actually all for breaking
I would be also quite interested in having better defaults. My list of
complains are:
* Easy way to get only two lines for axis (left and down, instead of four)
* Better default font (Source Sans Pro / Source Code Pro for example (open
source))
* Better default colormap
* Better axis limit
Hi all,
Since we're considering the possibility of making a matplotlib 2.0
release with a better default colormap, it occurred to me that it
might make sense to take this opportunity to improve other visual
defaults.
Defaults are important. Obviously for publication graphs you'll want
to end up
Some of your wishes are in progress already:
https://github.com/matplotlib/matplotlib/pull/3818
There is also an issue open about scaling the dashes with the line width,
and you are right, the spacing for the dashes are terrible.
I can definitely see the argument to making a bunch of these visual
I like the idea of aligning a set of changes for 2.0 even if still far
away.
Regarding to backwards compatibility I think that indeed it is important
but when changing mayor version (1.x to 2.0) becomes less important and we
must take care of prioritizing evolution.
Take for example the OO
With regards to defaults for 2.0, I am actually all for breaking them for
the better. What I find important is giving users an easy mechanism to use
an older style, if it is important to them. The current behavior isn't
buggy (for the most part) and failing to give users a way to get behavior
that
13 matches
Mail list logo
