Difference between revisions of "A Team - OOP344"

From CDOT Wiki
Jump to: navigation, search
(→‎IRC first meeting: editing)
(→‎TO DO LIST)
 
(68 intermediate revisions by 8 users not shown)
Line 8: Line 8:
 
! Last Name !! Name !! Seneca Username !! Section !! Blog Url !! IRC Nick !! SVN ID !! My Contributions !! Role
 
! Last Name !! Name !! Seneca Username !! Section !! Blog Url !! IRC Nick !! SVN ID !! My Contributions !! Role
 
|-
 
|-
−
| Tong || Wei || [mailto:wtong1@learn.senecac.on.ca wtong1] || A || [http://zakoop344.blogspot.com/ Blog] || wtong1 || not yet || [[Special:Contributions/wtong1 | Contributions]] || Team Contact
+
| Tong || Wei || [mailto:wtong1@learn.senecac.on.ca wtong1] || A || [http://zakoop344.blogspot.com/ Blog] || wtong1 || wtong1 || [[Special:Contributions/wtong1 | Contributions]] || Team Contact
 
|-
 
|-
−
| Xu || Kai || [mailto:kxu9@learn.senecac.on.ca kxu9] || A || [http://kxu9.blogspot.com/ Blog] || kxu9 || not yet || [[Special:Contributions/RedCool | Contributions]] || Team Contact
+
| Xu || Kai || [mailto:kxu9@learn.senecac.on.ca kxu9] || A || http://kxu9.blogspot.com/ || kxu9 || kxu9 || [[Special:Contributions/RedCool | Contributions]] || Team Contact
 
|-
 
|-
−
| Wang || Yu || [mailto:ywang268@learn.senecac.on.ca ywang268] || A || [http://ywang268.blogspot.com/ Blog] || ywang268 || not yet || [[Special:Contributions/lush | Contributions]] ||  
+
| Wang || Yu || [mailto:ywang268@learn.senecac.on.ca ywang268] || A || [http://ywang268.blogspot.com/ Blog] || ywang268 || ywang268 || [[Special:Contributions/lush | Contributions]] ||  
 
|-
 
|-
−
| Mo || Hsiu-Mei || [mailto:hmo6@learn.senecac.on.ca hmo6] || A || [http://hmo6.blogspot.com/ Blog] || hmo6 || not yet || [[Special:Contributions/hmo6 | Contributions]] ||  
+
| Mo || Hsiu-Mei || [mailto:hmo6@learn.senecac.on.ca hmo6] || A || [http://hmo6.blogspot.com/ Blog] || hmo6 || hmo6 || [[Special:Contributions/hmo6 | Contributions]] ||  
 
|-
 
|-
−
| Zhang || Shun Yao ||[mailto:syzhang4@learn.senecac.on.ca syzhang4] || A || [http://shunyao-cpa.blogspot.com/ Blog] || DownWind || not yet || [[Special:Contributions/warcalling | Contributions]] ||  
+
| Zhang || Shun Yao ||[mailto:syzhang4@learn.senecac.on.ca syzhang4] || A || [http://shunyao-cpa.blogspot.com/ Blog] || DownWind || syzhang4 || [[Special:Contributions/warcalling | Contributions]] ||  
 
|-
 
|-
−
| Chen || Wen Fang || [mailto:wfchen@learn.senecac.on.ca wfchen] || A || [http://wfchen2010.blogspot.com/ Gwen's Blog] || wfchen || not yet || [[Special:Contributions/wfchen | Contributions]] ||  
+
| Chen || Wen Fang || [mailto:wfchen@learn.senecac.on.ca wfchen] || A || [http://wfchen2010.blogspot.com/ Gwen's Blog] || wfchen || wfchen || [[Special:Contributions/wfchen | Contributions]] ||  
 
|-
 
|-
−
| Wang|| Chun Xia||  [mailto:cxwang@learn.senecac.on.ca cxwang] || A || [http://cxatseneca.blogspot.com/ cxwang's Blog] ||  cxatseneca || not yet || [[Special:Contributions/cxatseneca | Contributions]] ||
+
| Wang|| Chun Xia||  [mailto:cxwang@learn.senecac.on.ca cxwang] || A || [http://cxatseneca.blogspot.com/ cxwang's Blog] ||  cxatseneca || cxwang || [[Special:Contributions/cxatseneca | Contributions]] ||
 
|-
 
|-
−
| Wang || Liang || [mailto:lwang168@learn.senecac.on.ca lwang168] || A || [http://lwang168.blogspot.com/ Blog] || lwang168 || not yet || [[Special:Contributions/lwang | Contributions]] ||  
+
| Wang || Liang || [mailto:lwang168@learn.senecac.on.ca lwang168] || A || [http://lwang168.blogspot.com/ Blog] || lwang168 || lwang168 || [[Special:Contributions/lwang | Contributions]] ||  
 
|-
 
|-
 
|}
 
|}
−
[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 ==
 
<big>
 
<big>
 
oop344_101rep2
 
oop344_101rep2
 +
 
</big>
 
</big>
 +
 +
== TO DO LIST ==
 +
 +
{| class="wikitable sortable" border="1" cellpadding="5"
 +
 +
|+ A Team - assignment1 to do list
 +
! Seneca Username !! Function !! Complete status
 +
|-
 +
| [mailto:wtong1@learn.senecac.on.ca wtong1] || bio_init, bio_displayflag || bio_init, bio_displayflag
 +
|-
 +
| [mailto:kxu9@learn.senecac.on.ca kxu9] || bio_end, bio_getch, bio_flag || bio_end, bio_getch, bio_flag
 +
|-
 +
| [mailto:ywang268@learn.senecac.on.ca ywang268] || bio_flush, Escape key and default key in bio_edit || bio_flush, Escape key and default key in bio_edit complete
 +
|-
 +
| [mailto:hmo6@learn.senecac.on.ca hmo6] || bio_clrscr, bio_move, key value of MAC ||bio_clrscr, bio_move, key value of MAC
 +
|-
 +
| [mailto:syzhang4@learn.senecac.on.ca syzhang4] || bio_MenuItem, backspace key in bio_edit || bio_MenuItem Ver.1.00 backspace Ver. 1.2 Update in taps
 +
|-
 +
| [mailto:wfchen@learn.senecac.on.ca wfchen] || bio_putstr, bio_displayMenuItem ||V1.0 for putstr in BCC, V2.0 for displayMenuItem() under my tags
 +
|-
 +
| [mailto:cxwang@learn.senecac.on.ca cxwang] || bio_rows, bio_cols, right key and end key in bio_edit ||RIGHT_KEY and END_KEY update with test method.
 +
|-
 +
| [mailto:lwang168@learn.senecac.on.ca lwang168] || bio_putch, TAB key and Insert key in bio_edio ||bio_putch,TAB key and Insert key are updated
 +
|-
 +
|}
 +
 +
{| class="wikitable sortable" border="1" cellpadding="5"
 +
|+ A Team - PRJ0.5 to do list
 +
! Seneca Username !! Function !! Complete status
 +
|-
 +
| [mailto:wtong1@learn.senecac.on.ca wtong1] || bfield.h bfield.cpp || Done
 +
 +
|-
 +
| [mailto:kxu9@learn.senecac.on.ca kxu9] || bfield.cpp blabel.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] ||bedit.h bedit.cpp - ||Done
 +
|-
 +
| [mailto:syzhang4@learn.senecac.on.ca syzhang4] || blable.h blable.cpp || Done
 +
|-
 +
| [mailto:wfchen@learn.senecac.on.ca wfchen] || btext.h bframe.h bframe.cpp OpText.cpp|| Done
 +
|-
 +
| [mailto:cxwang@learn.senecac.on.ca cxwang] || bedit.h bedit.cpp || Done
 +
|-
 +
| [mailto:lwang168@learn.senecac.on.ca lwang168] || bform.h bform.cpp || Done
 +
|-
 +
|}
 +
 +
== Remember !!!! ==
 +
 +
We must hand in "TeamSelfMarking" sheet for every team member include yourself and you can download it in class note trunk\TeamSelfMarking!
  
 
== Team Announcement ==
 
== Team Announcement ==
  
−
Our first IRC meeting will on 20:00-22:00 27 jan.(wednesday)
+
Our first IRC meeting will on 20:00-22:00 27 Jan.(Wednesday) [http://fardad.com/irclogs/Default.aspx?co=0&log=%23seneca-oop344.freenode.20100127&u1=All+Users&u2=No+One+Else&u3=No+One+Else&u4=No+One+Else  IRC meeting record]  [[A Team IRC meeting | Notes for meeting]]
  
−
== IRC first meeting ==
+
Our second IRC meeting will on 20:00-22:00 6 Feb.(Saturday) [http://fardad.com/irclogs/Default.aspx?co=0&log=%23seneca-oop344.freenode.20100206&u1=All+Users&u2=No+One+Else&u3=No+One+Else&u4=No+One+Else  IRC meeting record]  [[A Team IRC meeting | Notes for  meeting]]
−
1-     First of all, understand that IRC meetings and chats are much slower than talking so be patient
 
  
−
2-     IRC in nature is a very casual environment, so don't be surprised to see casual talk like : wassssssup!!!!!!! But in at the same time, make sure not to cross the line by used bad and impolite words. (no "F" words for example)
+
Our third IRC meeting will on 20:00-21:00 10 Feb.(Wednesday) [http://fardad.com/irclogs/Default.aspx?co=0&log=%23seneca-oop344.freenode.20100210&u1=All+Users&u2=No+One+Else&u3=No+One+Else&u4=No+One+Else  IRC meeting record]
  
−
3-       Since visual contact is not possible, every now and the drop a word to show the meeting holder you are there ok?
+
Our fourth IRC meeting will on 19:00-21:00 3 Mar.(Wednesday) [http://fardad.com/irclogs/Default.aspx?co=0&log=%23seneca-oop344.freenode.20100303&u1=All+Users&u2=No+One+Else&u3=No+One+Else&u4=No+One+Else  IRC meeting record]  [[A Team IRC meeting | Notes for  meeting]]
  
−
4-     when in a meeting being funny with one or two smart thing to say, it ok, but again, DO NOT over do it
+
Our fifth IRC meeting will on 20:00-21:00 6 Mar.(Saturday) [http://fardad.com/irclogs/Default.aspx?co=0&log=%23seneca-oop344.freenode.20100306&u1=All+Users&u2=No+One+Else&u3=No+One+Else&u4=No+One+Else  IRC meeting record]
  
−
5-     when you enter a chat room and you see a meeting is happening, if you must say somehting to someone, use their nick like:
+
Our sixth IRC meeting will on 20:00-21:00 10 Mar.(Wednesday) [http://fardad.com/irclogs/Default.aspx?co=0&log=%23seneca-oop344.freenode.20100310&u1=All+Users&u2=No+One+Else&u3=No+One+Else&u4=No+One+Else IRC meeting record]
  
−
6-     people with @ in front of their name are moderators. They can kick you out of a chat room if you misbehave, or even ban you from the chat room for ever.
+
Our seventh IRC meeting will on 20:00-21:00 12 Mar.(Friday)
  
−
This is the major difference between IRC and kindergarten chat programs like MSN
+
Our eight IRC meeting will on 20:00-21:00 17 Mar.(Wednesday)
  
−
7-     if you are to meet few of your team members for a meeting in a chat room, say in #seneca
+
Our next IRC meeting will on 21:00-22:00 29 Mar.(Monday)
  
−
and you find out it is very crowded and busy... you can create temporary chat rooms by simply /join #A_NonExistantRoomName
+
Assignment 1 direct link [[BIOF 20101 (AS1) - OOP344| click here]]
  
−
8-      if you are talking about a program you wrote and want to show it to your friends
+
'''To all the team member!'''(No News)
  
−
use the pastebin.ca website to copy the text and post it, then copy the url and put pass the usl
+
Please "Check out" with svn://zenit.senecac.on.ca/oop344_101rep2  and verify your user name and password which informed in Fardad's email
  
−
also, if you have a very long URL and want to give it to others, do this: use tinyurl.com to copy your url and make is small.... that is too long to be pasted here, so I put it in the tinyurl.com and in return it gave me : http://tinyurl.com/201027log when you click on the short url, tinyurl.com will redirct you to the long one :)
+
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![[A Team IRC meeting | Rules]]
  
 
== Team Coding 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.

Latest revision as of 16:32, 7 April 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 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 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
A Team - PRJ0.5 to do list
Seneca Username Function Complete status
wtong1 bfield.h bfield.cpp Done
kxu9 bfield.cpp blabel.cpp Done
ywang268 btext.h bframe.h bframe.cpp OpText.cpp Done
hmo6 bedit.h bedit.cpp - Done
syzhang4 blable.h blable.cpp Done
wfchen btext.h bframe.h bframe.cpp OpText.cpp Done
cxwang bedit.h bedit.cpp Done
lwang168 bform.h bform.cpp Done

Remember !!!!

We must hand in "TeamSelfMarking" sheet for every team member include yourself and you can download it in class note trunk\TeamSelfMarking!

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 eight IRC meeting will on 20:00-21:00 17 Mar.(Wednesday)

Our next IRC meeting will on 21:00-22:00 29 Mar.(Monday)

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.
Retrieved from "https://wiki.cdot.senecapolytechnic.ca/w/index.php?title=A_Team_-_OOP344&oldid=37727"