Not What You Meant? There are 35 definitions for Toolkit. Also try: Glut.

OpenGL Utility Toolkit

About 2 pages (652 words)

Know this topic well? Help others and get FREE products!

The OpenGL Utility Toolkit (GLUT) is a library of utilities for OpenGL programs, which primarily perform system-level I/O with the host operating system. Functions performed include window definition, window control, and monitoring of keyboard and mouse input. Routines for drawing a number of geometric primitives (both in solid and wireframe mode) are also provided, including cubes, spheres, and the Utah teapot. GLUT even has some limited support for creating pop-up menus. GLUT was written by Mark J. Kilgard, author of OpenGL Programming for the X Window System and The Cg Tutorial: The Definitive Guide to Programmable Real-Time Graphics, while he was working for Silicon Graphics Inc. The two aims of GLUT are to allow the creation of rather portable code between operating systems (GLUT is cross-platform) and to make learning OpenGL easier. Getting started with OpenGL programming while using GLUT often takes only a few lines of code and does not require knowledge of operating system–specific windowing APIs. All GLUT functions start with the glut prefix (for example, glutPostRedisplay marks the current window as needing to be redrawn).

1 Implementations
2 Limitations
3 See also
4 External links

Implementations

The original GLUT library by Mark Kilgard supports the X Window System (GLX) and was ported to Microsoft Windows (WGL) by Nate Robins. Additionally, Mac OS X ships with a GLUT framework that supports its own CGL. Kilgard's GLUT library is no longer maintained, and its license did not permit the redistribution of modified versions of the library. This spurred the need for free software reimplementations of the API from scratch. The first such library was freeglut, which aims to be a fairly exact clone, though introducing a small number of new functions to deal with GLUT's limitations. OpenGLUT, itself a fork of freeglut, adds a number of new features to the original API.

Limitations

Some of GLUT's original design decisions made it hard for programmers to perform desired tasks. This led many to create non-canon patches and extensions to GLUT.[1] Some free software reimplementations also include fixes. Some of the more notable limitations of the original GLUT library include:

The library requires programmers to call glutMainLoop(), a function which never returns. This makes it hard for programmers to integrate GLUT into a program or library which wishes to have control of its own event loop. A common patch to fix this is to introduce a new function, often called glutCheckLoop(), which runs only a single iteration of the GLUT event loop. Another common workaround is to run GLUT's event loop in a separate thread, although this may vary by operating system, and also may introduce synchronization issues or other problems: for example, the Mac OS X GLUT implementation requires that glutMainLoop() be run in the main thread.
The fact that glutMainLoop() never returns also means that a GLUT program cannot exit the event loop. freeglut fixes this by introducing a new function, glutLeaveMainLoop().
The library terminates the process when the window is closed; for some applications this may not be desired. Thus, many implementations include an extra callback, such as glutWMCloseFunc().

Since it is no longer maintained, the above design issues are still not resolved in the original GLUT. In a web page description of the glutMainLoop() problem, one programmer claimed that Kilgard was opposed to integrating fixes.[2]