At the moment, the engine source code is split into four directories: engine/src, engine/inc, standard/src, standard/inc. There is not much, if any, logic left in that organisation. The main difference is that C++ classes in the latter half tend to have "Std" in their name, despite not being standard in any way. Most of the plattform abstraction code and some helper functions are in the second half, and most dependencies are only from "engine" to "standard", so it helps a little with maintenance. But other plattform abstractions and important helper functions are in engine. And engine is getting too big.

Has anybody a suggestion on a new prefix for classnames? Std is just stupid. (And no namespaces, please, they just make grepping harder.)

I think we need to further split the code. I can think of these categories: plattform abstraction, helper/library functions, GUI code, network, game logic, and scripting. To make these categories useful, a category should not depend on categories which depend on the category. This means that there is a limit to splitting, my list is probably already too long.

And do we still need those "inc" and "src" directories? They are useful if being in "inc" means that third party code will have access to the files, but we are not writing a library here, and having the header and corresponding source code right next to each other is more convenient.