Thread: my second coming

hi there i would like to ask for some advice i have recently started to make games again. i made one game before using sdl which was ok but never finished and polished.

the game i made i didnt really use classes and as a novice c++ programmer i fell the coding of the game was the easy part.

ok my question is how do you start designing a game i mean how do you decide the classes to use and which functions will belong to which class.
ok that might sound easy but i normally position things on screen manually and work out my collisions manually which is ok until i need to change the window size so either a little advice or maybe a link about the design of a game would be much appreciated.

thanks in advance

edit: ok maybe using a tetris clone as an example? what classes would you use im fairly sure once i got the idea of classes i could code them together its just the picking choosing of classes that gets me. how do you decide which classes are needed. thanks again

Deciding classes and such are never easy and there's never a must-do example.
But the general idea is to consider classes as objects, so in a tetris game, a class of the falling parts, one base class for them and from them derived classes for each type of part since they have different properties. If anything, their dimensions would be specified in a derived class.
One class for the actual room where the blocks fall. It must contain a vector with all the parts inside. It will also probably be the one that's responsible for seeing if there are any full lines are for collision detection. Each part class will probably keep track of its own coordinates in the room.

There's more, to be sure, but just off-hand, I cannot say. It will come to you when you start designing the whole thing. You just need to know what tools are available to you and think logically how they might fit into a solution for your design problem.

There's going to be polymorphism and virtual functions too (due to the base class).
Other might give you a different answer. It's up to the designer, really. A good implementation is one that will require you to do little code in sense of checking this and that, one might say. Or I don't really know how to explain it.

In any case, you really have to try and pan it out yourself. There are no definite rules for layout.

I'd stick with whatever was simpler to begin with, if you already have a bit of SDL experience I'd suggest sticking with it. I tried to dive into OpenGL but got overwhelmed with it, I was trying to create a far too advanced rendering system for my knowledge.

Now I'm working on a text blackjack game and learning is coming much easier.

I haven't used SDL at all, so no ideas there.

Stay with SDL because you can use openGL if you want. Personally I find SDL gets in the way too much (my opinion), so I use glfw instead.