nanovg: Haskell bindings for nanovg

This is a package candidate release! Here you can preview how this package release will appear once published to the main package index (which can be accomplished via the 'maintain' link below). Please note that once a package has been published to the main package index it cannot be undone! Please consult the package uploading documentation for more information.

[maintain] [Publish]

Raw bindings to the OpenGL vector graphics library NanoVG


[Skip to Readme]

Properties

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, 0.7.0.0, 0.8.0.0, 0.8.1.0, 0.8.1.0
Change log CHANGELOG.md
Dependencies base (>=4.8 && <5.0), bytestring (>=0.10 && <0.12), containers (>=0.5 && <0.7), 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
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 2022-08-15T17:00:18Z

Modules

[Index] [Quick Jump]

Flags

Manual Flags

NameDescriptionDefault
examples

Build examples

Disabled
gles3

Build for GLES3. This deactivates GL3 support.

Disabled
gl2

Build for GL2. This deactivates GL3 support.

Disabled
stb_truetype

Use stb_truetype. By default uses freetype.

Disabled

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

Downloads

Maintainer's Corner

Package maintainers

For package maintainers and hackage trustees


Readme for nanovg-0.8.1.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 :)).