OOP344 - 20101

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

• Please visit the School Of Computer Studies website for the detailed description of the subject

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.

• Console Input Output Library (ciol)
  • Basic Console Input Output (io):
    This part is written in C language. It is responsible for handling basic input output features needed to interact with the console
  • Line and Selection Editor:
    This part is written in C Language and only uses bcio routines, to interact with the console.
    • Line Editor
      This is responsible for making a full edit on a single line of text and also provide basis for a multi-line text editor.
    • Selection Editor
      It provides means (A Checkbox) to create selection lists or Yes/No queries.

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

• How To edit Wiki pages
• Subversion (SVN)
• Mercurial Version Control
• Mac Lab Available in 2108 as well as in the Computing Commons*

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.