The lambdacube-engine package

[Tags:bsd3, deprecated, library]
Deprecated. in favor of lambdacube-core

LambdaCube is a 3D rendering engine written entirely in Haskell. It targets newer graphics hardware. The engine uses Ogre3D's mesh and material file format. The main goal of this project is to provide a modern and feature rich graphical backend for various haskell projects (e.g. FRP libraries).


[Skip to Readme]

Properties

Versions 0.1.1, 0.1.2, 0.2.1, 0.2.2, 0.2.3, 0.2.4
Change log CHANGES
Dependencies array (>=0.2.0.0 && <1), base (>=4.0.0.0 && <5), binary (>=0.5.0.1 && <1), bytestring (>=0.9.1.4 && <1), containers (>=0.2 && <1), directory (>=1.0.0.2 && <2), fgl (>=5.4.2.2 && <6), filepath (>=1.1.0.1 && <2), hslogger (>=1.0.7 && <2), OpenGL (>=2.2.3 && <3), stb-image (>=0.1.3 && <0.2), uulib (>=0.9.10 && <1), xml (>=1.3 && <2), zip-archive (>=0.1.1.3 && <1) [details]
License BSD3
Author Csaba Hruska
Maintainer csaba (dot) hruska (at) gmail (dot) com
Stability experimental
Category Graphics
Home page http://www.haskell.org/haskellwiki/LambdaCubeEngine
Uploaded Thu Nov 26 16:42:52 UTC 2009 by CsabaHruska
Distributions NixOS:0.2.4
Downloads 1354 total (28 in the last 30 days)
Votes
0 []
Status Docs not available [build log]
All reported builds failed as of 2015-11-22 [all 5 reports]

Modules

  • Graphics
    • Graphics.LambdaCube
      • Graphics.LambdaCube.AnimationState
      • Graphics.LambdaCube.BlendMode
      • Graphics.LambdaCube.Common
      • Graphics.LambdaCube.Compositor
      • Graphics.LambdaCube.Entity
      • Graphics.LambdaCube.Frustum
      • Graphics.LambdaCube.GpuProgram
      • Graphics.LambdaCube.GpuProgramParams
      • Graphics.LambdaCube.GpuProgramUsage
      • Graphics.LambdaCube.HardwareBuffer
      • Graphics.LambdaCube.HardwareIndexBuffer
      • Graphics.LambdaCube.HardwareOcclusionQuery
      • Graphics.LambdaCube.HardwareVertexBuffer
      • Graphics.LambdaCube.Image
      • Graphics.LambdaCube.Light
      • Loader
        • Graphics.LambdaCube.Loader.CompositorScript
        • Generated
          • Graphics.LambdaCube.Loader.Generated.CompositorScriptScanner
          • Graphics.LambdaCube.Loader.Generated.MaterialScriptScanner
          • Graphics.LambdaCube.Loader.Generated.ResourceScriptScanner
        • Graphics.LambdaCube.Loader.MaterialScript
        • Graphics.LambdaCube.Loader.MeshXML
        • Graphics.LambdaCube.Loader.ParserUtil
        • Graphics.LambdaCube.Loader.ResourceScript
        • Graphics.LambdaCube.Loader.StbImage
      • Graphics.LambdaCube.Material
      • Graphics.LambdaCube.Math
      • Graphics.LambdaCube.Mesh
      • Graphics.LambdaCube.Pass
      • Graphics.LambdaCube.PixelFormat
      • Graphics.LambdaCube.RenderOperation
      • Graphics.LambdaCube.RenderQueue
      • Graphics.LambdaCube.RenderSystem
        • Graphics.LambdaCube.RenderSystem.GL
          • Graphics.LambdaCube.RenderSystem.GL.GLCapabilities
          • Graphics.LambdaCube.RenderSystem.GL.GLGpuProgram
          • Graphics.LambdaCube.RenderSystem.GL.GLIndexBuffer
          • Graphics.LambdaCube.RenderSystem.GL.GLOcclusionQuery
          • Graphics.LambdaCube.RenderSystem.GL.GLRenderSystem
          • Graphics.LambdaCube.RenderSystem.GL.GLTexture
          • Graphics.LambdaCube.RenderSystem.GL.GLUtils
          • Graphics.LambdaCube.RenderSystem.GL.GLVertexBuffer
      • Graphics.LambdaCube.RenderSystemCapabilities
      • Graphics.LambdaCube.Resource
      • Graphics.LambdaCube.SceneGraph
      • Graphics.LambdaCube.Technique
      • Graphics.LambdaCube.Texture
      • Graphics.LambdaCube.TextureUnitState
      • Graphics.LambdaCube.Types
      • Graphics.LambdaCube.Utility
      • Graphics.LambdaCube.VertexIndexData
      • Graphics.LambdaCube.World

Downloads

Maintainer's Corner

For package maintainers and hackage trustees

Readme for lambdacube-engine

Readme for lambdacube-engine-0.1.2

This is all highly experimental. Check out the examples package and
the website for further details.

There is one important feature that none of the examples can use due
to the way cabal deals with data files.  You can specify the paths to
your resources in an ini-style config file, which looks something like
this:

# Comment
[Section]
Zip=path/to/resources-1.zip
Zip=path/to/resources-2.zip
FileSystem=path/to/more/resources/1
FileSystem=path/to/more/resources/2
...

You can use the addConfig function (found in comments in all the
examples) to load this file.