-
-
Notifications
You must be signed in to change notification settings - Fork 112
Subplots for all trace types #580
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
Comments
Types of subplots:
Examples of how to subplot various combos of these:
|
Should we consider a new "Subplots" panel which somehow figures out all the subplots and allows us to position them with vertical/horizontal sliders? |
Step 1: let's collect in a comment in this issue information about where in the figure the subplot domain information lives for all the different types of subplots listed above :) |
So it seems domain can be either in layout or in data and it can be either an array of two values or an object: layout.axisname.domain = [0.65, 0.95] layout.axisname.domain = {“y”: [0, 0.9], "x": [0, 0.55]} data[x].domain = {"x": [0, 0.48]} |
Having an extra panel for this would allow us to do things without magic and keep things close to ploty.js. But with a bit of magic... we could make a radio button in the GraphCreatePanel with choices like "Merged" | "Separate subplot" | "Move to the side within same subplot" (with better wording of course), and once that radio is selected, the new axes are created automatically as needed and sliders appear that allow to move your subplot around. That would replace current AxesSelector. |
OK, so here's the spec for how to handle this issue:
Once this is done, there will be a (long!) series of clicks whereby it will be possible to create and position a figure which can contain arbitrary combinations of subplots of any currently-supported type! (i.e. not parcoords, splom, sankey... yet :) |
Finally:
|
If I create a choropleth trace and an atlas map trace, they reuse the same layout.geo object, so domain is shared |
right, but we can change one of them to use a second |
This mock just blows my mind: https://rreusser.github.io/plotly-mock-viewer/#grid_subplot_types So much easier to use grids instead of percentage layouts. We should about how this feature (which I only just learned about!) impacts this design... /cc @VeraZab check out that mock! |
Subsumes #440 |
Once #610 is merged, the only thing left here is to move geo., scene. stuff into subplot panel OR create some SubpotConnectedSections in GraphCreatePanel |
OK, so let's move all the Note that this means that the "Geo Layout" fold will disappear and thus make the geo subplot folds huge, and we'll also have to lightly adapt the |
In an ideal world, users should be able to create and manipulate all subplot variants that plotly.js can create. Certainly it should be possible to create multiple
pie
subplots for example.The text was updated successfully, but these errors were encountered: