luminance 0.6.0.1 → 0.6.0.2
raw patch · 3 files changed
+10/−6 lines, 3 filesPVP ok
version bump matches the API change (PVP)
API changes (from Hackage documentation)
Files
- CHANGELOG.md +4/−0
- luminance.cabal +1/−1
- src/Graphics/Luminance.hs +5/−5
CHANGELOG.md view
@@ -1,3 +1,7 @@+### 0.6.0.2++- Fixed typo in the hackage documentation.+ ### 0.6.0.1 - Fixed `(:*:)` for `UniformBlock`.
luminance.cabal view
@@ -1,5 +1,5 @@ name: luminance-version: 0.6.0.1+version: 0.6.0.2 synopsis: Type-safe, type-level and stateless graphics framework description: This package exposes several modules to work with /GPUs/ in a stateless and type-safe way. Currently, it uses OpenGL as backend hardware technology but
src/Graphics/Luminance.hs view
@@ -188,8 +188,8 @@ -- A 'Geometry' is a /GPU/ version of a mesh. It’s composed of /vertices/, /indices/ and a primitive -- mode used to know how to link vertices between each others. Sometimes, 'Geometry' doesn’t have -- /indices/. That’s called __direct geometry__, because the /vertices/ are supposed to be directly--- used when creating primitives. If you use /indices/, then you have a __indiced geometry__ and the--- /vertices/ can linked by looking at the /indices/ you’ve fed in.+-- used when creating primitives. If you use /indices/, then you have an __indexed geometry__ and+-- the /vertices/ can linked by looking at the /indices/ you’ve fed in. -- -- A 'Geometry' is created with the 'createGeometry' function and a 'RenderCmd' is created with -- 'renderCmd'. You’re supposed to create a 'Geometry' once – while loading your resources for@@ -203,9 +203,9 @@ -- vertices :: ['V' 2 'Float'] -- vertices = -- [--- 'V2' (-0.5) (-0.5)--- , 'V2' 0 0.5--- , 'V2' 0.5 (-0.5)+-- 'vec2' (-0.5) (-0.5)+-- , 'vec2' 0 0.5+-- , 'vec2' 0.5 (-0.5) -- ] -- @ --