Difference between revisions of "Team Q - OOP344 20133"
Brad Clement (talk | contribs) (→Coding Style and Standards) |
Brad Clement (talk | contribs) (→Coding Style and Standards) |
||
Line 23: | Line 23: | ||
* Tab's are allowed in the code | * Tab's are allowed in the code | ||
− | * Each object must have its own type to make it as clear as possible | + | * Each object and variable must have its own type to make it as clear as possible |
<big><syntaxhighlight lang="cpp"> | <big><syntaxhighlight lang="cpp"> | ||
int a; | int a; | ||
Line 45: | Line 45: | ||
} | } | ||
</syntaxhighlight></big> | </syntaxhighlight></big> | ||
+ | |||
+ | * File Heading Comments | ||
+ | |||
+ | <big><syntaxhighlight lang="cpp"> | ||
+ | /* | ||
+ | filename.cpp (or .h) OOP344x (x for Section) | ||
+ | Version Number: Version 1,2,3,4 etc | ||
+ | Description: Small description of the purpose | ||
+ | Name: Firstname Lastname | ||
+ | Student Id - 123-456-789 | ||
+ | Date Modified: Month, Day, Year | ||
+ | */ | ||
+ | </syntaxhighlight></big> | ||
+ | |||
+ | Comments in Code | ||
+ | |||
+ | * placed above each function, gives a short description of purpose | ||
+ | * comment any large blocks or complex code to the right of your code | ||
+ | For Example | ||
+ | <big><syntaxhighlight lang="cpp"> | ||
+ | |||
+ | if (blahblah = 50) | ||
+ | { | ||
+ | do1; // will perform this | ||
+ | do2; // will perform that | ||
+ | do3; // will perform whatever | ||
+ | } | ||
== Team Members == | == Team Members == |
Revision as of 10:50, 20 October 2013
Contents
Team Name
TEAM Q
Project Marking Percentage
- due right after study break
Group work: 50% (25 <= xx <= 50) Individual work: 50% + (50 <= xx <= 75) ------------------------- Total 100%
Repository
- repo path: https://github.com/Seneca-OOP344/Team-Q.git
Master Branch Status
Status
- Open/Closed
- Open: you can merge now.
- Closed: Wait for the repo to get opened
Logs
- DateTime, Merged/being Merged by full name, ircnick: mynick, any other info
Coding Style and Standards
- Tab's are allowed in the code
- Each object and variable must have its own type to make it as clear as possible
int a;
int b;
CDialog D;
- Formatting of condition blocks
if (condition)
{
doStuff;
}
else
{
doOtherStuff;
}
for (x=0;x<5;x++)
{
loopStuff;
}
- File Heading Comments
/*
filename.cpp (or .h) OOP344x (x for Section)
Version Number: Version 1,2,3,4 etc
Description: Small description of the purpose
Name: Firstname Lastname
Student Id - 123-456-789
Date Modified: Month, Day, Year
*/
Comments in Code
- placed above each function, gives a short description of purpose
- comment any large blocks or complex code to the right of your code
For Example <syntaxhighlight lang="cpp">
if (blahblah = 50) {
do1; // will perform this do2; // will perform that do3; // will perform whatever
}
Team Members
First Name | Last Name | Section | Seneca Id | wiki id | IRC nick | Blog URL |
---|---|---|---|---|---|---|
Alvaro | Lemus | C | alemus4@myseneca.ca | alemus4 | alemus4 | blog address Blogname |
Brad | Clement | C | bclement1@myseneca.ca | Brad Clement | bradc14 | Brad's Blog |
Gyeongmin | Jung | A | gjung1@myseneca.ca | Gyeongmin Jung | gjung1 | Hello World! |
Dave | Dooney | C | ddooney@myseneca.ca | David Dooney | bakoomerang | Dave's Blog |
tasks
task name
- task description
- being done by team member name / not assigned
- status
meetings
- latest will be on top