Innovative Coders

From CDOT Wiki
Revision as of 16:40, 7 November 2012 by Pvaaheeswaran (talk | contribs) (Made milestone 0.2 title link to CIO Framwork))
Jump to: navigation, search


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

Innovative Coders (Team XIV)

Project Marking Percentage

  • due immediately

Group work:      30%        
Individual work: 70% +       
-------------------------
Total           100%

Repository

  • repo Github id: XIV-InvCod

Team Members

Innovative Coders (Team XIV)
First Name Last Name Section Seneca Id Github ID wiki id IRC nick Blog URL
Atieh Mohammadi B amohammadi5 Github:atiehm Atieh Mohammadi AtiehM Journy Using C++
Shawnique Warren B sdwarren1 Github:nique12 Shawnique Donaree Allison Warren nique12 Nique's World
Svetlana Molodtsova B smolodtsova Github:s5molodtsova Svetlana Molodtsova sveta Svetlana Molodtsova
Prasanth Vaaheeswaran A pvaaheeswaran Github:vprasamth Prasanth Vaaheeswaran iampv We're All Forked
Tejaskumar Patel A trpatel8 Github:trpatel8 Tejaskumar Ramanlal Patel trpatel8 Tejas Patel's OOP344 Blog

Issue/Branch Name Format

V.V_Name
example; issue: Add Text Class to the project (issue 2.9.1) issue and branch name on gitub: 2.9.1_AddTextClass

Issues and Status

0.2 Milestone (Due Fri 9th)

  1. Add console class to project and test with cio_test (issue 1)
  2. Create Mock-up classes:
    Create the class files (header and cpp) with blank methods and make sure they compile.
    1. CField Mock-up Class (issue 2.1)
    2. CLabel Mock-up Class (issue 2.2)
    3. CDialog Mock-up Class (issue 2.3)
    4. CLineEdit Mock-up Class (issue 2.4)
    5. CButton Mock-up Class (issue 2.5)
    6. CValEdit Mock-up Class (issue 2.6)
    7. CCheckMark Mock-up Class (issue 2.7)
    8. CText
      1. Add Text Class to the project (issue 2.8.1)
      2. CText Mock-up Class (issue 2.8.2)
    9. CCheckList Mock-up Class (issue 2.9)

0.X Milestone

  • Assigned to: FULLNAME
  • Code review by: FULLNAME
  • Status:
    (being developed/pull request/being reviewed/pushed to master)
  • comments:

Coding Rules

  • Indentation - 2 Spaces, no Tabs! (Change settings in Visual Studio)
  • All safeguards for header files will use the following format: _XX_FILENAME_H_ (XX being your initials to make it unique)
  • Member variables should begin with an underscore (i.e. int _data)
  • Blocks of code will follow the structure outlined below
 if(condition)
 {
    //code here
 }
  • Always use curly brackets (with conditions) even for single line
  • Label the start and finish when there are large blocks of code
  • Briefly comment each function - outlining its purpose

Remember the class standards

  • Declaring each variable separately
  • Correct pointer placement i.e. char* str not char *str

meetings

  • October 19, 2012. Group meeting room 1122. Time: 8.55 a.m. to 10.40 a.m.

Discussed coding rules and standards, grade distribution.

  1. topic and date1
  2. topic and date2

discussions