Difference between revisions of "OOP344 20131 - iCODE"

From CDOT Wiki
Jump to: navigation, search
(Progress)
(Project Style)
Line 39: Line 39:
 
** date
 
** date
 
** release number
 
** 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
  
  
Line 53: Line 62:
  
  
Example for file comments style:
+
Example for Header comments style:
 
<big><pre>
 
<big><pre>
 
// File Brief
 
// File Brief
Line 59: Line 68:
 
//
 
//
 
// Your First Name & Last Name
 
// Your First Name & Last Name
// Date Created
+
// Date Modified / Submitted
// Release Version
+
// Release Number
  
 
</pre></big>
 
</pre></big>
 +
 +
Example for Release Number Format:
 +
<big><pre>
 +
3.5.0.1
 +
 +
3.5.1.5
 +
 +
3.5.2.1
 +
 +
3.5.3.0
 +
</pre></big>
 +
*3.5 -> 3.5_CButtonImplementation Branch On GitHUB
  
 
==Progress==
 
==Progress==

Revision as of 02:17, 7 March 2013

iCODE Team Page
OOP344 | Weekly Schedule | Student List | Teams | Project | Student Resources

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 Area
Haiyu Qiao iCODE B hqiao3 Haiyu Qiao CallaQ haiyuqiao C++ Island CButton
Chun Chen iCODE B cchen116 Chun Chen Garycc Garycc GaryC's blog ClineEdit
Yue Heng(Brian) Wong iCODE B yhwong6 Yue Heng Wong byhwong yhwong Brian's blog CLabel
Jie Ming(Jay) Feng iCODE B jmfeng1 Jie Ming Feng jayfeng jayfeng Blue Jay C++ CDialog


Project Style

  • 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
  • 3.5 -> 3.5_CButtonImplementation Branch On GitHUB

Progress

  • Milestone 0.2 completed
  • Milestone 0.3
    • Feb 22, 2013
      • CLabel completed, waiting for test file
    • Feb 23, 2013
      • Created test file for CLabel and made changes to CLabel implementation.
    • March 1, 2013
      • Merged the changes to CDialog and cuigh.h to master
      • Merged CLabel to master
    • March 4, 2013
      • 3.5_CButtonImplementation Uploaded, waiting for CDialog & CLabel testing
    • March 6, 2013
      • Milestone 0.3 completed

Resources