GLFW-b: Bindings to GLFW OpenGL library

The GLFW-b package

[Tags:bsd3, library, test]

Bindings to GLFW (http://www.glfw.org/), an open source, multi-platform library for creating windows with OpenGL contexts and managing input and events.

GLFW-b depends on bindings-GLFW (http://hackage.haskell.org/package/bindings-GLFW), which, as of the time of this writing, binds to GLFW 3.1, released 2015-01-18 (http://www.glfw.org/Version-3.1-released.html http://www.glfw.org/changelog.html).

If you've used GLFW < 3 before, you should read the transition guide (http://www.glfw.org/docs/3.0/moving.html).

[Skip to Readme]

Properties

Versions 0.0.1, 0.0.2, 0.0.2.1, 0.0.2.2, 0.0.2.3, 0.0.2.4, 0.0.2.5, 0.0.2.6, 0.0.2.7, 0.0.2.8, 0.0.2.9, 0.0.2.10, 0.1.0.0, 0.1.0.1, 0.1.0.2, 0.1.0.3, 0.1.0.4, 0.1.0.5, 1.0.0, 1.0.1, 1.0.2, 1.1.0, 1.2.0, 1.2.1, 1.3, 1.4, 1.4.1, 1.4.2, 1.4.3, 1.4.4, 1.4.5, 1.4.6, 1.4.7, 1.4.7.1, 1.4.7.2, 1.4.7.3, 1.4.8.0, 1.4.8.1
Dependencies base (<5), bindings-GLFW (>=3.1.2.0) [details]
License BSD3
Author Brian Lewis <brian@lorf.org>
Maintainer Brian Lewis <brian@lorf.org>, Schell Scivally <schell.scivally@synapsegroup.com>
Category Graphics
Source repository head: git clone git://github.com/bsl/GLFW-b.git
Uploaded Mon Oct 3 19:14:14 UTC 2016 by javjarfer
Distributions LTSHaskell:1.4.8.1, NixOS:1.4.8.1, Stackage:1.4.8.1, Tumbleweed:1.4.8.1
Downloads 15649 total (351 in the last 30 days)
Votes
0 []
Status Docs available [build log]
Last success reported on 2016-10-03 [all 1 reports]

Modules

[Index]

Downloads

Maintainer's Corner

For package maintainers and hackage trustees

Readme for GLFW-b

Readme for GLFW-b-1.4.8.1

GLFW-b

Hackage

Description

Haskell bindings to GLFW, an Open Source, multi-platform library for creating windows with OpenGL contexts and managing input and events.

GLFW-b depends on bindings-GLFW, which, as of the time of this writing, binds to GLFW 3.1, released 2015-01-18.

For a demonstration of GLFW-b, see GLFW-b-demo.

When running GLFW-b in GHCI, don't forget to

:set -fno-ghci-sandbox

since GHCI can (and might) run each line of your code in a fresh unbounded thread.

Contributing

This package uses git-flow as development model, in short that means that:

  1. New features should be added to "develop" branch.
  2. "master" branch is reserved for stable releases.
  3. Patches for bugs related with previous releases should always be done in "hotfixes" branch.
  4. All merge commits to master from "hotfixes" should be done using the "--no-ff" flag and from "develop" should avoid merging commits.

Until we have a defined road-map we are going to leave out "release "branches" and "feature branches". For more information about this development model please refer to this site.

Thanks you, and happy coding.