Difference between revisions of "Skynet"
(→Issue description and/or number (2)) |
(→Issues and Status) |
||
| Line 35: | Line 35: | ||
==Issues and Status == | ==Issues and Status == | ||
==== 0.2 Milestone (Due Fri 9th)==== | ==== 0.2 Milestone (Due Fri 9th)==== | ||
| − | # Add console class to project and test with cio_test (issue 1) | + | # Add console class to project and test with cio_test (issue 1) (Assigned to Michael, reviewed by Kang) |
# Create Mock-up classes | # Create Mock-up classes | ||
#: Create the class files (header and cpp) with blank methods and make sure they compile | #: Create the class files (header and cpp) with blank methods and make sure they compile | ||
| − | ## CField Mock-up Class (issue 2.1) | + | ## CField Mock-up Class (issue 2.1) (Assigned to Michael, reviewed by Kang) |
| − | ## CLabel Mock-up Class (issue 2.2) | + | ## CLabel Mock-up Class (issue 2.2) (Assigned to Kang, reviewed by Matt) |
| − | ## CDialog Mock-up Class (issue 2.3) | + | ## CDialog Mock-up Class (issue 2.3) (Assigned to Michael, reviewed by Matt) |
| − | ## CLineEdit Mock-up Class (issue 2.4) | + | ## CLineEdit Mock-up Class (issue 2.4) (Assigned to Dyllon, reviewed by Bruno) |
| − | ## CButton Mock-up Class (issue 2.5) | + | ## CButton Mock-up Class (issue 2.5) (Assigned to Dyllon, reviewed by Bruno) |
| − | ## CValEdit Mock-up Class (issue 2.6) | + | ## CValEdit Mock-up Class (issue 2.6) (Assigned to Matt, reviewed by Dyllon) |
| − | ## CCheckMark Mock-up Class (issue 2.7) | + | ## CCheckMark Mock-up Class (issue 2.7) (Assigned to Matt, reviewed by Dyllon) |
| − | ## CText | + | ## CText (Assigned to Kang, reviewed by Michael) |
### Add Text Class to the project (issue 2.8.1) | ### Add Text Class to the project (issue 2.8.1) | ||
| − | ### CText Mock-up Class (issue 2.8.2) | + | ### CText Mock-up Class (issue 2.8.2) (Assigned to Bruno, reviewed by Michael) |
| − | ## CCheckList Mock-up Class (issue 2.9) | + | ## CCheckList Mock-up Class (issue 2.9) (Assigned to Bruno, reviewed by Michael) |
| + | |||
| + | ===Issue Name Format=== | ||
| + | Issue and branch name format:<br /> | ||
| + | V.V_Name <br /> | ||
== Coding Rules == | == Coding Rules == | ||
Revision as of 11:29, 6 November 2012
OOP344 | Weekly Schedule | Student List | Teams | Project | Student Resources
Contents
Team Name (Skynet)
Project Marking Percentage
Group work: 50% Individual work: 50% + ------------------------- Total 100%
Repository
- repo Github id:
Team Members
| First Name | Last Name | Section | Seneca Id | Github ID | wiki id | IRC nick | Blog URL |
|---|---|---|---|---|---|---|---|
| Michael | Wang | B | mmwang2 | MichaelMWang | Michael Mengyuan Wang | mekko | Michael's Blog |
| Bruno | Pereira | B | bpereira5 | bpereira5 | Bruno Pereira | bpereira | Open Source |
| Kanghoon | Park | B | kpark27 | kpark27 | Kanghoon Park | kpark27 | Kang's Blog |
| Matthew | Torrance | B | mstorrance | mstorrance | Matthew Scott Torrance | mstorrance | Matt's Blog |
| Dyllon | Ricardo | A | ddricardo | Dyllon-R | Dyllon Da Silva Ricardo | Dyllon-R | Dyll's Tech Blog |
Issues and Status
0.2 Milestone (Due Fri 9th)
- Add console class to project and test with cio_test (issue 1) (Assigned to Michael, reviewed by Kang)
- 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) (Assigned to Michael, reviewed by Kang)
- CLabel Mock-up Class (issue 2.2) (Assigned to Kang, reviewed by Matt)
- CDialog Mock-up Class (issue 2.3) (Assigned to Michael, reviewed by Matt)
- CLineEdit Mock-up Class (issue 2.4) (Assigned to Dyllon, reviewed by Bruno)
- CButton Mock-up Class (issue 2.5) (Assigned to Dyllon, reviewed by Bruno)
- CValEdit Mock-up Class (issue 2.6) (Assigned to Matt, reviewed by Dyllon)
- CCheckMark Mock-up Class (issue 2.7) (Assigned to Matt, reviewed by Dyllon)
- CText (Assigned to Kang, reviewed by Michael)
- Add Text Class to the project (issue 2.8.1)
- CText Mock-up Class (issue 2.8.2) (Assigned to Bruno, reviewed by Michael)
- CCheckList Mock-up Class (issue 2.9) (Assigned to Bruno, reviewed by Michael)
Issue Name Format
Issue and branch name format:
V.V_Name
Coding Rules
meetings
- latest will be on top
