Open main menu

CDOT Wiki β

Changes

A Team - OOP344

2,902 bytes added, 17:32, 7 April 2010
TO DO LIST
! 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 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 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 ywang268 || [[Special:Contributions/lush | Contributions]] ||
|-
| Mo || Hsiu-Mei || [mailto:hmo6@learn.senecac.on.ca hmo6] || A || [http://hmo6.blogspot.com/ Blog] || hmo6 || not yet 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 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 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 cxwang || [[Special:Contributions/cxatseneca | Contributions]] ||
|-
| Wang || Liang || [mailto:lwang168@learn.senecac.on.ca lwang168] || A || [http://lwang168.blogspot.com/ Blog] || lwang168 || not yet 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@learn.senecac.on.ca,lwang168@learn.senecac.on.ca Email to this team]
== SVN Account ==
<big>
oop344_101rep2
 
</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 ==
Our first IRC meeting will on 20:00-22:00 27 janJan.(wednesdayWednesday)[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]]
== Our second IRC first meeting will on 20:00-22:00 6 Feb.(Saturday) [http://fardad.com/irclogs/Default.aspx?co=0&log= Normal 0 false false false EN%23seneca-US oop344.freenode.20100206&u1=All+Users&u2=No+One+Else&u3=No+One+Else&u4=No+One+Else IRC meeting record] ZH-CN X-NONE[[A Team IRC meeting | Notes for meeting]]
1Our third IRC meeting will on 20:00-21:00 10 Feb.(Wednesday) [http://fardad.com/irclogs/Default.aspx?co=0&log=%23seneca- First of all, understand that oop344.freenode.20100210&u1=All+Users&u2=No+One+Else&u3=No+One+Else&u4=No+One+Else IRC meetings and chats are much slower than talking so be patientmeeting record]
2Our fourth IRC meeting will on 19:00- IRC in nature is a very casual environment, so don't be surprised to see casual talk like 21:00 3 Mar.(Wednesday) [http: wassssssup!!!!!!! But in at the same time, make sure not to cross the line by used bad and impolite words//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 (no "F" words IRC meeting record] [[A Team IRC meeting | Notes for example) meeting]]
3Our fifth IRC meeting will on 20:00-21:00 6 Mar.(Saturday) [http://fardad.com/irclogs/Default.aspx?co=0&log=%23seneca- Since visual contact is not possible, every now and the drop a word to show the oop344.freenode.20100306&u1=All+Users&u2=No+One+Else&u3=No+One+Else&u4=No+One+Else IRC meeting holder you are there ok?record]
4Our sixth IRC meeting will on 20:00-21:00 10 Mar.(Wednesday) [http://fardad.com/irclogs/Default.aspx?co=0&log=%23seneca- when in a oop344.freenode.20100310&u1=All+Users&u2=No+One+Else&u3=No+One+Else&u4=No+One+Else IRC meeting being funny with one or two smart thing to say, it ok, but again, DO NOT over do itrecord]
5Our seventh IRC meeting will on 20:00- when you enter a chat room and you see a meeting is happening, if you must say somehting to someone, use their nick like21:00 12 Mar.(Friday)
6Our eight IRC meeting will on 20:00- 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 ever21:00 17 Mar.(Wednesday)
This is the major difference between Our next IRC and kindergarten chat programs like MSNmeeting will on 21:00-22:00 29 Mar.(Monday)
7Assignment 1 direct link [[BIOF 20101 (AS1) - if you are to meet few of your team members for a meeting in a chat room, say in #senecaOOP344| click here]]
and you find out it is very crowded and busy... you can create temporary chat rooms by simply /join #A_NonExistantRoomName'''To all the team member!'''(No News)
8- if you are talking about a program you wrote Please "Check out" with svn://zenit.senecac.on.ca/oop344_101rep2 and want to show it to verify your friendsuser name and password which informed in Fardad's email
use Please create your own working folder with your svn ID in the pastebin.ca website to copy the text and post itbranches, then copy the url and put pass create a text file with your svn ID in the usltrunk![[A Team IRC meeting | Rules]]
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 :)== 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.
1
edit