A+ Programmers - OOP344 20113

From CDOT Wiki
Revision as of 20:44, 19 October 2011 by Hchobanlou (talk | contribs) (Tasks)
Jump to: navigation, search


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

A+ Programmers

Project Marking Percentage

  • due right after study break

Group work:      XX%        (25 <= xx <= 50)
Individual work: XX% +      (50 <= xx <= 75) 
-------------------------
Total           100%

Repository

  • repo id:

Trunk Status

  • committed/committing by
    id: emailid
    name: full name
    irc nick: mynick
    any other info


Team Members

A+ Programmers
First Name Last Name Section Seneca Id wiki id IRC nick Blog URL
Ronson Wan A rwan1 rwan1 Ronsonnn Ronson's Blog
Ramone Burrell B raburrell raburrell burrellramone Ramone's Blog
Hesam Chobanlou B hchobanlou hchobanlou hchobanlou Triggaz Blog
Mike Shutov B mshutov mshutov mshutov Mike's Blog
Akash Patel B acpatel4 acpatel4 Akash123 Akash Patel's Blog

tasks

CField

  • task description
  • being done by team member name / not assigned
  • status

CLabel

  • task description
  • being done by team member name / not assigned
  • status

CDialog

  • task description
  • being done by team member name / not assigned
  • status

CLineEdit

  • task description
  • being done by team member name / not assigned
  • status

CButton

  • task description
  • being done by team member name / not assigned
  • status

Syntax Guidelines

This is a group of recommendation of coding style pertinent to this group. Feel free to add or modify where you see fit.

Comments:

  • Comments should explain the purpose behind statements not logic.
  • Explain each parameters role to the function.
  • State the return value of the function.

Example:

/*
* Pourpose: A short description of the function.
*
* Parameters: int x -> Describe what use the function makes of the variable.
*
* Return: int, bool etc...
*/

void foo(int x) {
 return x;
}

meetings

  • latest will be on top

topic, date

date