Difference between revisions of "Alpha"

From CDOT Wiki
Jump to: navigation, search
(→‎Team Members)
(→‎Issues and Status)
Line 36: Line 36:
 
==Issues and Status ==
 
==Issues and Status ==
 
=== Issue description and/or number (1)===
 
=== Issue description and/or number (1)===
 +
* Assigned to: [mailto:ssun24@myseneca.ca Shijie Sun]
 +
* Code review by: [mailto:ssun24@myseneca.ca Shijie Sun]
 +
* Status: pushed to master
 +
* comments:
 +
*:
 +
# 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
 +
=== 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:
 +
*:
 +
## CField Mock-up Class (issue 2.1)
 +
=== Issue description and/or number (3)===
 +
* 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:
 +
*:
 +
## CLabel Mock-up Class (issue 2.2)
 +
=== Issue description and/or number (4)===
 +
* 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:
 +
*:
 +
## CDialog Mock-up Class (issue 2.3)
 +
=== Issue description and/or number (5)===
 +
* 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:
 +
*:
 +
## CLineEdit Mock-up Class (issue 2.4)
 +
=== Issue description and/or number (6)===
 +
* 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:
 +
*:
 +
## CButton Mock-up Class (issue 2.5)
 +
=== Issue description and/or number (7)===
 
* 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 41: Line 90:
 
*: (being developed/pull request/being reviewed/pushed to master)
 
*: (being developed/pull request/being reviewed/pushed to master)
 
* comments:
 
* comments:
−
*:  
+
*:
 +
## CValEdit Mock-up Class (issue 2.6)
 +
=== Issue description and/or number (8)===
 +
* 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:
 +
*:
 +
## CCheckMark Mock-up Class (issue 2.7)
 +
## CText
 +
=== Issue description and/or number (9)===
 +
* 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:
 +
*:
 +
### Add Text Class to the project (issue 2.8.1)
 +
=== Issue description and/or number (10)===
 +
* 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:
 +
*:
 +
### CText Mock-up Class (issue 2.8.2)
 +
=== Issue description and/or number (11)===
 +
* 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:
 +
*:
 +
## CCheckList Mock-up Class (issue 2.9)
 +
 
 +
 
 +
example:
 
=== Issue description and/or number (2)===
 
=== Issue description and/or number (2)===
 
* Assigned to: [mailto:EMAILID@myseneca.ca FULLNAME]
 
* Assigned to: [mailto:EMAILID@myseneca.ca FULLNAME]
Line 48: Line 134:
 
*: (being developed/pull request/being reviewed/pushed to master)
 
*: (being developed/pull request/being reviewed/pushed to master)
 
* comments:
 
* comments:
−
*:  
+
*:
 +
 
 
== Coding Rules ==
 
== Coding Rules ==
 
== meetings ==
 
== meetings ==

Revision as of 00:12, 8 November 2012

ALPHA

Project Marking Percentage

  • due immediately 

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

Repository

  • repo Github id:

Team Members

Team Name (team x)
First Name Last Name Section Seneca Id Github ID wiki id IRC nick Blog URL
Shijie Sun B ssun24 nihao123 Shijie Sun Jack Sun program344
Sivathanushan Easwaran B seaswaran sivae Sivathanushan Easwaran LineCircle OOP344Class
James Marmer B jmarmer jamesm007 James Marmer ToraReaper Blog
Ronny Wan B rwan3 ronnywan Ronny Wan ronnywann ronnywann
Jungmin Ji B jjungmin Ji Jungmin Ji Jungmin Viscaria Hit!

Issues and Status

Issue description and/or number (1)

  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

Issue description and/or number (2)

  • Assigned to: FULLNAME
  • Code review by: FULLNAME
  • Status:
    (being developed/pull request/being reviewed/pushed to master)
  • comments:
    1. CField Mock-up Class (issue 2.1)

Issue description and/or number (3)

  • Assigned to: FULLNAME
  • Code review by: FULLNAME
  • Status:
    (being developed/pull request/being reviewed/pushed to master)
  • comments:
    1. CLabel Mock-up Class (issue 2.2)

Issue description and/or number (4)

  • Assigned to: FULLNAME
  • Code review by: FULLNAME
  • Status:
    (being developed/pull request/being reviewed/pushed to master)
  • comments:
    1. CDialog Mock-up Class (issue 2.3)

Issue description and/or number (5)

  • Assigned to: FULLNAME
  • Code review by: FULLNAME
  • Status:
    (being developed/pull request/being reviewed/pushed to master)
  • comments:
    1. CLineEdit Mock-up Class (issue 2.4)

Issue description and/or number (6)

  • Assigned to: FULLNAME
  • Code review by: FULLNAME
  • Status:
    (being developed/pull request/being reviewed/pushed to master)
  • comments:
    1. CButton Mock-up Class (issue 2.5)

Issue description and/or number (7)

  • Assigned to: FULLNAME
  • Code review by: FULLNAME
  • Status:
    (being developed/pull request/being reviewed/pushed to master)
  • comments:
    1. CValEdit Mock-up Class (issue 2.6)

Issue description and/or number (8)

  • Assigned to: FULLNAME
  • Code review by: FULLNAME
  • Status:
    (being developed/pull request/being reviewed/pushed to master)
  • comments:
    1. CCheckMark Mock-up Class (issue 2.7)
    2. CText

Issue description and/or number (9)

  • Assigned to: FULLNAME
  • Code review by: FULLNAME
  • Status:
    (being developed/pull request/being reviewed/pushed to master)
  • comments:
      1. Add Text Class to the project (issue 2.8.1)

Issue description and/or number (10)

  • Assigned to: FULLNAME
  • Code review by: FULLNAME
  • Status:
    (being developed/pull request/being reviewed/pushed to master)
  • comments:
      1. CText Mock-up Class (issue 2.8.2)

Issue description and/or number (11)

  • Assigned to: FULLNAME
  • Code review by: FULLNAME
  • Status:
    (being developed/pull request/being reviewed/pushed to master)
  • comments:
    1. CCheckList Mock-up Class (issue 2.9)


example:

Issue description and/or number (2)

  • Assigned to: FULLNAME
  • Code review by: FULLNAME
  • Status:
    (being developed/pull request/being reviewed/pushed to master)
  • comments:

Coding Rules

meetings

  • latest will be on top
  1. topic and date1
  2. topic and date2

discussions

Question and discuss

  • Nothing for now...
Retrieved from "https://wiki.cdot.senecapolytechnic.ca/w/index.php?title=Alpha&oldid=90776"