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
The existing React visualization libraries such as victory or react-vis are more useful for explanatory data visualization projects. However, they have less consistent visual encoding grammars to help users generate different graphs with minimum modifications, and thus rendering them not well-suited for exploratory visualization purposes.
Meanwhile, the Javascript visualization library vega-lite handles the visual encodings particularly well. Therefore, we propose integrating similar approaches to handle axes, fields, and colors.
Note (for @zhusee2 and @tz5514 ) that the pros of this approach is that we can share the same props / scale computation logic to any visualization graph with x-y axis (line/bar/scatter/point...), and let the chart decides what to render with computed scale. With this way we can have consistent props in different charts, which makes changing chart in client code easier.
hsunpei
changed the title
Rewriting the <DataLayer> with better visual encodings
Rewriting the <DataLayer> with better visual encodings
Feb 25, 2019
The existing React visualization libraries such as
victory
orreact-vis
are more useful for explanatory data visualization projects. However, they have less consistent visual encoding grammars to help users generate different graphs with minimum modifications, and thus rendering them not well-suited for exploratory visualization purposes.Meanwhile, the Javascript visualization library vega-lite handles the visual encodings particularly well. Therefore, we propose integrating similar approaches to handle
axes
,fields
, andcolors
.Rewriting the
<DataLayer>
:Original line chart:
=> Line chart with colors: Vega Editor
Dealing with dual axis chart:
@chenesan and I discussed how to achieve drawing similar graphs like vega-lite does in the future.
The text was updated successfully, but these errors were encountered: