iCODE

Contacts

EMAIL TEAM MEMBER
number of team members: 4

OOP344 - iCODE Team Member list (Winter of 2013)
First Name	Last Name	Team Name	Section	Seneca Id	wiki id	IRC nick	GITHUB ID	Blog URL	R0.2 Area	R0.4 Area
Haiyu	Qiao	iCODE	B	hqiao3	Haiyu Qiao	CallaQ	haiyuqiao	C++ Island	CButton	CText
Chun	Chen	iCODE	B	cchen116	Chun Chen	Garycc	Garycc	GaryC's blog	ClineEdit	CValEdit, CCheckList
Yue Heng(Brian)	Wong	iCODE	B	yhwong6	Yue Heng Wong	byhwong	yhwong	Brian's blog	CLabel	CCheckMark
Jie Ming(Jay)	Feng	iCODE	B	jmfeng1	Jie Ming Feng	jayfeng	jayfeng	Blue Jay C++	CDialog	CMenuItem

Indentations are to be in spaces of 4
Blocks are to be coded as follows:
- the beginning bracket must go with the statement
- the ending bracket is standalone
Variables and class names are to be in camel case. Variable names should beign with a lowercase letter and class names should begin with an uppercase letter.
Header comments must have the following and in the listed order:
- description of program
- file name
- author
- date
- release number
Release Number Format:
- x.x.x.x
- First and Second number is your Branch Number
- Third position:
  - 0 for alpha (status)
  - 1 for beta (status)
  - 2 for release candidate
  - 3 for (final) release
- Fourth position: bug fixes

Example for code blocks style:

if(data){
    ...
}
else{
    ...
}

Example for Header comments style:

// File Brief
// File Name
//
// Your First Name & Last Name
// Date Modified / Submitted
// Release Number

Example for Release Number Format:

3.5.0.1

3.5.1.5

3.5.2.1

3.5.3.0