-
Notifications
You must be signed in to change notification settings - Fork 795
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
Update docs to better describe how to use checkboxes and logic-based bindings in general #2926
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
joelostblom
commented
Feb 24, 2023
Comment on lines
+84
to
+85
alt.Size('Hundred_Million_Production:Q'), | ||
alt.SizeValue(25) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I switched the order so that checking the box shows the big budget films instead of removes them
joelostblom
commented
Feb 24, 2023
Comment on lines
+534
to
+540
Binding: Adding Widgets to Drive Interactivity | ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | ||
With an understanding of the selection types and conditions, you can now add data-driven and logic-driven widgets (or "bindings") as input elements to the charts using the ``bind`` option. As specified by `Vega-lite binding <https://vega.github.io/vega-lite/docs/bind.html#input-element-binding>`_, bindings can be of three types: | ||
|
||
1. Point selections can be bound directly to an input element, *for example, a radio button.* | ||
2. Interval selections which can be bound to scale, *for example, zooming in on a map.* | ||
1. Point and interval selections can be used for data-driven interactive elements, such as highlighting and filtering based on values in the data. | ||
2. Sliders and checkboxes can be used for logic-driven interactive elements, such as highlighting and filtering based on the absolute values in these widgets. | ||
3. Interval selections can be bound to a scale, such as zooming in on a map. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this restructuring make sense?
mattijn
approved these changes
Feb 25, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Sprung from discussion in #2871 and resolves #2856.
I tried to update the docs to better reflect the correct usage of these parameters as well as update the gallery examples to use checkboxes correctly (but @mattijn already committed most of that in #2871 already, so mostly docs left here).
https://joelostblom.github.io/altair-docs/user_guide/interactions.html#binding-adding-widgets-to-drive-interactivity