| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Sorry, something went wrong.
There was a problem hiding this comment.
I like the style.
I am in two minds whether to add a second plot with a newly registered color sequence or to leave this as a purely reference example of what is available by default.
You can add a sentence that users can register their own sequences as well and point to register. IMHO an example is not too helpful here. The concept "register -> you can query it by name" is straigt forward. The plot itself will not be helpful as you cannot visualize "there's a new element in the registry". That can only be inferred from the associated example code. But as said, the concept is so simple that any example is dilluting the message because of the additional visualization code.
Sorry, something went wrong.
|
Did there used to be a Dark1? |
Sorry, something went wrong.
Sorry, something went wrong.
There was a problem hiding this comment.
Minor style suggestions.
Sorry, something went wrong.
There was a problem hiding this comment.
Take or leave the suggestions.
Sorry, something went wrong.
…563-on-v3.10.x Backport PR #29563 on branch v3.10.x (DOC: add color sequences reference example)
| Back | FazBrowse Home | New Git URL |
PR summary
Introducing the Matplotlib Abacus!
I did not know that the color sequence registry was a thing. Once I did know, the next thing I wanted to know was what sequences are available. This PR adds an example showing all the built in sequences, analogous to the Colormaps reference and List of Named Colors.
I am in two minds whether to add a second plot with a newly registered color sequence or to leave this as a purely reference example of what is available by default.
PR checklist