Difference between revisions of "The Sixth Core 20123 - OOP344"

From CDOT Wiki
Jump to: navigation, search
(→‎Application)
(→‎3.1.2_CDialog)
 
Line 111: Line 111:
  
 
=== 3.1.2_CDialog ===
 
=== 3.1.2_CDialog ===
−
* Assigned to: [mailto:sahankoub@myseneca.ca Saeid Ahankoub] & [mailto:ammobasseri@myseneca.ca Amir Mohammad Mobasseri]
+
* Assigned to: [mailto:ammobasseri@myseneca.ca Amir Mohammad Mobasseri]
 
* Code review by: [mailto:rmpietrangelo@myseneca.ca Rocco Pietrangelo]
 
* Code review by: [mailto:rmpietrangelo@myseneca.ca Rocco Pietrangelo]
 
* Status: being developed
 
* Status: being developed
−
* comments:  
+
* comments:
  
 
=== 3.1.3_CLineEdit ===
 
=== 3.1.3_CLineEdit ===

Latest revision as of 12:23, 16 December 2012


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

The Sixth Core (XIII)

Project Marking Percentage

  • due immediately 

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

Repository

  • repo Github id: XIII-SixCor

Team Members

Team Name (The Sixth Core)
First Name Last Name Section Seneca Id wiki id IRC nick Blog URL
Amir Mohammad Mobasseri B ammobasseri ammobasseri ammobasseri Amir's Blog
Saeid Ahankoub B sahankoub Saeid Ahankoub sahankoub C++ Blog
Prateek Chadha B prateek Prateek Chadha aviat0r prateek chadha
Rocco Pietrangelo A rmpietrangelo WikiID IrcNick oop344-seneca

Issues and Status

1.0_AddConsoleClass

2.1_CFieldMockups

2.2_CLabelMockups

2.3_CDialogMockups

2.4_CLineEditMockups

2.5_CButtonMockups

2.6_CValEditMockups

2.7_CCheckMarkMockups

2.8_CTextMockups

2.9_CCheckListMockups

3.1.1_CField

3.1.2_CDialog

3.1.3_CLineEdit

3.1.4_CLabel

4.0.1_CCheckMark

4.1.1_CButton

4.2.1_CValEdit

Application

Coding Rules

  • Use Safegaurd for header files with the format of _XIII_FILENAME_H_
  • Data members in any classes start with underscore(_), for example _data
  • Use Capital letter for the second (third, forth, ...) word of variables with compound words
  • Use meaningfully variable names
  • Use 2 spaces for indentation
  • Use only SPACE BAR for indentation (do not use Tab)
  • Use curly-braces for all kinds of loops, if statements, switch, etc. For example,
 if (condition){
   code;   
 } // end if
  • Comment shortly and properly, specially at the end of long scopes
  • You can use extra spaces to align statements or blank line between parts of the code that you are going to put comment

meetings

  • latest will be on top
  1. We need to make a meeting time for our group so we can discuss the issues and get organized.
  2. topic and date1
  3. topic and date2

discussions

Retrieved from "https://wiki.cdot.senecapolytechnic.ca/w/index.php?title=The_Sixth_Core_20123_-_OOP344&oldid=92096"