Hadouken
Revision as of 23:34, 9 November 2012 by Kajanthan Tharmabalan (talk | contribs) (→2.1_CFieldMockups)
OOP344 | Weekly Schedule | Student List | Teams | Project | Student Resources
Contents
Hadouken (Team XI) 20123 - OOP344
Project Marking Percentage
Group work: 50% (25 <= xx <= 50) Individual work: 50% + (50 <= xx <= 75) ------------------------- Total 100%
Repository
- repo Github id: git@github.com:Seneca-OOP344/XI-Hadouk.git
Team Members
First Name | Last Name | Section | Seneca Id | wiki id | IRC nick | GITHUB ID | Blog URL |
---|---|---|---|---|---|---|---|
Kajanthan | Tharmabalan | A | ktharmabalan | Kajanthan Tharmabalan | C0d3z | Kajan- | Research C++ |
Kenneth | Cromarty | A | kscromarty | Kenneth Stewart Cromarty | kscromarty | mrkennc | Kenn C.PGM |
Alex | Lesnikov | A | alesnikov | Alexander Lesnikov | (irc nick) | Dotz303 | (Blog Name) |
Issues and Status
1.0_AddConsoleClass
- Assigned to: Kenneth Cromarty
- Code review by: Andre Mendes
- Status: pull request
- comments: none
2.1_CFieldMockups
- Assigned to: Kajathan Tharmabalan
- Code review by: Kajathan Tharmabalan
- Status: completed
2.2_CLabelMockups
- Assigned to: Kajathan Tharmabalan
- Code review by: Kenneth Stewart Cromarty
- Status: being developed
- comments: none
2.3_CDialogMockups
- Assigned to: Kajathan Tharmabalan
- Code review by: Andre Mendes
- Status: being developed
- comments: none
2.4_CLineEditMockups
- Assigned to: Kenneth Cromarty
- Code review by: Alex Lesnikov
- Status: being developed
- comments: none
2.5_CButtonMockups
- Assigned to: Kenneth Cromarty
- Code review by: Alex Lesnikov
- Status: being developed
- comments: none
Coding Rules
- Curly brackets for code blocks start after the condition and end on an empty line.
if(condition){ // Comment on what it does code code } // state the end of code block
- use 2 spaces to indent
- do not leave any empty lines other than to separate classes
- If variable or class has a measurable value, the units will be added to the end for the var name.
- Variables will be completely in lower case and declared separately on a new line.
- Pointers will have the asterisk near the type when casting and near the variable name when not.
- Classes will begin each words with an uppercase character followed by lowercase characters.
class
- Constants and/or variable defines will be all uppercase separated by underscores
- Types will be casted in lowercase
#define MAX_LENGTH 5
const CAR_TONNES 2
int x;
int* y;
*y = x;
int weightlbs;
Meetings
- latest will be on top