You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a meta-issue to track and discuss the implementation of all color options exposed by Plotly Express.
This discussion started in #215 but I decided to open a new issue to discuss and track the more general goal of implementing of all color options exposed by Plotly Express, and make sure ridgeplot follows the same conventions laid out by the Plotly Express interface.
Plotly uses color_continuous_scale in Plotly Express functions and colorscale for its object API (e.g. marker.colorscale in go.Scatter)
From the Plotly docs:
legends are visible representations of the mapping between colors and data values. Legend markers also change shape when used with various kinds of traces, such as symbols or lines for scatter-like traces. Legends are configurable under the layout.legend attribute. Legends are the discrete equivalent of continuous color bars
Currently our built-in support for legends is also quite basic. Maybe this is something we could expand on in the future?
Also from the docs:
Most Plotly Express functions accept a color argument which automatically assigns data values to discrete colors if the data is non-numeric. If the data is numeric, the color will automatically be considered continuous.
Is there something we can do to emulate this color behaviour? There seems to be some conceptual overlap between Plotly's color and our colormode...
Plotly Express allows passing a continuous color scale by name just like ridgeplot already does. However, Plotly treats the input as case-insensitive strings, while I don't think we do... (e.g., they allow both'Inferno' and 'inferno'). (REF1)(REF2)
Rename colorscale to color_continuous_scale. Maybe we could deprivate colorscale and support both for a long while?
What is the difference between ridgeplot.list_all_colorscale_names() and px.colors.named_colorscales() (and ColorscaleValidator().named_colorscales)? Why did we use a different name? Document this?
Do we need to do anything special to support cyclical color scales? Maybe they are already supported? Are they included in our ridgeplot.list_all_colorscale_names()? Etc...
Same as above but for diverging color scales... See next point too 👇
This is a meta-issue to track and discuss the implementation of all color options exposed by Plotly Express.
This discussion started in #215 but I decided to open a new issue to discuss and track the more general goal of implementing of all color options exposed by Plotly Express, and make sure ridgeplot follows the same conventions laid out by the Plotly Express interface.
Here are some relevant references:
Notes
Plotly uses
color_continuous_scale
in Plotly Express functions andcolorscale
for its object API (e.g.marker.colorscale
ingo.Scatter
)From the Plotly docs:
Currently our built-in support for legends is also quite basic. Maybe this is something we could expand on in the future?
Also from the docs:
Is there something we can do to emulate this
color
behaviour? There seems to be some conceptual overlap between Plotly'scolor
and ourcolormode
...Tasks:
General
_plotly_utils.basevalidators.ColorscaleValidator
to see if we can use it to replace some of our own custom logic.Continuous color scales
Allow continuous color scale values to be integers too (for 0 and 1). This should be a simple fix to the type annotations.Plotly Express allows passing a continuous color scale by name just like ridgeplot already does. However, Plotly treats the input as case-insensitive strings, while I don't think we do... (e.g., they allow both'Inferno'
and'inferno'
). (REF1) (REF2)Renamecolorscale
tocolor_continuous_scale
. Maybe we could deprivatecolorscale
and support both for a long while?ridgeplot.list_all_colorscale_names()
andpx.colors.named_colorscales()
(andColorscaleValidator().named_colorscales
)? Why did we use a different name? Document this?range_color
#276ridgeplot.list_all_colorscale_names()
? Etc...Discrete color scales
color_discrete_sequence
#275color_discrete_map
#274The text was updated successfully, but these errors were encountered: