Hackage :: [Package]

rigel-viz: A mid-level wrapper for vega-lite

[ bsd3, data-science, graphics, library, visualization ] [ Propose Tags ] [ Report a vulnerability ]

A mid-level wrapper for vega-lite. Please see the README for details

[Skip to Readme]

Downloads

Maintainer's Corner

Package maintainers

For package maintainers and hackage trustees

Candidates

  • No Candidates
Versions [RSS] 0.1.0.0, 0.2.0.0
Change log changelog.md
Dependencies aeson (>=1.4.2.0), base (>=4.7 && <5), bytestring (>=0.10.8.2), colour (>=2.3.4), containers (>=0.6.0.1), text (>=1.2.3.1) [details]
Tested with ghc ==8.6.3
License BSD-3-Clause
Copyright (c) Marco Zocca, 2019
Author Marco Zocca
Maintainer ocramz fripost org
Category Graphics, Data Science, Visualization
Home page https://github.com/ocramz/rigel-viz
Source repo head: git clone https://github.com/ocramz/rigel-viz
Uploaded by ocramz at 2019-02-25T10:57:24Z
Distributions
Downloads 1281 total (8 in the last 30 days)
Rating (no votes yet) [estimated by Bayesian average]
Your Rating
  • λ
  • λ
  • λ
Status Docs available [build log]
Last success reported on 2019-02-25 [all 1 reports]

Readme for rigel-viz-0.2.0.0

[back to package description]

rigel-viz

Build Status

🌟 Rigel (also called Beta Orionis) is the seventh-brightest star in the night sky, slightly less visible than Vega 🌟

A (mid-level, simplified, opinionated) Haskell wrapper for vega-lite, currently targeting version 3 of the vega-lite schema.

Aims / definitions

  • mid-level :

    • types which can take one of a few possible values are represented by sum types, not by strings.
    • glyph colours are encoded via the colour Haskell library.

  • simplified : the generated vega-lite JSON is not normalized, i.e. has some redundancies. This reflects the internal representation but also makes it easier to reason "locally" (i.e. code sections don't visibly exploit inheritance from higher layers).

  • opinionated : part of the vega-lite API is not used at all. For example, there is no support for data preprocessing (e.g. summarization etc.). This forces the user to use the host language for preprocessing, which is bound to be more expressive and robust.