nanovg: Haskell bindings for nanovg

[ graphics, library ] [ Propose Tags ]

Raw bindings to the OpenGL vector graphics library NanoVG


[Skip to Readme]
Versions 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
Change log CHANGELOG.md
Dependencies base (>=4.8 && <5.0), bytestring (==0.10.*), containers (>=0.5 && <0.7), text (==1.2.*), 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 Fri Jun 22 15:19:56 UTC 2018
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 Sun May 20 18:00:12 UTC 2018
Distributions NixOS:0.6.0.0
Executables example00
Downloads 1725 total (24 in the last 30 days)
Rating (no votes yet) [estimated by rule of succession]
Your Rating
  • λ
  • λ
  • λ
Status Docs uploaded by user
Build status unknown [no reports yet]
Hackage Matrix CI

Modules

[Index]

Flags

NameDescriptionDefaultType
examples

Build examples

DisabledManual
gles3

Build for GLES3. This deactivates GL3 support.

DisabledManual
gl2

Build for GL2. This deactivates GL3 support.

DisabledManual

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

For package maintainers and hackage trustees


Readme for nanovg-0.6.0.0

[back to package description]

NanoVG Haskell bindings

Build Status Hackage

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 :)).