iDevGames Forums
A toolkit for OpenGL - Printable Version

+- iDevGames Forums (
+-- Forum: Development Zone (/forum-3.html)
+--- Forum: Graphics & Audio Programming (/forum-9.html)
+--- Thread: A toolkit for OpenGL (/thread-6884.html)

A toolkit for OpenGL - whogben - Jul 28, 2003 09:16 AM

do you guys program straight openGL or do you have other APIs and toolkits that are higher level to work with. I just started with openGL (up to NeHe tutorial 8) and I am finding it to be a tad low level for me, I'm more interested in rapid-construction than painstaking vertex positioning etc, what do you all use, or do you take your openGl straight?

A toolkit for OpenGL - skyhawk - Jul 28, 2003 09:46 AM

straight opengl... but all my programs eventually build up more complicated primitives like sprites and such Grin

A toolkit for OpenGL - Mark Levin - Jul 28, 2003 09:49 AM

There's GLU, which mostly provides complex but common calculations (setting up projections, curved surfaces) but is still pretty low-level, and GLUT, which can provide an entire GL application (using your graphics code alone) but can only automatically create shapes like spheres, cylinders, and teapots.

3D is complicated, and you usually have to get down to the low level to get exactly what you want to happen. That's why it's so powerful and so fast (the operations are made as simple and streamlined as possible). Unless you want to get into licensing commercial engine components.

A toolkit for OpenGL - Josh - Jul 28, 2003 10:08 AM

If all you are doing is 2D then I would heartily recommend CocoaBlitz.

A toolkit for OpenGL - kelvin - Jul 29, 2003 01:09 AM

I'll have demos and a better build of CB ready by Aug 4, I swear!

A toolkit for OpenGL - whogben - Aug 1, 2003 10:24 AM

whats CB? cocoa blitz?

A toolkit for OpenGL - Josh - Aug 1, 2003 11:38 AM

Yep, CB == CocoaBlitz.

A toolkit for OpenGL - Feanor - Aug 3, 2003 10:16 AM

If/when Quesa becomes sufficiently speedy to be useable, I still want to try integrating that in my work. The other thing I'm waiting on is 3DKit, but that seems to be dead again.

I used to think I wanted an engine, but after looking at dozens of game engines (mostly in C++), I think you have hit the nail on the head -- what everybody really wants is a toolkit. Just a set of useful classes that would do all the things that everybody always has to do the first time that they start a game, which take a long time and tend to make you get bored with the work very early. It's like you were writing a book but had to build your own word processor or make your own paper from wood pulp.

I certainly don't want a "book-writing engine" or anything -- I'm happy with the pre-existence of language, culture, and some useful tools for putting sentences together. Why not the same for game development?

Does it annoy anyone else that there is not even a standard for how to define and name a vector ADT? Every engine/kit I've looked at does it differently. It's like everybody speaks the same languages, but they all use different technical dialects. Software development is still in its infancy, I guess.