A+ Programmers - OOP344 20113

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

• complete all functions for this class
• Ramone Burrell
• Done

CLabel

• complete all methods for this class
• Ronson Wan
• Completed

CDialog

• Constructor
• Hesam Chobanlou
• Completed

• Working on draw method.
• Akash Patel
• Completed

• Working on operator<<(CField& field)
• Ronson Wan
• Completed

• Working on int add(CField* field, bool dynamic = true)
• Ramone Burrell
• Completed

• Working on int add(CField& field, bool dynamic = false)
• Ramone Burrell
• Completed

• Working on destructor for cdialog class
• Ramone Burrell
• Completed

• Working on edit method for cdialog class
• Ronson Wan
• Completed

• Dummy File(Prototype of all functions)
• Mike Shutov
• Completed

• General Function maintenance and some work on many of the functions.
• CField& CDialog::operator[] and CField& CDialog::curField(){ and int CDialog::curIndex() + other queries
• Mike Shutov
• Completed

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 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