Difference between revisions of "BTP300 To-Do List Fall 2012"
(→Week 4) |
(→Week 4) |
||
| Line 19: | Line 19: | ||
***Run the executable code for A2 Release 0.1 (CFrame). | ***Run the executable code for A2 Release 0.1 (CFrame). | ||
***Inspect the source code of testFrame() in a2test.cpp. | ***Inspect the source code of testFrame() in a2test.cpp. | ||
| − | *Do Workshop 4 ( | + | *Do Workshop 4 first this week, then Workshop 3 for next week(or vice versa). |
*Update the wiki. | *Update the wiki. | ||
**Form a team of 4 for A2 Releases 0.2 & 0.3 | **Form a team of 4 for A2 Releases 0.2 & 0.3 | ||
Revision as of 10:58, 26 September 2012
Contents
Week 1
- Workshop 0 (Reading & Practice) - VERY IMPORTANT!
- Be ready for doing Pair Programming in the computer lab next Monday!
Week 2
- Begin work on Assignment 1 - Line Editing Facility
- Workshop 1 - Macros (Due 11:59 pm, 9/16, Sunday)
Week 3
- Work on A1 as a team! The due date is approaching...
- Update Weekly Log.
- Do Workshop 2 (due on Sunday).
- Do READING on the BTP300 course website.
Week 4
- Do READING on the BTP300 course website.
- Start working on A2 Release 0.1 (CFrame).
- Read the Practical Tips for A2 Release 0.1.
- Run the executable code for A2 Release 0.1 (CFrame).
- Inspect the source code of testFrame() in a2test.cpp.
- Read the Practical Tips for A2 Release 0.1.
- Do Workshop 4 first this week, then Workshop 3 for next week(or vice versa).
- Update the wiki.
- Form a team of 4 for A2 Releases 0.2 & 0.3
- Update your Weekly Log.
