Changes

Jump to: navigation, search

CpaCoderpz - oop344 20123

4,769 bytes added, 14:07, 22 November 2012
0.4 Milestone
== Project Marking Percentage ==
* due immediately  <big>  Group work: 50% XX% (25 <= xx <= 50)  Individual work: XX 50% + (50 <= xx <= 75)
-------------------------
  Total 100% </big>
== Repository ==
* repo Github id:   [https://github.com/Seneca-OOP344/X-CpaCdr/ X-CpaCdr]
== Team Members ==
|-
 
|[[User:klara|Kelly]]||Lara||[[cpaCoderpz|cpaCoderpz]]||A||[mailto:klara@myseneca.ca?subject=oop344 klara]||[[Special:Contributions/klara|klara]]||kmlara||kmlara|| [http://kmlara.blogspot.ca/ Occupation:student]
 
|-
|[[User:Leo Turalba|Vernileo]]||Turalba||[[cpaCoderpz|cpaCoderpz]]||A||[mailto:vturalba@learn.senecac.on.ca?subject=oop344 vturalba]||[[Special:Contributions/Leo Turalba|Leo Turalba]]||Ltur||leoturalba||[http://leoturalba.blogspot.ca/ Blogging Coderz]
|-
|[[User:Joseph_Visconti|Joseph]]||Visconti||[[cpaCoderpz|cpaCoderpz]]||B||[mailto:jvisconti2@myseneca.ca?subject=oop344 jvisconti2]||[[Special:Contributions/Joseph_Visconti|Joseph_Visconti]]||Visconti||Joseph-Visconti|| [http://josephvisconti.wordpress.com/ OOP344]
|-
==Issues and Status ==
=== Issue description 0.2 Milestone ===# Add console class to project and test with cio_test (issue 1) (by Freddy Cheungh - reviewed by Joseph Visconti)# Create Mock-up classes#: Create the class files (header and/or number cpp) with blank methods and make sure they compile## CField Mock-up Class (issue 2.1) (by Matt Jang - reviewed by Freddy Cheungh)## CLabel Mock-up Class (issue 2.2) (by Matt Jang - reviewed by Freddy Cheungh)## CDialog Mock-up Class (issue 2.3) (by Matt Jang - reviewed by Freddy Cheungh)## CLineEdit Mock-up Class (issue 2.4) (by Freddy Cheungh - reviewed by Joseph Visconti)## CButton Mock-up Class (issue 2.5) (by Joseph Visconti - reviewed by Vernileo Turalba)## CValEdit Mock-up Class (issue 2.6) (by Joseph Visconti - reviewed by Vernileo Turalba)## CCheckMark Mock-up Class (issue 2.7) (by Joseph Visconti - reviewed by Vernileo Turalba)## CText ### Add Text Class to the project (issue 2.8.1)===(by Vernileo Turalba - reviewed by Matt Jang)### CText Mock-up Class (issue 2.8.2) (by Vernileo Turalba - reviewed by Matt Jang)## CCheckList Mock-up Class (issue 2.9) (by Vernileo Turalba - reviewed by Matt Jang)
* Assigned to: [mailto:EMAILID@myseneca.ca FULLNAME]
* Code review by: [mailto:EMAILID@myseneca=== 0.ca FULLNAME]3 Milestone ===
* Status:# CField (issue 3.1) (by Joseph Visconti - reviewed by Freddy Cheungh)# CDialog (issue 3.2) (by Freddy Cheungh & Matt Jang - reviewed by Vernileo Turalba)# CLabel (issue 3.3) (by Freddy Cheungh & Joseph Visconti - reviewed by Matt Jang)# CLineEdit (issue 3.4) (by Vernileo Turalba - reviewed by Joseph Visconti)
*: === 0.4 Milestone ===# CButton (being developed/pull request/being issue 4.1) (by Joseph Visconti - reviewed by Freddy Cheungh)# CValEdit (issue 4.2) (by Vernileo Turalba - reviewed by Matt Jang)# CCheckMark (issue 4.3) (by Freddy Cheungh & Matt Jang - reviewed/pushed to masterby Vernileo Turalba & Joseph Visconti)
* comments:=== 0.5 Milestone ===# CText (issue 5.1)# CCheckList (issue 5.2)
== Coding Rules =='''General'''*: tab four (4) spaces* do not cut off long lines* use spaces and not tabs* ordering rules may be broken if needed for functionality or practicality
=== Issue description '''Naming'''* private variables and/or number methods must start with an underscore (2_)* variable names use camel case starting with a lowercase letter (variableName)* method and function names use camel case starting with a lowercase letter (methodName)* class names use camel case starting with an uppercase letter (ClassName)* constant names are all uppercase and words are split with an underscore (CONSTANT_NAMES)===
'''Variables'''* Assigned in classes, order variables by type and then name unless an alternate order is required to: [mailto:EMAILID@myseneca.ca FULLNAME]function* primitive before non primitive* with primitive types, largest to smallest* order non primitive types alphabetically
'''Classes'''* Code review by: [mailto:EMAILID@myseneca.ca FULLNAME]in class interfaces everything is indented at least one level* in class interfaces in scopes that are specified, indent the method and variable declarations in that scope an additional level* declare variables before methods in a scope* variable names are not included in the interface* method comments are in the implementation* variable comments are in the interface* constructors and destructors are declared first in their scope
* Status<pre>class ExampleClass { int _privateVariable; public: bool status; int something(int);};</pre>
'''Conditional Statements'''*: (being developed/pull request/being reviewed/pushed to master)else and else if statements take place the line after a closing bracket* no break on default case in switch statement* in switch statement, break statements share the same indent level as a case statement* always use brackets, even with single line statements
* comments:<pre>if (false) { statement;}else { statement;}
*switch (1) { case 2: statement; break; default: statement;}</pre>
'''Loops'''* in for loops, use the letter i to count iterations* in nested for loops, use alphabetically increased letters from the letter i as iteration counters (i, j, k, ect)* always use brackets or ; to declare that there is no code to be run each loop <pre>for (int i =0; i < 10; i++);</pre> <pre>for (int i = Coding Rules 0; i < 10; i++) { for (int j =0; j < 10; j++) { statement; }}</pre> '''Comments'''* comments for variables take place on the same line as the variable* method and function comments must always be multi-line comments* method and function comments describe the method or function and then specify the the parameters and return with a short description (if needed) of each* code blocks of over 20 lines can have their end bracket commented <pre>/* * increases a number by 1 * * param: num, the integer number to increase * return: num increased by 1 * */int func(int num) { return num + 1;}</pre> '''Spacing'''* if, for, switch and while statements are followed by a space before the open parentheses* the close parentheses for these statements is followed by a space before the open curly bracket* when the parentheses is followed by a semicolon, there is no space* in for statements, each semicolon is followed by a space unless it is empty* for method and function declaration, there is no space between the end of the name and the open parentheses <pre>switch (1) { case 2: statement; break; default: statement;}</pre> <pre>if (true) { statement;}else if (false) { statement}else { statement;}</pre> <pre>for (int i =0; i < 10; i++); while (false) { statement;} do { statement;} while (true);</pre> '''Includes'''* order includes in order of priority then alphabetically
== meetings ==

Navigation menu