-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
theme_ggEHD() color palette #14
Comments
One hazard of color palettes is that they often controlled by data mappings, so the place to set them might be in any of a dozen places (notably the scale_color* functions, but also fill, guides, etc). But we can certainly make it easier by providing one or several palette functions. Personally I've been using the palettes from package |
After thinking more about this, I agree that it is probably best to just supply color palettes manually. There are too many places to supply it and too many variations that come up. What I have been doing lately is having a "toolbox" script for whatever project I'm working on that I run whenever I first start R. It loads my standard packages, sets plot parameters, and creates common color palettes that I can then reference easily later. |
I may have overstated my case -- I agree fully that it'd be helpful to include a non-default palette, it just needs some thought to do it right. Even something like
would simplify the other color mapping operations. I don 't mind if this stays open while we think on it more, but your call. |
For sure. Still new to GitHub...sorry, learning how all these buttons work. |
Ah, gotcha. All good. |
The default color palette for ggplot2 is certainly pleasing to my eyes, but not so much so for my color-blind committee member. Consequently, I am consistently changing and color scales to the scale found here. You can see it below:
It might be good practice just to default to this, but I thought it was at least something to open for discussion.
And here's our favorite example plot with the new palette:
The text was updated successfully, but these errors were encountered: