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
Should we continue with the expr stuff? I'm ambivalent... it might be better to make users think about transforms directly, particularly in the context of compound charts. Decision: keep limited expr interface
top-level methods
mark_*
hconcat
,vconcat
,layer
, and associated operator overloadingconfigure_*
add_selection
resolve
add_layer
,add_honcat
,add_vconcat
add_transform
(plusadd_transform_filter
, etc.?)savechart
method, with outputs tohtml
,json
,png
,eps
from_dict
, delegating toalt.Root.from_dict
if necessaryremove default width/height from charts? (Remove default width/height from Chart? #482) use
config.view.width/height
insteadfinalize selection API (Interval selection #463)
Should we continue with the
expr
stuff? I'm ambivalent... it might be better to make users think about transforms directly, particularly in the context of compound charts. Decision: keep limitedexpr
interfacetop-level wrapper for RepeatSpec? done in ENH: add RepeatChart & example #533
Raise useful error when repeating, layering, hconcating, vconcating charts that are invalid.
Make certain error messages are useful (More readable error messages #480)
Make certain that object introspection is as useful as possible (e.g. AnyOf definitions)
sphinx documentation see WIP: Build Infrastructure for Sphinx Docs #552)
Examples
Restore settings in
.travis.yml
(see Fix travis #458)--doctest-modules
flagThe text was updated successfully, but these errors were encountered: