Difference between revisions of "Hadouken"

From CDOT Wiki
Jump to: navigation, search
(Project Marking Percentage)
(2.1_CFieldMockups)
Line 44: Line 44:
 
=== 2.1_CFieldMockups ===
 
=== 2.1_CFieldMockups ===
 
* Assigned to: [mailto:ktharmabalan@myseneca.ca Kajathan Tharmabalan]
 
* Assigned to: [mailto:ktharmabalan@myseneca.ca Kajathan Tharmabalan]
* Code review by: [mailto:kscromarty@myseneca.ca Kenneth Stewart Cromarty]
+
* Code review by: [mailto:ktharmabalan@myseneca.ca Kajathan Tharmabalan]
* Status: being developed
+
* Status: completed
* comments: none
 
  
 
=== 2.2_CLabelMockups ===
 
=== 2.2_CLabelMockups ===

Revision as of 00:34, 10 November 2012


OOP344 | Weekly Schedule | Student List | Teams | Project | Student Resources

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

OOP344 - Team Hadouken
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

2.1_CFieldMockups

2.2_CLabelMockups

2.3_CDialogMockups

2.4_CLineEditMockups

2.5_CButtonMockups

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
  1. IRC meeting logs

Discussions