Core OpenGL: Difference between revisions

Content deleted Content added
m try to sort sentences a bit
Line 1:
'''Core OpenGL''', or '''CGL''', is [[Apple Computer]]'s Macintosh Quartz windowing system interface to the [[Mac OS X]] implementation of the [[OpenGL]] specification. CGL is analogous to [[GLX]], which is the [[X11]] interface to OpenGL as well as WGL, which is the [[Microsoft Windows]] interface to OpenGL.
 
On OS X, CGL is the foundation layer of windowing system interfaces to OpenGL. Both AGL (Apple OpenGL) and the [[Cocoa (API)]] (or AppKit) have interfaces to OpenGL and are logical software layers and depend on CGL for their behavior. CGL and AGL interoperate freely. CGL and Cocoa may be used together, however Cocoa classes may implicitly make changes to CGL state. Function calls from AGL and Cocoa should not be mixed.
 
==History==
All windowing system interfaces to OpenGL arose out of the migration of [[Silicon Graphics]] proprietary 3D graphics application programming interface ([[API]]) IrisGL to its current open standard form OpenGL. When the decision was made to make IrisGL an open standard, the primary required design change was to make this graphics standard API windowing system agnostic. All window system specific logic was therefore removed from IrisGL when moving to OpenGL. Window system logic includes any event mechanism for gathering input from devices such as keyboards and mice, as well as any window ordering or sizing logic used when drawing to a modern windowed user interface. Further, all internal management of window memory buffers, sometimes referred to as surfaces, was also removed from IrisGL to create OpenGL.
 
With OpenGL windowing system agnostic, companies such as Apple must shoulder the burden of configuring and managing the surfaces used as a destination for OpenGL rendering.

==Features
On OS X, CGL is the foundation layer of windowing system interfaces to OpenGL. Both AGL (Apple OpenGL) and the [[Cocoa (API)]] (or AppKit) have interfaces to OpenGL and are logical software layers and depend on CGL for their behavior. CGL and AGL interoperate freely. CGL and Cocoa may be used together, however Cocoa classes may implicitly make changes to CGL state. Function calls from AGL and Cocoa should not be mixed.

Configuration of these surfaces is done through a pixel format selection process where different compatible layers of rendering information are combined to form a framebuffer. Examples of such layers are color buffers, transparency buffers (alpha), stencil buffers, and depth buffers. The CGL function CGLChoosePixelFormat is used to perform this buffer compatibility check. CGLChoosePixelFormat will, based on input parameters and their scoring policy, choose a pixel format that represents a compatible buffer configuration that is supported by the underlying renderer that will be used to process graphics commands. Renderers may be either hardware based, such that they correspond to graphics cards installed in the system or they may be software based, where the main CPU of the system handles all of the graphics command processing and final rasterization work.
 
On Mac OS X, CGL is also responsible for handling the heterogeneous nature of graphics device installations and configuration on Macintosh systems. Macintosh computers may have any number of displays and graphics cards installed in them. In these configurations, the users desktop may be virtualized (extended) or mirrored across multiple displays which are connected to multiple graphics cards which may or may not be from the same graphics vendor.