WonderCode 20123 - OOP344

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

Project Marking Percentage

• due immediately

Group work:      40%        (25 <= xx <= 50)
Individual work: 60% +      (50 <= xx <= 75) 
-------------------------
Total           100%

Repository

• repo Github id: II-WonCod (https://github.com/Seneca-OOP344/II-WonCod.git)

Team Members

WonderCode

First Name	Last Name	Section	Seneca Id	Github ID	wiki id	IRC nick	Blog URL
Guiwen	Chen	B	gchen42	Github:guiwen	Guiwen Chen	chgw	Guiwen's Blog
Linpei	Fan	B	lfan9	Github:lilyfan	Linpei Fan	Lilyaj	Learning Path to Software Development
Hye Young (Rody)	Choi	B	hychoi6	Github:rodychoi	Hye Young Choi	RodyChoi	Happy Life
Diao Qiang	He	A	dqhe1	Github:diaoqianghe	Diao Qiang He	Antares	Diao Qiang He's Blog
Jie Ming (Jay)	Feng	B	jmfeng1	Github:jayfeng	Jie Ming Feng	jayfeng	Blue Jay C++

Issues and Status

0.2 Milestone (Due Fri 9th)

1. Add console class to project and test with cio_test (issue 1) (by Linpei Fan and reviewed by Guiwen Chen)
2. Create Mock-up classes

   Create the class files (header and cpp) with blank methods and make sure they compile

   1. CField Mock-up Class (issue 2.1) (by Guiwen Chen and reviewed by Linpei Fan)
   2. CLabel Mock-up Class (issue 2.2) (by Linpei Fan and reviewed by Rody Choi)
   3. CDialog Mock-up Class (issue 2.3) (by Rody Choi and reviewed by Diaoqiang He)
   4. CLineEdit Mock-up Class (issue 2.4) (by Diaoqiang He and reviewed by JieMing Feng)
   5. CButton Mock-up Class (issue 2.5) (by Jieming Feng and reviewed by Guiwen Chen)
   6. CValEdit Mock-up Class (issue 2.6) (by Guiwen Chen and reviewed by Lipei Fan)
   7. CCheckMark Mock-up Class (issue 2.7)(by Linpei Fan and reviewed by Rody Choi)
   8. CText
      1. Add Text Class to the project (issue 2.8.1) (by Rody Choi and reviewed by Diaoqiang He)
      2. CText Mock-up Class (issue 2.8.2) (by Diaoqiang He and reviewed by Jieming Feng)
   9. CCheckList Mock-up Class (issue 2.9) (by Jieming Feng and reviewed by Guiwen Chen)

0.X Milestone

• Assigned to: FULLNAME
• Code review by: FULLNAME
• Status:

  (being developed/pull request/being reviewed/pushed to master)

• comments:

Coding Rules

• Data members in any classes start with underscore(_);
• Use meaningfully variable name;
• Comment properly;
• Use 4 spaces for each indentation;
• Define each variable in a new line;
• Keep functions simple and clear;

Meetings

• latest will be on top

1. Branching in Github and Nov. 5: Meeting held in IRC. Discussed how to use GUI and command line to create branches, create issues and make pull requests.
2. Branching Again in Git and Nov. 8: Met in person in school. Discussed more details on previous topics.
3. Merging and Solve Merging Problems and Nov. 9: Audio conference in Skype. Discussed the problems on merging. There were some errors when merging branch back to master. It prompted that there were unmerged files and merge conflict. Explored those problem. Finally, all branches were merged to master by resetting it.

Discussions

• DH1109: Indentation! Plz use exactly 4 spaces for each indentation. Otherwise, when we open the codes in Github in the "master", they will look ugly. To set this up, go Visual C++ - Tools - Options - Text Editor - C/C++ - Tabs, set "Indenting" to "Smart", choose "Insert spaces", and set both "Tab size" and "Indent size" to 4. Or, go Notepad++ - Settings - Preferences - Language Menu/Tab Settings, set "Tab size" to 4 and check "Replace by space".
• DH1106-2: I am thinking about how to communicate effectively. I guess we have to narrow down to just 1 or 2 places to meet constantly, so that we could keep in tight touch during this project. I'll start with an email to you and hopefully we'll get to an agreement these days.
• DH1106-1: One suggestion -- can we always add a thread id in front of each discussion? As you see, it could start with the name initials and then the date. The benefit is that we could refer to the particular problem simply by using the thread id when we are discussing it in other places, e.g. the chatting room, the discussion board, the blog, the github, the class, the documentation.
• I am in trouble because I push the "fork" button. I think I changed the master...Can you anybody help me?? @.@ <-- I emailed Fardad to help me out. Sorry for that
• Does anyone know where methods _frame->draw() or draw() in void CFrame::refresh() comes from? I cannot find it in Bconsole or Console. In CFrame, there is a draw(int) method. But I am not sure if it calls draw(int). --> Hey Lily, if you click F12 on the draw() text, you can see the function's definition,(maybe you already know that) so I think _frame->draw() comes from CFrame::draw(). If you have other opinion, let me know. ^^