Difference between revisions of "Innovative Coders"
(→Application Milestone) |
(→Application Milestone) |
||
Line 75: | Line 75: | ||
==== Application Milestone ==== | ==== Application Milestone ==== | ||
− | # Interface for movie application -'''Atieh Mohammadi''' | + | # Interface for movie application - '''Atieh Mohammadi''' |
===Mandatory=== | ===Mandatory=== |
Revision as of 16:59, 12 December 2012
OOP344 | Weekly Schedule | Student List | Teams | Project | Student Resources
Contents
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
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)
- 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
- Interface for movie application - Atieh Mohammadi
Mandatory
- 90%
- Browse Opened data file - ???
- 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: 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.
Discussed coding rules and standards, grade distribution.