Would the tutorial be any use to me as a SDL user , as a idea on how to design classes for a game/project ?
I get the idea of encapsulation, and protecting data that 'some potential user' may alter in an unwanted manner... its just I keep smacking into ' I cant do this here because this class doesnt know about that information, but that class doesnt know about this pointer, and the main class needs the pointer to acces another class altother ' walls.
A lot of the time I end up with a load of get x and set x mini functions to do the stupidest things.
I have gone through sdltutorials.com framework tutorial and picked up a lot of ideas, but even that has me wondering... like why declare the main display in the CApp , there is a CSurface class why not leave the surface work to the surface class itself ?
To a certain degree, yeah.
The first two parts would be completely useless, as they are all about configuration. Your game loop would have to be rewritten, and obviously you would have to swap SFML for SDL calls, but that would be about it. The fundamentals and such would all still apply, so if you have a good understanding of SDL, you should be able to translate it pretty easily.