Difference between revisions of "A Team - OOP344"
m (→TO DO LIST) |
m (→TO DO LIST) |
||
| Line 69: | Line 69: | ||
| [mailto:ywang268@learn.senecac.on.ca ywang268] || btext.h bframe.h bframe.cpp OpText.cpp|| Done | | [mailto:ywang268@learn.senecac.on.ca ywang268] || btext.h bframe.h bframe.cpp OpText.cpp|| Done | ||
|- | |- | ||
| − | | [mailto:hmo6@learn.senecac.on.ca hmo6] || - ||- | + | | [mailto:hmo6@learn.senecac.on.ca hmo6] ||bedit.h bedit.cpp - ||- |
|- | |- | ||
| [mailto:syzhang4@learn.senecac.on.ca syzhang4] || blable.h blable.cpp || - | | [mailto:syzhang4@learn.senecac.on.ca syzhang4] || blable.h blable.cpp || - | ||
Revision as of 14:24, 20 March 2010
OOP344 | Weekly Schedule | Student List | Teams | Project | Student Resources
Contents
Team Members
| Last Name | Name | Seneca Username | Section | Blog Url | IRC Nick | SVN ID | My Contributions | Role |
|---|---|---|---|---|---|---|---|---|
| Tong | Wei | wtong1 | A | Blog | wtong1 | wtong1 | Contributions | Team Contact |
| Xu | Kai | kxu9 | A | http://kxu9.blogspot.com/ | kxu9 | kxu9 | Contributions | Team Contact |
| Wang | Yu | ywang268 | A | Blog | ywang268 | ywang268 | Contributions | |
| Mo | Hsiu-Mei | hmo6 | A | Blog | hmo6 | hmo6 | Contributions | |
| Zhang | Shun Yao | syzhang4 | A | Blog | DownWind | syzhang4 | Contributions | |
| Chen | Wen Fang | wfchen | A | Gwen's Blog | wfchen | wfchen | Contributions | |
| Wang | Chun Xia | cxwang | A | cxwang's Blog | cxatseneca | cxwang | Contributions | |
| Wang | Liang | lwang168 | A | Blog | lwang168 | lwang168 | Contributions |
SVN Account
oop344_101rep2
TO DO LIST
| Seneca Username | Function | Complete status |
|---|---|---|
| wtong1 | bio_init, bio_displayflag | bio_init, bio_displayflag |
| kxu9 | bio_end, bio_getch, bio_flag | bio_end, bio_getch, bio_flag |
| ywang268 | bio_flush, Escape key and default key in bio_edit | bio_flush, Escape key and default key in bio_edit complete |
| hmo6 | bio_clrscr, bio_move, key value of MAC | bio_clrscr, bio_move, key value of MAC |
| syzhang4 | bio_MenuItem, backspace key in bio_edit | bio_MenuItem Ver.1.00 backspace Ver. 1.2 Update in taps |
| wfchen | bio_putstr, bio_displayMenuItem | V1.0 for putstr in BCC, V2.0 for displayMenuItem() under my tags |
| cxwang | bio_rows, bio_cols, right key and end key in bio_edit | RIGHT_KEY and END_KEY update with test method. |
| lwang168 | bio_putch, TAB key and Insert key in bio_edio | bio_putch,TAB key and Insert key are updated |
| Seneca Username | Function | Complete status |
|---|---|---|
| wtong1 | bfield.h bfield.cpp | Done |
| kxu9 | bfield.cpp blabel.cpp | bfield.cpp Done |
| ywang268 | btext.h bframe.h bframe.cpp OpText.cpp | Done |
| hmo6 | bedit.h bedit.cpp - | - |
| syzhang4 | blable.h blable.cpp | - |
| wfchen | btext.h bframe.h bframe.cpp OpText.cpp | Done |
| cxwang | bedit.h bedit.cpp | - |
| lwang168 | bform.h bform.cpp | - |
Team Announcement
Our first IRC meeting will on 20:00-22:00 27 Jan.(Wednesday) IRC meeting record Notes for meeting
Our second IRC meeting will on 20:00-22:00 6 Feb.(Saturday) IRC meeting record Notes for meeting
Our third IRC meeting will on 20:00-21:00 10 Feb.(Wednesday) IRC meeting record
Our fourth IRC meeting will on 19:00-21:00 3 Mar.(Wednesday) IRC meeting record Notes for meeting
Our fifth IRC meeting will on 20:00-21:00 6 Mar.(Saturday) IRC meeting record
Our sixth IRC meeting will on 20:00-21:00 10 Mar.(Wednesday) IRC meeting record
Our seventh IRC meeting will on 20:00-21:00 12 Mar.(Friday)
Our Next IRC meeting will on 20:00-21:00 17 Mar.(Wednesday)
Assignment 1 direct link click here
To all the team member!(No News)
Please "Check out" with svn://zenit.senecac.on.ca/oop344_101rep2 and verify your user name and password which informed in Fardad's email
Please create your own working folder with your svn ID in the branches, and create a text file with your svn ID in the trunk! Rules
Team Coding Rules
Conventions and Styles
- File heading : Please include a comment heading stating the file name, author, date create, and short description
- Function comment : Please include a comment above the function
- Inline comment : Please use inline comment when the code is hard to understand.
- Indent : Please indent all the code in same block. There will be no tab use.
- Variables and function naming : follow Fordad's style.
