Artistic Palettes
#11898
Replies: 2 comments 1 reply
-
On the contrary - I think it's the way to go. One small addendum - the palettes should be done in a way that does not rely on Bokeh at all. It should be just data that's obvious to use, with no classes. This way, it would be possible to use it from any Python code, maybe even from old Python versions - not with just the most recent Bokeh version running on top of the most recent Python version. |
Beta Was this translation helpful? Give feedback.
1 reply
-
I really like this idea! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Recently a request for this "artistic" R palette package to be in "Python vis" came by on twitter:
There are also other very nice (to me) artistic palette repos:
I have been interested in and experimenting with using Bokeh for generative art, so having palettes like these in a ready-to-consume format would be appreciated. By me at least, but I expect others might also be interested in them as well, for more "design-focused" usage. So the question is: where could they go? Is there any objection to a separate
bokeh/art-palettes
repository and package under the Bokeh org? I don't want to maintain a published package from my own personal repo (but I do want to publish this as a package).I would not plan to mention these in the main docs beyond passing a sentence with a link to the package, and make it clear in the package docs that the palettes are derived from artistic considerations, not necessarily dataviz principles (athough FWIW the PNWColors claims to be evaluated with chroma.js for color-blind safety).
cc @bokeh/dev @karen-poon @jbednar
Beta Was this translation helpful? Give feedback.
All reactions