-
-
Notifications
You must be signed in to change notification settings - Fork 404
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 Customizing Plots Docs #2916
Comments
Yes, .options() should replace .opts() in nearly every case, and probably eventually in every case. I've already done that for pyviz.org, but holoviews.org needs it too. I agree with preferring .options() over %%opts as well, but that's a larger task, because it often needs examples to be refactored rather than simply replaced. %%opts has many differences from .options() that need very careful attention, such as whether they work in place or give a new object, the scope of what they affect, whether they apply per type or per object, etc. So helping move the most important docs from %%opts to .options() would be a great service to us! The main remaining benefit of %%opts is tab completion, but with some work that can be fixed too (#2485). |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
http://holoviews.org/user_guide/Customizing_Plots.html
Perhaps could deprecate the .opts() syntax in favor of the .options() because .opts() is very overwhelming, and demonstrate that it's possible to access specific elements with .options()
.options({'VLine': dict(axiswise=True), 'Curve': dict(axiswise=True)})
Also maybe prioritize .options() over %%opts since .options() is portable in notebook and py script.
I can help if wanted!
The text was updated successfully, but these errors were encountered: