This section lists important differences between IRIS GL and OpenGL and describes the basic steps for porting code from IRIS GL to OpenGL. For a complete list of the differences between IRIS GL and Open GL, see IRIS GL and OpenGL Differences.
Porting IRIS GL programs to OpenGL for Windows NT and Windows 95 requires considerably more work than converting OpenGL programs from the X Window System. While IRIS GL programs are designed to run with specific hardware and software, OpenGL was designed for portability among various systems.
The following table lists some of the key differences between OpenGL and IRIS GL programs.
OpenGL Code | IRIS GL Code |
---|---|
Operating system independent; contains no functions for windowing, event handling, buffer allocation/management, and so on. | Dependent on operating system; windowing-system functions are mixed with rendering functions. There is no windows manager in IRIS GL. |
Uses a standard, common naming convention. OpenGL functions and defined types begin with a "gl" prefix to prevent conflicts with other libraries. | Does not use a common naming convention for functions and defined types. |
Manages state variables (such as color, fog, texture, lighting, and so on) directly and consistently. Does not use tables to load state-variable values. | Uses tables to manage state variables and must bind variables to table values. |
Display lists cannot be edited. | Display lists can be edited. |
Does not provide a file format for fonts. | Provides functions to handle fonts and text strings and a file format for fonts. |
Includes a GL Utility (GLU) library that contains additional functions and routines (such as NURBS and quadratic rendering routines). | Does not support the GLU library. |