Difference between revisions of "GPipe"
(Collada added) |
|||
(9 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
== What is GPipe? == |
== What is GPipe? == |
||
− | [http://hackage.haskell.org/package/GPipe GPipe] is a library for programming the GPU (graphics processing unit). It is an alternative to using OpenGl, and has the advantage that it is |
+ | [http://hackage.haskell.org/package/GPipe GPipe] is a library for programming the GPU (graphics processing unit). It is an alternative to using OpenGl, and has the advantage that it is functional and statically typed as opposed to OpenGl's inherently imperative style. Another important difference with OpenGl is that with GPipe you don't need to write shaders in a second shader language such as GLSL or Cg, but instead use regular Haskell functions on the GPU data types. GPipe uses the same conceptual model as OpenGl, so if you already know OpenGl, getting up to speed with GPipe is quick! |
+ | |||
+ | == Version 2 == |
||
+ | |||
+ | In 2015, a new major version of GPipe was realeased. Read the announcement [http://tobbebex.blogspot.se/2015/09/gpipe-is-dead-long-live-gpipe.html here on the GPipe blog]! |
||
== Examples and tutorials == |
== Examples and tutorials == |
||
+ | A comprehensive tutorial in five parts is now available for GPipe 2: |
||
⚫ | |||
+ | |||
+ | * [http://tobbebex.blogspot.se/2015/09/gpu-programming-in-haskell-using-gpipe.html Part 1 - Hello world] |
||
+ | * [http://tobbebex.blogspot.se/2015/09/gpu-programming-in-haskell-using-gpipe_11.html Part 2 - Buffers and arrays] |
||
+ | * [http://tobbebex.blogspot.se/2015/10/gpu-programming-in-haskell-using-gpipe.html Part 3 - Shaders and primitive streams] |
||
+ | * [http://tobbebex.blogspot.se/2015/10/gpu-programming-in-haskell-using-gpipe_21.html Part 4 - Textures and samplers] |
||
+ | * [http://tobbebex.blogspot.se/2015/11/gpu-programming-in-haskell-using-gpipe.html Part 5 - Drawing] |
||
+ | |||
+ | * Quake 3 map viewer using GPipe 2, sources on [https://github.com/csabahruska/gpipe-quake3 GitHub]. |
||
+ | |||
+ | Use at least version 2.1.3 for the examples in these. |
||
+ | |||
+ | == GPipe 1 Examples and tutorials == |
||
+ | |||
+ | '' Note that these only applies to the older deprecated version of GPipe '' |
||
+ | |||
⚫ | |||
* [http://hackage.haskell.org/package/GPipe-Examples GPipe-Examples package], by Kree Cole-McLaughlin features a set of four examples with increasing complexity. |
* [http://hackage.haskell.org/package/GPipe-Examples GPipe-Examples package], by Kree Cole-McLaughlin features a set of four examples with increasing complexity. |
||
+ | * Csaba Hruska has made a Quake 3 map viewer using GPipe 1, sources on [https://github.com/csabahruska/GFXDemo GitHub]. |
||
+ | |||
+ | == Sources == |
||
+ | |||
+ | All my GPipe related library sources are available on [http://github.com/tobbebex Github]. If you have something to contribute with, just send me a patch and I might merge it into the trunk. |
||
== Other resources == |
== Other resources == |
||
+ | === GPipe 2 === |
||
⚫ | |||
+ | |||
+ | * [http://hackage.haskell.org/package/GPipe-GLFW GPipe-GLFW] is the first window management package for GPipe 2. |
||
+ | * [http://hackage.haskell.org/package/linear linear] is the vector math package used by GPipe 2. |
||
+ | |||
+ | === GPipe 1 === |
||
+ | |||
⚫ | |||
⚫ | |||
* [http://hackage.haskell.org/package/GPipe-TextureLoad GPipe-TextureLoad package] helps loading textures from disc. |
* [http://hackage.haskell.org/package/GPipe-TextureLoad GPipe-TextureLoad package] helps loading textures from disc. |
||
⚫ | |||
* [http://hackage.haskell.org/package/GPipe-Collada GPipe-Collada package] makes it possible to use Collada files with GPipe. |
* [http://hackage.haskell.org/package/GPipe-Collada GPipe-Collada package] makes it possible to use Collada files with GPipe. |
||
+ | |||
== Questions and feedback == |
== Questions and feedback == |
||
Line 19: | Line 52: | ||
[[Category:3D]] |
[[Category:3D]] |
||
+ | [[Category:Graphics]] |
||
+ | [[Category:Libraries]] |
||
+ | [[Category:Packages]] |
Latest revision as of 15:27, 6 January 2016
What is GPipe?
GPipe is a library for programming the GPU (graphics processing unit). It is an alternative to using OpenGl, and has the advantage that it is functional and statically typed as opposed to OpenGl's inherently imperative style. Another important difference with OpenGl is that with GPipe you don't need to write shaders in a second shader language such as GLSL or Cg, but instead use regular Haskell functions on the GPU data types. GPipe uses the same conceptual model as OpenGl, so if you already know OpenGl, getting up to speed with GPipe is quick!
Version 2
In 2015, a new major version of GPipe was realeased. Read the announcement here on the GPipe blog!
Examples and tutorials
A comprehensive tutorial in five parts is now available for GPipe 2:
- Part 1 - Hello world
- Part 2 - Buffers and arrays
- Part 3 - Shaders and primitive streams
- Part 4 - Textures and samplers
- Part 5 - Drawing
- Quake 3 map viewer using GPipe 2, sources on GitHub.
Use at least version 2.1.3 for the examples in these.
GPipe 1 Examples and tutorials
Note that these only applies to the older deprecated version of GPipe
- Wiki Tutorial that explains the basic principles of GPipe 1.
- GPipe-Examples package, by Kree Cole-McLaughlin features a set of four examples with increasing complexity.
- Csaba Hruska has made a Quake 3 map viewer using GPipe 1, sources on GitHub.
Sources
All my GPipe related library sources are available on Github. If you have something to contribute with, just send me a patch and I might merge it into the trunk.
Other resources
GPipe 2
- GPipe-GLFW is the first window management package for GPipe 2.
- linear is the vector math package used by GPipe 2.
GPipe 1
- GLUT is used in GPipe 1 for window management and the main loop.
- Vec package is the vector math package used by GPipe 1.
- GPipe-TextureLoad package helps loading textures from disc.
- GPipe-Collada package makes it possible to use Collada files with GPipe.
Questions and feedback
If you have any questions or suggestions, feel free to mail me. I'm also interested in seeing some use cases from the community, as complex or trivial they may be.