Open main menu

CDOT Wiki β

A Team - OOP344

Revision as of 11:41, 10 February 2010 by Lush (talk | contribs) (added 'to do list' to team wikipage)

Team Members

A Team - Member list
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

Email to this team

SVN Account

oop344_101rep2

TO DO LIST

A Team - assignment1 to do list
Seneca Username Function Complete state
wtong1 bio_init, bio_displayflag -
kxu9 bio_end, bio_getch, bio_flag -
ywang268 bio_flush, default in bio_edit -
hmo6 bio_clrscr, bio_move, key value of MAC -
syzhang4 bio_MenuItem, backspace key in bio_edit -
wfchen bio_putstr, bio_displayMenuItem -
cxwang bio_rows, bio_cols, right key and end key in bio_edit -
lwang168 bio_putch, TAB key and Insert key in bio_edio -

Team Announcement

Our first IRC meeting will on 20:00-22:00 27 Jan.(wednesday) Notes for meeting

Our second IRC meeting will on 20:00-22:00 6 Feb.(Saturday) Notes for meeting

Our third IRC meeting will on 20:00-21:00 10 Feb.(wednesday)

Assignment 1 direct link click here

To all the team member!(Feb.02.2010)

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.