Difference between revisions of "A Team - OOP344"

From CDOT Wiki
Jump to: navigation, search
(Add some information)
m (Corrected the team email)
Line 25: Line 25:
 
|-
 
|-
 
|}
 
|}
[mailto:wtong1@learn.senecac.on.ca,kxu9@learn.senecac.on.ca,ywang268@learn.senecac.on.ca,hmo6@learn.senecac.on.ca,syzhang4@learn.senecac.on.ca,wfchen@learn.senecac.on.ca,cxwang@senecac.on.ca,lwang168@learn.senecac.on.ca  Email to this team]
+
[mailto:wtong1@learn.senecac.on.ca,kxu9@learn.senecac.on.ca,ywang268@learn.senecac.on.ca,hmo6@learn.senecac.on.ca,syzhang4@learn.senecac.on.ca,wfchen@learn.senecac.on.ca,cxwang@learn.senecac.on.ca,lwang168@learn.senecac.on.ca  Email to this team]
  
 
== SVN Account ==
 
== SVN Account ==

Revision as of 02:08, 7 February 2010


OOP344 | Weekly Schedule | Student List | Teams | Project | Student Resources

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 Blog 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

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

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 or some meanfull name in the trunk!

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.