Bug 115888

Summary: Add a color palette based on Color Brewer
Product: LibreOffice Reporter: Allen Downey <downey>
Component: LibreOfficeAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED WONTFIX    
Severity: enhancement CC: heiko.tietze, vsfoote
Priority: medium    
Version: 5.0.3.2 release   
Hardware: All   
OS: All   
Whiteboard:
Crash report or crash signature: Regression By:
Attachments: A color palette based on Color Brewer

Description Allen Downey 2018-02-20 18:10:46 UTC 
Description:
Existing color palettes are not well organized, and don't contain sets of colors that work well together.

I've created a palette based on colors from Color Brewer (http://colorbrewer2.org)

It's available at https://raw.githubusercontent.com/AllenDowney/ProbablyOverthinkingIt2/master/colorbrewer.soc

Actual Results:  
This field is apparently mandatory.

Expected Results:
So is this one.


Reproducible: Always


User Profile Reset: No



Additional Info:


User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36
Comment 1 Allen Downey 2018-02-20 18:11:39 UTC 
Created attachment 140021 [details]
A color palette based on Color Brewer
Comment 2 V Stuart Foote 2018-02-21 15:53:53 UTC 
That is a lovely palette but not clear it is appropriate. You throw away 3 columns with blanks. But even so it is OK down to the first accent row, then looses cohesiveness.

Otherwise Brewer & Wooddruff's ColorBrewer [1] is a special use palette generator of choropleth map color schemes [2]. No real color theme across the whole palette and the organization/sequencing you've chosen in picking generated choropleth maps to string together follows no recognizable color theory.

Also the palette has issues with the color naming for the generated strips--untranslatable.

At 5.3 we provide the tonal.soc (bug 80196), and the freecolour-hlc.soc (bug 104052) structured SOC palettes. And at 5.4 the standard.soc was converted to RYB color model, which for 6.1 the RYB standard.soc was rebuilt (bug 114719) using Eddy's Gossett and Chen implementation [3]. So spend some time with current  6.0.1 build, or a current master to see if those palettes are more to your liking.

Then if you still prefer your palette, fine use it. If you think others would benefit -- clean it up and package as an extension. But believe technical flaws in layout and construction render it unsuitable for inclusion in LO core.

IMHO => WF

=-ref-=
[1] https://github.com/axismaps/colorbrewer/
[2] https://en.wikipedia.org/wiki/Choropleth_map
[3] https://bahamas10.github.io/ryb/
Comment 3 Heiko Tietze 2018-02-21 18:04:35 UTC 
(In reply to V Stuart Foote from comment #2)
> If you think others
> would benefit -- clean it up and package as an extension.

You definitely should do that. Here is a how-to https://design.blog.documentfoundation.org/2017/03/29/libreoffice-extension-export-custom-palette/ 
It's actually about the exporter but should explain how easy it is to create an extension.