Gloss hides the pain of drawing simple vector graphics behind a nice data type and a few display functions. Gloss uses OpenGL and GLUT under the hood, but you won't have to worry about any of that. Get something cool on the screen in under 10 minutes.

Gloss is a fork and cleanup of ANUPlot, which was used for teaching first year computer science at the ANU some time ago. Its main goal is to allow total beginners to get something working with a minimum of fuss.


These are some of the examples included in the gloss-examples package:

Hello Lifespan Styrene Tree Clock Zen
code result code result code result code result code result code video


From Hackage

With cabal

If you have cabal installed you should be able to:

cabal update
cabal install gloss-examples

From the source repo

The source repo is on github:

git clone
cd gloss/gloss
cabal install

Then again for the gloss-raster and gloss-examples packages in that same repo.

Further Information

To report bugs or request features, post in the haskell-gloss Google group.

We're also interested in cool examples you come up with. Contributed examples can be added to the gloss-examples package and posted on this page.

To get an account on the trac, send email to gloss [wibble]

Active Related Projects

Frequently Asked Questions (FAQ)

Q: Gloss freezes in ghci. It tries to draw the window but I don't get a picture and must kill the process.
A0: Start ghci with -fno-ghci-sandbox. This is because OpenGL uses thread local state, which doesn't work when the running program is in a different thread.
A1: Try installing gloss to use the GLFW window manager interface instead of GLUT: cabal install gloss --flags="GLFW -GLUT"

Q: I tried to draw a polygon shaped like a star, but it looks wrong.
A: Gloss does not support non-convex polygons. You'll need to break up your picture into several separate convex polygons (eg, triangles). Gloss calls OpenGL directly to draw polygons, and the API doesn't handle non-convex ones. To fix this we'll need to write a triangulation function (#11).

Q: I'm getting an "internal stack overflow" or "internal stack underflow" error from OpenGL when running a program that draws a picture recursively.
A: Your GPU hardware has a fixed sized transform matrix stack. Each time you use a more deeply nested 'rotate' 'translate' or 'scale' transform then a matrix is pushed on this stack. When the stack is full you should get an overflow error and the OpenGL library should kill the process. If your OpenGL library was poorly implemented then matrices pushed onto a full stack will be silently discarded, and then when Gloss tries to pop the full number this will cause an underflow.

The OpenGL specification requires implementations to support at least 32 entries on the transform stack, so you should be able to apply this many nested 'rotate' 'translate' and 'scale' transforms to your picture. If this isn't enough then you can probably refactor your program so it doesn't use so many nested transforms.

This problem with a fixed size transform stack is discussed further in Section 4 of Avoiding common OpenGL pitfalls. Gloss tries not to use the stack when it doesn't have to, but we don't know of any way to spill the stack to main memory to allow more entries. If you know how to solve this problem without giving up on hardware acceleration and doing the transforms in software, then please let us know on the mailing list.

Q: Animations seem jerky.
A: Make sure you're compiling with -O2 -threaded. Without the threaded runtime, the code that manages the frame rate will behave badly. This is because GHC takes too long to reschedule the gloss process after the sleep timer has expired. With the threaded runtime, most simple animations should run at about 100fps, which is our internal frame-rate cap.

Q: On my MacBook Pro under OSX, gloss programs freeze after displaying the first few frames.
A: This can happen on dual GPU systems when the OS switches from the integrated GPU (baked into the processor) to the discrete one (separate from the main processor). The gloss program can sometimes draw a few frames before getting stuck, otherwise it just shows a black window. This is probably a bug in OSX not switching the graphics context properly. The work-around is to disable automatic GPU switching under System Preferences / Energy Saver.

Q: On Windows, when I try to run a gloss program it says user error (unknown GLUT entry glutInit).
A1: You need to install glut32.dll. Copy it into \Windows\System32 (for 32-bit installs) or \Windows\SysWOW64 (for 64-bit installs). Alternatively, you can just copy it into the same directory as the Main.exe executable you are trying to run.

Q: On Windows, how do I turn off the console window when the Gloss program runs?
A: Pass GHC the flag -optl-mwindows when compiling the program. At runtime, if your program tries to write to stdout or stderr then Windows will kill the process.

Q: With Xmonad, the Gloss window doesn't resize properly.
A: Use the GLFW window manager interface instead, or prod the Xmonad people about it. This is probably an incompatibility between Xmonad and GLUT, but the main Gloss developer doesn't use Xmonad.

Last modified 6 years ago Last modified on Mar 24, 2018, 3:49:59 PM

Attachments (6)

Download all attachments as: .zip