Open main menu

CDOT Wiki β

OOP344 - 20101

Revision as of 09:47, 5 October 2009 by Fardad (talk | contribs)

OOP344 - OOP344 Student List - OOP344 Teams - OOP344 Assignment One

Please help make this page resourceful for all OOP344 students to use!

OOP344 -- Object Oriented Programming II Using C++

Subject Description and Course Outcomes

The Project

The project for this semester is a multiplatform text based, Text Editor.

The project is divided into 2 main parts.

Individual work

Done individually! Each student must complete and hand her/his own work, no collaboration permitted for this part.

The assignment can be found here.

Open Source

This part will be done collaboratively in groups of 4 - 8 students under a simulated open source model

  • Basic Encapsulating Classes (bec)
    This part is written in C++ and encapsulates the io routines into classes
  • The Text Editor
    this part is written in C++ and uses the bec classes to do full text edit.

Grading

To be completed

Resources

Examples

Examples and Notes done in class

Archives

Class notes, samples, tests, ... since 2001

OOP344 -- Weekly Schedule

Week 2 - Sep 13

To Do

Due date: Sep -17 - 2009 , 23:59 (11:59pm)

  • Add your name to the OOP344 Student List
  • Join the IRC by registering your nickname on freenode server and joining the #Seneca channel
  • Create a blog (if you don't already have one) and add your feed to Planet CDOT
  • Challenge: write this function without using any library functions; void GetInt(char *strint, int val);
    this function gets an integer value and converts it to a string ("strint")
  • Challenge: Modify io_display function to the shortest code possible. Get the source HERE.

Week 3 - Sep 20

To Do

  • Complete last week's "To Do"s.
  • Form the teams and add your team to the wiki
    • Teams with less than 4 members and more than 8 are not acceptable.
    • Merge or divide teams if necessary to adjust the number of team members.
    • Teams' member selection must be finalized by Oct 3rd.
    • Those without a team, join the teams with least number of members.
    • Select a team leader who is going to be the contact person for the team.
  • Challenge 3: using what we learned so far (logical operators, and pointers) write the io_display function in ONE line only(Due Sunday 23:59):
void io_display(const char *str, int row, int col, int len){
   yada yada yada;
}

Week 4 - Sep 27

Topics for this week

  • #undef, casting, unsigned variables, multi-dimensional arrays and their pointer notation
  • pointers to functions, pointers to pointers to pointers to...
  • to be completed....

To Do

  • Complete last week's "To Do"s.
  • Finalize Teams by end of the week (Sat Oct 3rd)
    • If your team has less than 4 members, either try to merge your team to another team or break up your team and join other teams.
    • After finalizing your members make sure your team wiki page is created and inculdes the list of all team members and their information
    • Select and identify a first and second contact person for your group.

Week 5 - Oct 04

  • Complete last week's "To Do"s, if not done already!
  • Read first four chapters of the SVN book.
  • download SVN and install it on you PC from subversion.tigris.org
    • windows: Tortoise SVN
    • Linux (Fedora: yum install subversion)
    • MAC: already in Apple's Developer Tools