BattleSignal Code
Status: Planning
Brought to you by:
nmond002
File | Date | Author | Commit |
---|---|---|---|
gl | 2008-07-29 | nmond002 | [r15] Adding OpenGLUT folder |
BattleSignal.dev | 2008-07-10 | nmond002 | [r12] New OpenGL version of BattleSignal |
Makefile.win | 2008-07-10 | nmond002 | [r12] New OpenGL version of BattleSignal |
README.txt | 2008-07-10 | nmond002 | [r12] New OpenGL version of BattleSignal |
display.h | 2008-08-04 | nmond002 | [r17] Report Updates |
fof.h | 2008-08-04 | nmond002 | [r17] Report Updates |
main.cpp | 2008-08-04 | nmond002 | [r17] Report Updates |
track.h | 2008-08-04 | nmond002 | [r17] Report Updates |
/******************************************************************************* Project: BattleSim By: Neil Monday, Tony Luong, Dwight Swain, Steve Simmons, Lowell Knight, Scott Wood, *******************************************************************************/ Please follow these guidelines and it will make everyone's life a lot easier. I know everyone codes in their own way, but I think everyone will benefit from having a few rules for the way you should code for this project. 1. All function names should be be descriptive of what the function does. If a function sets a location of a track then the function should be called something like "set_location()". Also, all functions should be lower case, and different words in a function name should be separated by underscores "_". Good: "load_torpedoes()" Bad: "loadTorpedoes()" Bad: "ldTpds()" etc. 2. Make sure all of a class's functions are EXACTLY like they are on the UML cards. This is VERY IMPORTANT so that people accessing a class's function will know exactly what to expect and how to spell it. Feel free to add to this document and then commit the changes to the server if you have any other rules you would like to add.