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
It seems Vega and Vega-Lite could act as an Intermediate Representation for describing charts.
Thus it makes sense to create a "vega-frontend" using Haskell's algebraic capabilities which can be compiled to a vega specification in JSON. Then a "vega-backend" using Haskell Diagrams package to render those specifications in Haskell as well. Of course the official vega render is already suited to the web world. But Haskell diagrams would be useful in other ways.
The text was updated successfully, but these errors were encountered:
So, at the moment hvega has you essentially build up the JSON specification as you go along (that is, the API can be thought of as a thin wrapper around Aeson). Are you thinking that a module could take the JSON and then map to Diagrams, or would you rather see the types used by hvega be an abstract representation, which then gets converted to JSON (using Vega specification) or some other backend?
It seems Vega and Vega-Lite could act as an Intermediate Representation for describing charts.
Thus it makes sense to create a "vega-frontend" using Haskell's algebraic capabilities which can be compiled to a vega specification in JSON. Then a "vega-backend" using Haskell Diagrams package to render those specifications in Haskell as well. Of course the official vega render is already suited to the web world. But Haskell diagrams would be useful in other ways.
The text was updated successfully, but these errors were encountered: