Open main menu

CDOT Wiki β

GP

Revision as of 22:12, 13 November 2012 by Youngjae Kim (talk | contribs) (Coding Rules)

Team Name (team GP)

Project Marking Percentage

  • due immediately

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

Repository

Team Members

Team Name (team GP)
First Name Last Name Section Seneca Id Github ID wiki id IRC nick Blog URL
Hiroshi Takemoto A htakemoto htakemoto Hiroshi Takemoto rostato Magic Logic Program
Youngjae Kim A ykim116 YoungJae-K Youngjae Kim ykim116 OOP344_YJK
Peter (Xiang Qiang) Chen A xqchen3 Sushii Peter Chen Sushii Peter.ug... Just another blog...
Wei Wang A wwang125 weiwang727 Wei Wang BigData Wei's Blog
Fahd Wahab A wfahd FahdW Fahd Wahab FahdW Fahd's C++ Blog

Issues and Status

0.2 MileStone

  • issue 1: 1_AddConsole (by Youngjae Kim and reviewed by Hiroshi Takemoto)
  • issue 2.1: 2.1_CFieldMockup (by Hiroshi Takemoto and reviewed by Peter Chen)
  • issue 2.2: 2.2_CLabelMockup (by Hiroshi Takemoto and reviewed by Peter Chen)
  • issue 2.3: 2.3_CDialogMockup (by Youngjae Kim and reviewed by Hiroshi Takemoto)
  • issue 2.4: 2.4_CLineEditMockup (by Fahd Wahab and reviewed by Youngjae Kim)
  • issue 2.5: 2.5_CButtonMockup (by Youngjae Kim and reviewed by Hiroshi Takemoto)
  • issue 2.6: 2.6_CValEditMockup (by Fahd Wahab and reviewed by Youngjae Kim)
  • issue 2.7: 2.7_CCheckMarkMockup (by Peter Chen and reviewed by Wei Wang)
  • issue 2.8.1: 2.8.1_AddText (by Wei Wang and reviewed by Fahd Wahab)
  • issue 2.8.2: 2.8.2_CTextMockup (by Wei Wang and reviewed by Fahd Wahab)
  • issue 2.9: 2.9_CCheckListMockup (by Peter Chen and reviewed by Wei Wang)

0.3 MileStone

  • issue 3.1.1: 3.1.1_CField (by Hiroshi Takemoto and reviewed by Peter Chen)
  • issue 3.1.2: 3.1.2_CDialog (by Youngjae Kim and reviewed by Fahd Wahab)
  • issue 3.1.3: 3.1.3_CLabel (by Peter Chen and reviewed by Youngjae Kim)
  • issue 3.2.1: 3.2.1_CLineEdit (by Fahd Wahab reviewed by Hiroshi Takemoto)

0.X MileStone

Issues detail, (by whom and reviewed by whom

Coding Rules

  • Each class MUST have its own header file and cpp file for implementation.
  • Use the class name for the name of the file but make sure it is all lowercase.
 For example CFrame class should have cframe.h and cframe.cpp files for its implementation.
  • Add recompilation safeguards to all your header files.
 The name of safeguard must follow the next rule: __[Team name]_[namespace]_[class name]_H__
 
 For example(CFrame.h):
 
 #ifndef __GP_CIO_CFRAME_H__
 #define __GP_CIO_CFRAME_H__
    .................
    .................

 #endif
  • Must use only #ifndef ... #endif for safeguard. (Do not use both #pragma once and #ifndef)
  • Member variables must start from a underscore.
 For example: int _data, char* _covered;
  • The other rules to declare variables
 (X) int i, j;
 (O) int i;
     int j;

 (X) char *_date;
 (O) char* _date;
  • Use 2 spaces for indent (don't use tab)
  • General rules.
 (X) if(true) return x;
 (O} if(true) {
       return x;
     }
 (X) for(;;) x = y;
 (O) for(;;) {
       x = y;
     }
 (O) for(;;);
 (X) void CButton::draw(int rn) {   <--- SPACE between ) and {
 (O) void CButton::draw(int rn){    <--- NO SPACE between ) and {

meetings

  • latest will be on top
  1. topic and date1
  2. topic and date2

discussions