First, we need to decide on a set of coding style guidelines.
I would suggest something like the google ones: https://google-styleguide.googlecode.com/svn/trunk/cppguide.xml
or the ones used by DungeonHack: http://dungeonhack.sourceforge.net/Code_Style_Guidelines
We should work on having consistency in the code. Some of the work could probably be done using a refactoring tool.
Some specific things I suggest we should work on:
- Try to avoid "using" statements in headers. (And preferably in source files as well unless it provides more clarity) (I know andrew has been removing some while developing)
- Use the ogre logging function rather than using cout for all text output. Things printed on Stdout is not easily accessible in windows.
- Make some sort of graceful exit and handle errors better when something fails to load. This will make it easier for people to see what's wrong if the game crashes.
- Try to only include other headers in headers if it's strictly needed and can't be sorted with a forward declaration. This should speed up building.
There are probably some more things i have forgotten to mention.