Difference between revisions of "Innovative Coders"

From CDOT Wiki
Jump to: navigation, search
(→‎Coding Rules)
(→‎Application Milestone (Due Sunday Dec 17 14:00))
 
(33 intermediate revisions by 4 users not shown)
Line 10: Line 10:
 
</big>
 
</big>
 
== Repository ==
 
== Repository ==
−
* repo Github id:  
+
* repo Github id: XIV-InvCod
 +
 
 
== Team Members ==
 
== Team Members ==
 
{| class="wikitable sortable" border="1" cellpadding="5"
 
{| class="wikitable sortable" border="1" cellpadding="5"
Line 28: Line 29:
 
|[[User:Tejaskumar Ramanlal Patel | Tejaskumar]]||Patel||A||[mailto:trpatel8@myseneca.ca?subject=oop344 trpatel8]||Github:[http://github.com/trpatel8 trpatel8]||[[Special:Contributions/Tejaskumar Ramanlal Patel | Tejaskumar Ramanlal Patel]]||trpatel8||[http://trpatel8.blogspot.ca/ Tejas Patel's OOP344 Blog]
 
|[[User:Tejaskumar Ramanlal Patel | Tejaskumar]]||Patel||A||[mailto:trpatel8@myseneca.ca?subject=oop344 trpatel8]||Github:[http://github.com/trpatel8 trpatel8]||[[Special:Contributions/Tejaskumar Ramanlal Patel | Tejaskumar Ramanlal Patel]]||trpatel8||[http://trpatel8.blogspot.ca/ Tejas Patel's OOP344 Blog]
 
|}
 
|}
 +
 +
== Issue/Branch Name Format ==
 +
V.V_Name <br /><br />
 +
'''Example:'''<br />
 +
Issue:  Add Text Class to the project (issue 2.9.1).<br />
 +
Issue and Branch name on gitub:<br />
 +
'''2.9.1_AddTextClass'''<br />
  
 
==Issues and Status ==
 
==Issues and Status ==
−
=== Issue description and/or number (1)===
+
==== [[The_CIO_Framework_-_OOP344_20123#Issues | 0.2 Milestone]] (Due Fri 9th)====
 +
# Add console class to project and test with cio_test  (issue 1)
 +
# Create Mock-up classes:
 +
#: Create the class files (header and cpp) with blank methods and '''make sure they compile'''.
 +
## CField Mock-up Class (issue 2.1)- '''Svetlana Molodtsova'''
 +
## CLabel Mock-up Class (issue 2.2)- '''Svetlana Molodtsova'''
 +
## CDialog Mock-up Class (issue 2.3)- '''Prasanth Vaaheeswaran'''
 +
## CLineEdit Mock-up Class (issue 2.4)- '''Prasanth Vaaheeswaran'''
 +
## CButton Mock-up Class (issue 2.5)- '''Shawnique Warren'''
 +
## CValEdit Mock-up Class (issue 2.6)- '''Shawnique Warren
 +
## CCheckMark Mock-up Class (issue 2.7)-'''Atieh Mohammadi'''
 +
## CCheckList Mock-up Class (issue 2.9)- '''Atieh Mohammadi'''
 +
## CText -
 +
### Add Text Class to the project (issue 2.8.1)-'''Tejas Patel'''
 +
### CText Mock-up Class (issue 2.8.2)- '''Tejas Patel'''
 +
 
 +
==== 0.3 Milestone ====
 +
# CField -  '''Svetlana Molodtsova'''
 +
# CLabel -
 +
## Second Constructor, Edit, Draw, Set -'''Atieh Mohammadi'''
 +
## First Constructor, Destructor, Editable- '''Shawnique Warren'''
 +
## Draw , Set -'''Tejas Patel'''
 +
# CDialog - '''Prasanth Vaaheeswaran'''
 +
# CLineEdit -
 +
## First Constructor, edit, editable - '''Shawnique Warren'''
 +
## Destructor, draw - '''Atieh Mohammadi'''
 +
## Second Constructor - '''Svetlana Molodtsova'''
 +
 
 +
==== 0.4 Milestone ====
 +
# Cbutton - '''Shawnique Warren'''
 +
# CValEdit - '''Prasanth Vaaheeswaran'''
 +
# CCheckMark -
 +
## Constructor, Copy Constructor,set, boolean and void radio - '''Atieh Mohammadi'''
 +
## Draw, bool and void checked - '''Svetlana Molodtsova'''
 +
## Edit -'''Tejas Patel'''
 +
 
 +
==== Application Milestone (Due Sunday Dec 16 14:00) ====
 +
# Movie Application Interface - '''Atieh Mohammadi'''
 +
 
 +
===Mandatory===
 +
:90%
 +
# Browse Opened data file - '''Shawnique Warren'''
 +
## goto next record
 +
## goto previous record
 +
## goto last record
 +
## goto first record
 +
## goto record by number
 +
# edit the record - Prasanth + Tejas?
 +
## save the edited record
 +
## cancel editing a record without saving
 +
## make sure edit information is not lost (saving unsaved data on exit with prompt)
 +
# Add a record - ???
 +
## create an empty record and save it at the end of the file
 +
 
 +
==== 0.X Milestone ====
 
* Assigned to: [mailto:EMAILID@myseneca.ca FULLNAME]
 
* Assigned to: [mailto:EMAILID@myseneca.ca FULLNAME]
 
* Code review by: [mailto:EMAILID@myseneca.ca FULLNAME]
 
* Code review by: [mailto:EMAILID@myseneca.ca FULLNAME]
Line 36: Line 98:
 
*: (being developed/pull request/being reviewed/pushed to master)
 
*: (being developed/pull request/being reviewed/pushed to master)
 
* comments:
 
* comments:
−
*:  
+
*:
−
=== Issue description and/or number (2)===
+
 
−
* Assigned to: [mailto:EMAILID@myseneca.ca FULLNAME]
 
−
* Code review by: [mailto:EMAILID@myseneca.ca FULLNAME]
 
−
* Status:
 
−
*: (being developed/pull request/being reviewed/pushed to master)
 
−
* comments:
 
−
*:
 
 
== Coding Rules ==
 
== Coding Rules ==
−
*For indentation - '''2 spaces''' will be used
+
*Indentation - '''2 Spaces''', no Tabs! (Change settings in Visual Studio) [http://wereallforked.tumblr.com/post/36055983477/tabs Instructions ]
−
*All safeguards for header files will use the following format: '''_IC_FILENAME_H_'''
+
*All safeguards for header files will use the following format: '''_IC_FILENAME_H_'''  
−
*Member variables should begin with an underscore (eg int _data)
+
*Member variables should begin with an underscore (i.e. int '''_data''')
 
*Blocks of code will follow the structure outlined below
 
*Blocks of code will follow the structure outlined below
  
−
   if(condition)
+
   if(condition){
−
  {
 
 
     //code here
 
     //code here
 
   }
 
   }
  
 +
*Always use curly brackets (with conditions) even for single line
 
*Label the start and finish when there are large blocks of code
 
*Label the start and finish when there are large blocks of code
 
*Briefly comment each function - outlining its purpose
 
*Briefly comment each function - outlining its purpose
Line 60: Line 116:
 
'''Remember the class standards'''
 
'''Remember the class standards'''
 
*Declaring each variable separately
 
*Declaring each variable separately
−
*Correct pointer placement  (char* str)
+
*Correct pointer placement i.e. '''char* str''' not '''char *str'''
 +
 
 +
== IRC ==
 +
Please familiarize yourself with IRC as we may be using it for group meetings and troubleshooting. Resources are available [[OOP344 Student Resources|here]].
 +
===Channel===
 +
Our official channel is '''#innocoders'''
 +
 
  
 
== meetings ==
 
== meetings ==
  
 
*'''October 19, 2012'''. Group meeting room 1122. Time: 8.55 a.m. to 10.40 a.m.
 
*'''October 19, 2012'''. Group meeting room 1122. Time: 8.55 a.m. to 10.40 a.m.
 +
*'''November 09, 2012'''. Group meeting Room T3135. Time: 5:10 p.m. to 7:00 p.m.
 +
*'''November 15, 2012'''. Group meeting Library. Time: 11:45 a.m. to 1:30 p.m.
 +
*'''November 16, 2012'''. Group meeting room S3011 . Time: 8.55 a.m. to 2:25 p.m.
 +
*'''December 07, 2012'''. Group meeting room S1134 & S3010. Time: 8.55 a.m. to 4:30 p.m.
 
Discussed coding rules and standards, grade distribution.
 
Discussed coding rules and standards, grade distribution.
 
# [[(Irc)logs of meeting number ### - oop344 20113 | topic and date1 ]]
 
# [[(Irc)logs of meeting number ### - oop344 20113 | topic and date1 ]]

Latest revision as of 09:17, 15 December 2012


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)- Svetlana Molodtsova
    2. CLabel Mock-up Class (issue 2.2)- Svetlana Molodtsova
    3. CDialog Mock-up Class (issue 2.3)- Prasanth Vaaheeswaran
    4. CLineEdit Mock-up Class (issue 2.4)- Prasanth Vaaheeswaran
    5. CButton Mock-up Class (issue 2.5)- Shawnique Warren
    6. CValEdit Mock-up Class (issue 2.6)- Shawnique Warren
    7. CCheckMark Mock-up Class (issue 2.7)-Atieh Mohammadi
    8. CCheckList Mock-up Class (issue 2.9)- Atieh Mohammadi
    9. CText -
      1. Add Text Class to the project (issue 2.8.1)-Tejas Patel
      2. CText Mock-up Class (issue 2.8.2)- Tejas Patel

0.3 Milestone

  1. CField - Svetlana Molodtsova
  2. CLabel -
    1. Second Constructor, Edit, Draw, Set -Atieh Mohammadi
    2. First Constructor, Destructor, Editable- Shawnique Warren
    3. Draw , Set -Tejas Patel
  3. CDialog - Prasanth Vaaheeswaran
  4. CLineEdit -
    1. First Constructor, edit, editable - Shawnique Warren
    2. Destructor, draw - Atieh Mohammadi
    3. Second Constructor - Svetlana Molodtsova

0.4 Milestone

  1. Cbutton - Shawnique Warren
  2. CValEdit - Prasanth Vaaheeswaran
  3. CCheckMark -
    1. Constructor, Copy Constructor,set, boolean and void radio - Atieh Mohammadi
    2. Draw, bool and void checked - Svetlana Molodtsova
    3. Edit -Tejas Patel

Application Milestone (Due Sunday Dec 16 14:00)

  1. Movie Application Interface - Atieh Mohammadi

Mandatory

90%
  1. Browse Opened data file - Shawnique Warren
    1. goto next record
    2. goto previous record
    3. goto last record
    4. goto first record
    5. goto record by number
  2. edit the record - Prasanth + Tejas?
    1. save the edited record
    2. cancel editing a record without saving
    3. make sure edit information is not lost (saving unsaved data on exit with prompt)
  3. Add a record - ???
    1. create an empty record and save it at the end of the file

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) Instructions
  • All safeguards for header files will use the following format: _IC_FILENAME_H_
  • 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

IRC

Please familiarize yourself with IRC as we may be using it for group meetings and troubleshooting. Resources are available here.

Channel

Our official channel is #innocoders


meetings

  • October 19, 2012. Group meeting room 1122. Time: 8.55 a.m. to 10.40 a.m.
  • November 09, 2012. Group meeting Room T3135. Time: 5:10 p.m. to 7:00 p.m.
  • November 15, 2012. Group meeting Library. Time: 11:45 a.m. to 1:30 p.m.
  • November 16, 2012. Group meeting room S3011 . Time: 8.55 a.m. to 2:25 p.m.
  • December 07, 2012. Group meeting room S1134 & S3010. Time: 8.55 a.m. to 4:30 p.m.

Discussed coding rules and standards, grade distribution.

  1. topic and date1
  2. topic and date2

discussions

Retrieved from "https://wiki.cdot.senecapolytechnic.ca/w/index.php?title=Innovative_Coders&oldid=92091"