Thread: OOOP Where to start?

Depends how you want to do it. Two common ways are to have the room object draw itself or to have another viewer object draw the room model(similar to model-view-controller or MFC's document-view). So, for example, you could have an interface like this:

Code:

class Room {
public:
      // ... //
       
      void draw( // ... // )
private:
      // vertex data
} ;

The style used here would be for the room object to draw itself. On the other hand, having the room model notify a viewer object when it has changed could look like this

Code:

class RoomModel {
      void addChangeListener(ChangeListener l);
      void removeChangeListener(ChangeListener l);
public:
     // vertex data
};

class RomeViewer : public ChangeListener {
public:
        virtual void stateChanged(ChangeEvent e);
};

In the techneque above, when the RomeModel changes, the RoomViewer is notified, by stateChanged. The RoomViewer will then attempt to draw itself on the screen or update some type of display infomation.

What technique you use depends on the circumstance. I don't know too much about OpenGL, but the first technque, I think, is usually the best if all the rendering is done all at once. The second technique might be good for a GUI application, whereby the screen is rendered only when a display object has changed.

You understand the first example, right?

For the second example, the methods to add and remove the model listeners should be public, and the data should private. When the model changes, the code, if completed, should tell its listeners, the viewers, that its data has been modified. The listeners are then able to react to this change in data by drawing themselves. But this technique isn't too useful for opengl; you're drawing the objects that are visible, rather than the objects that have changed.

// is a C++ style comment
it comments out the rest of the line

The code I gave you was never meant to be compilable, but you could replace with /* */. I used that notation just to mean that you'd probably have to send in a graphic device context of some sort, I think OpenGL hides this within the library.

but I am just stupid, dull

Well, you have to give yourself some time to learn C++.

Go to NeHe Downloads and download the resources - nehe_sdk.zip. Within this zip file lays the best OpenGL scene creator. All you have to do to create your scene is to put your code in between this one function in this one class, start with the first example, rip out the stuff you don't need, compile, edit, compile, edit, repeat 200 times, and you're an OpenGL wizard ;)

Repeat 20000 more times, and you'll be working for a really good game designing company! lol

I'm not sure they'll allow you to use a third API in a course.

Since the API is written by people who have a great deal of experience in C++, looking at them will probably only serve to confuse you more.