Team A - OOP344 20133

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

Team A

Repository

• Repository path: Team A Master Repository

Master Branch Status

Status: OPEN

• Change The Status Before You Merge To Master Repository

  CLOSE: Wait for the Repository to get opened

  OPEN: The Repository is free and mergeable

Team-A Logs

Log Entry For Each Merged To Master

Date	Time	Student's Name	Merged User	IRC Nickname	Description
02/11/2013	7:40 PM	Mohammad-Reza Akbari	makbari11	reza_akbari	Adding the comments and set the correct format to clabel; it's mereged to the Master.
30/10/2013	1:27 PM	Mohammad-Reza Akbari	makbari11	reza_akbari	The prototyping of clabel, cdialog, and clineedit has pushed to it's branch, and merged to the Master.
DD/MM/YYYY	00:00 PM	Full Name	MySenecaEmail	IRC Nickname	Merged Description here

Team Members

Team Name : Team A

First Name	Last Name	Section	Seneca Id	wiki id	IRC nick	Contact Info	Blog URL
Jaemin	Yeo	A	jyeo	Jaemin Yeo	Jaemin	Contact Info	Jaemin's OOP344 Blog
Mohammad-Reza	Akbari	A	makbari11	Mohammad-Reza Akbari	reza_akbari	(647)389-6082	Reza's Blog
Omkar	Parmar	A	onparmar	onparmar	onparmar	Contact Info	C++ OOP Programming
Hamza	Tahir	A	htahir1	Hamza-Tahir	hamzaT-	Contact Info	OOP344 C++

Tasks

Task Name : Release 0.3, Due Date: Monday November 4, 2013 - 23:59

Prototyping

• Task Description : Create a branch from the "Master", add all the Mock-ups (That compiled successfuly), download the 'CField' and Testers implementation files from GitHub. Push the Mock-ups branch to the "Master" branch.
• Programmer Name : Mohammad-Reza Akbari
• Status : Completed
• Github Branch Link : Prototyping Branch

CLabel

• Task Description : Implementing CLabel: A readonly Field that encapsulates console.display() function. CLabel although, by inheritance is Frame, but it is never bordered.
• Programmer Name : Omkar and Jaemin
• Status : Completed
• Github Branch Link : CLabel Branch

CLineEdit

• Task Description : ClineEdit encapsulates the console.edit() function of Console class.
• Programmer Name : Hamza (with a little help from classmate Shehzin Arshad)
• Status : Completed
• Github Branch Link : CLineEdit Branch

CDialog

• Task Description : CDialog Organizes CField objects on the screen, displays them and then lets the user edit them one by one.
• Programmer Name : Jaemin and Mohammad-Reza and Omkar
• Status : Completed
• Github Branch Link : CDialog Branch

Release 0.3 Tester Programs

• Task Description : Run the Tester Programs. It should work the same as Fardad's Demo on Matrix.
• Programmer Name : Jaemin Yeo
• Status : Completed
• Github Branch Link :

Task Name : Release 0.2, Due Date: Sunday Oct 20th, 23:59

Merging To Master Repo

• Task Description : Setting up the development environment and testing CFrame Base class. Jaemin Yeo had compile and run the Test1Frame.cpp with his console program; his branch had been merged to "Master" for the group test. Reza had clone and run the "Master" successfuly.

More Detail Release 0.2 OOP344 To Do

• Programmer Name : Jaemin, Reza...
• Status : The "Master" is passed the Release 0.2 requirements.
• Github Branch Link : Add Console Branch

Project Marking Percentage

Group work: 25% 
Individual work: 75% +
------------------------
Total 100%

Coding Style and Standards

• No Tab Character allowed. Replace the Tabs with 2 spaces on any IDE that you're currently using.
• Each object must have its own type:

int a;
int b;
CDialog D;

• Every statement should be within its own curly brackets (Even it's a one line statement)

for((initilization; condition; increment){
  code block statement(s);
}

if(condition){
  code block statement(s);
}
else{
  code block statement(s);
}

• Commenting Style:

/*-------------------------
| Comment your class |
-------------------------*/

Group Meetings

Release 0.3 Issues

• November 11 2013 @11:25AM
  • The CDialog needs to be debugged.
  • The group members will have flexible due date for their assigned tasks.
  • A couple of GitHub thingys that will be done for next release:
    • Each class will have an Issue assigned to a member
    • Each class will have a Milestone for it's completion date.
    • The class won't be merged to Master unless it's completed and compilable.
  • The classes should be prioritize for it's due date and testing process.

date