nanovg: Haskell bindings for nanovg

[ graphics, library ] [ Propose Tags ]

Raw bindings to the OpenGL vector graphics library NanoVG


[Skip to Readme]

Flags

Manual Flags

NameDescriptionDefault
examples

Build examples

Disabled

Use -f <flag> to enable a flag, or -f -<flag> to disable that flag. More info

Downloads

Note: This package has metadata revisions in the cabal description newer than included in the tarball. To unpack the package including the revisions, use 'cabal get'.

Maintainer's Corner

Package maintainers

For package maintainers and hackage trustees

Candidates

Versions [RSS] 0.1.0.0, 0.1.0.1, 0.1.0.2, 0.2.0.0, 0.3.0.0, 0.4.0.0, 0.5.0.0, 0.5.1.0, 0.5.2.0, 0.6.0.0, 0.7.0.0, 0.8.0.0, 0.8.1.0
Change log CHANGELOG.md
Dependencies base (>=4.7 && <5.0), bytestring (>=0.10 && <0.11), containers (>=0.5 && <0.6), text (>=1.2 && <1.3), vector (>=0.11 && <0.13) [details]
License ISC
Copyright 2016 Moritz Kiefer
Author Moritz Kiefer
Maintainer moritz.kiefer@purelyfunctional.org
Revised Revision 1 made by cocreature at 2017-01-08T09:05:00Z
Category Graphics
Home page https://github.com/cocreature/nanovg-hs
Source repo head: git clone https://github.com/cocreature/nanovg-hs
Uploaded by cocreature at 2017-01-04T14:52:43Z
Distributions LTSHaskell:0.8.1.0, NixOS:0.8.1.0, Stackage:0.8.1.0
Reverse Dependencies 3 direct, 2 indirect [details]
Executables example00
Downloads 7959 total (56 in the last 30 days)
Rating 2.0 (votes: 1) [estimated by Bayesian average]
Your Rating
  • λ
  • λ
  • λ
Status Docs available [build log]
Last success reported on 2017-01-04 [all 1 reports]

Readme for nanovg-0.5.2.0

[back to package description]

NanoVG Haskell bindings

Build Status

Currently only the GL3 backend is supported.

A large part of the example bundled with NanoVG is translated into Haskell and bundled as example00.

Most of the bindings directly expose the corresponding NanoVG so look there for more details on the usage.

There is also a diagrams backend using these bindings.

Feel free to open issues if you have any ideas for improvements (or even better PRs :)).