Open main menu

CDOT Wiki β

Team Q - OOP344 20133

Revision as of 10:19, 13 November 2013 by Brad Clement (talk | contribs) (Coding Style and Standards)

== TEAM Qt ==

Project Marking Percentage

  • due right after study break

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

Repository

Master Branch Status

Status

  • Open/Closed
  • Closed: Wait for the repo to get opened
    PLEASE PULL FROM THE REPO

Coding Style and Standards

  • Tab's are allowed in the code however when using Visual Studio we must change the TAB setting ( Please set your tab size to 3 and also your indent size to 3 and have it insert spaces, instead of TAB)
  • Each object and variable must have its own type to make it as clear as possible
int a;
int b;
CDialog D;
  • Pointer *
Is Accepted int* number;
Not Accepted int *number;
  • Header Files and Class/Struct Formatting
#ifndef __TEAMQ_FILENAME_H__ // Safeguard
#define __TEAMQ_FILENAME_H__


class example
{
private:
   int var1;
   int* var2;
public:
   void display();
};

void example::display()
{
   a=var1+var2;
}

#endif


  • Formatting of condition blocks
if (condition)
{
     doStuff;
}
else
{
     doOtherStuff;
}

for (x=0;x<5;x++)
{
     loopStuff;
}
  • File Heading Comments
/********************************************
Filename: filename.cpp (or .h)
Description: Small description of the purpose
Section: OOP344x (x for Section)
Name: Firstname Lastname
Student Id: 123-456-789
Date Last Modified: Month, Day, Year
********************************************/

Comments in Code

  • placed above each function, gives a short description of purpose
  • comment any large blocks or complex code above your code

For Example

if (blahblah = 50)
{
     // will perform this
     do1;
     // will perform that
     do2;
     // will perform whatever 
     do3;     
}

Team Members

Team Qt
First Name Last Name Section Seneca Id wiki id IRC nick Blog URL
Alvaro Lemus C alemus4@myseneca.ca Alvaro Lemus alemus4 Kyno's Blog
Brad Clement C bclement1@myseneca.ca Brad Clement bradc14 Brad's Blog
Gyeongmin Jung A gjung1@myseneca.ca Gyeongmin Jung gjung1 Hello World!
Dave Dooney C ddooney@myseneca.ca David Dooney bakoomerang Dave's Blog

tasks

Release 0.4 Release Date TBA

  1. CButton
    • Member: Brad Clement
    • Task: Code cbutton.h and cbutton.cpp
    • Status: In Progress

  2. CValEdit
    • Member:
    • Task: Code cvaledit.h and cvaledit.cpp
    • Status: In Progress

  3. CCheckMark
    • Member:
    • Task: Code ccheckmark.h and ccheckmark.cpp
    • Status: In Progress

  4. CMenuItem
    • Member: Alvaro Lemus
    • Task: Code cmenuitem.h and cmenuitem.cpp
    • Status: In Progress

Release 0.3 Monday Nov 4th, 23:59

  1. Prototyping Workload-16%
    • Member: Alvaro Lemus
    • Task: Create prototypes and empty definitions for all classes
    • Status: Complete

  2. CLabel Workload-17%
    • Member: Alvaro Lemus
    • Task: Code CLabel.h and CLabel.cpp
    • Status: Complete

  3. CDialog Workload-50%
    • Member: Brad Clement / David Dooney
    • Task: Code CDialog.h and CDialog.cpp
    • Status: Complete

  4. CLineEdit Workload-17%
    • Member:Gyeongmin Jung
    • Task: Code CLineEdit.h and CLineEdit.cpp
    • Status: Complete

Release 0.2 Due Date October 20th, 23:59

  • Organize and complete team page - Always in Progress
  • Select a team member's console.cpp and console.h to use - Complete - Used David Dooney's Files
  • That team member should branch and clone the repository, add console.cpp and console.h to the files in the repository, compile, run and test the execution. When done this team member should add her/his name, github id and the date and time of the completion (as a comment) to cframe.h and merge the branch back to the master repo and push the changes up to github.
  • All other members clone the repository, comment, and test the execution of CFrame
  1. Branch the master for review with a proper name
  2. Complete
  3. Compile, run and test the execution
  4. Complete
  5. Add a comment with your, github id and date and time to the top of cframe.h header file
  6. Complete
  7. Merge the branch back into the master branch
  8. Complete
  9. Push the changes to github
  10. Complete

Meetings

November 4th - Met in 1131 Study Room to finish completing release 0.3

November 2nd and 3rd - Spoke on Skype to work through and fix issues

November 1st 9:50 AM up to 4:30pm - Reserved room at Library Studies 1131. Working on Release 0.3

October 21st 11:00 AM - talked over dividing of tasks for Release 0.3

October 20th 4:30 PM - completed details for coding styles and requirements

October 17th 5:00 PM - initial setup of team page and deciding requirements

  • latest will be on top