Team P - OOP344 20133

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

UGO

Team Members

UGO (Team P)

First Name	Last Name	Section	Seneca Id	wiki id	IRC nick	Blog URL
Ruojia	Chen	B	rchen50	Ruojia Chen	avoin	Ruojia's Blog
Yan	Song	A	ysong55	Yan Song	puerile	Sophomoric OOP344ing
Yuzhi	Xing	A	yxing5	maichaelxing	michaelxing
Shreyas	Patel	B	spatel221	Shreyas Patel	Dean_Winchester	OO Programming

Repository

• GitHub Project Repo for Team P (Sign-in required)

Master Branch Status

• Merged by Yan Song, puerile : follow-up merging
• Merged by Shreyas Patel, Dean_Winchester: initial setting up

Project Marking Percentage

• due right after study break

Group work: XX% (25 <= xx <= 50) Individual work: XX% + (50 <= xx <= 75)

---

Total 100%

Coding Style and Standards

• No Tab Character allowed. (replace tabs with spaces)
• Each object must have its own type:

int a;
int b;
CDialog D;

• Indent two spaces at a time.

Tasks

Release 0.3 Task Assignment

r0.3-1 

Ruojia, CLineEdit, in progress

r0.3-2 

Yuzhi, CLabel, in progress

r0.3-3 

Shreyas and Yan, CDialog, in progress

Release 0.2 Task Assignment

r0.2-1 

Shreyas, initial testing and merging, done

r0.2-2 

Rest of team, follow-up updating and merging, ...

Meetings

• latest will be on top

topic, date

date

Discussion

---

Shreyas

• I need your help with warning guys i fixed one of them however, the warnings about conversion from 'int' to 'char', possible loss of data are because of (str[*strOffset+*curPosition] = key;)<-this line.I would appreciate is anyone can comes up with an idea to solve it. [It's safe to cast key to char this way: (char) key (C way) or char(key) (C++ way), because we're working in ASCII.]
• About rest of the warnings I found this link which somewhat explains the problem.
• http://stackoverflow.com/questions/4001736/what-with-the-thousands-of-warnings-in-standard-headers-in-msvc-wall