Asg 3: Read in (parse) and output a simple A|W object

Objectives

Assignment

1. In the inputCube() function, read in the data for the verteces and faces as they are encountered. The program should contain two global lists:
   • std::vector<point_t *> points a list of vertices,
   • std::vector<face_t *> faces a list of faces, and
   • std::string group an unused string to store the group designation
2. Create a face_t object that will be used to store the integer vertex indeces that index into the object's vertex list, basically a list of integers. The face_t object contains the following data objects:
   • std::vector<int> vin a list of integers
   The interface and implementation for this object should be provided in separate header face.h and implementation face.cpp files.

Details

1. Write an outputCube() function that outputs the list of points, the group string, and the list of faces.
2. When you write cout << points[i], the point should use the operator<< to output its list of coordinates.
3. When you write cout << faces[i], the face should use the operator<< to output its list of vertex indices.

Hints

1. Notice that the indices stored in the data file number from 1..n whereas C/C++ lists, including the std::vector, are indexed 0..n-1.
2. One of two trickiest parts of this assignment is the file parsing. You should look over previous code for reading the point_t object and follow that pattern. This time, when looping through the input, you will have to decide what is being read in: a point_t object, a face_t object, or the std::string object. Each of these is identified by the leading character, i.e., v, f, or g, respectively. Therefore, your parsing loop should read in a single character and then switch on that character to decide what to read in, e.g., with std::istream& s,

     while( s.get(c) && !s.eof() ) {
       switch(c) {
         case 'v':
           // read in vertex_t object
         break;
         case 'g':
           // read in group string
         break;
         case 'f':
           // read in face_t object
         break;
     }
   	

3. See Assignment 02 for how to print out pointers to coordinates (recall the (*the_points[i])[0] syntax).

Input

1. The cube-ccw.obj file used to test the above program is:

   v 1.0 1.0 1.0
   v 1.0 1.0 -1.0
   v 1.0 -1.0 1.0
   v 1.0 -1.0 -1.0
   v -1.0 1.0 1.0
   v -1.0 1.0 -1.0
   v -1.0 -1.0 1.0
   v -1.0 -1.0 -1.0
   g cube
   f 1 5 7 3
   f 2 1 3 4
   f 5 6 8 7
   f 6 2 4 8
   f 2 6 5 1
   f 8 4 3 7
   	

2. An object is represented by a list of vertices, basically a list of 3D points similar to what was used previously to display a plane.
3. Each vertex is now used in a list of faces (polygons) that define the spatial boundary of the object. For a cube, there are 6 quadrilaterals.
4. Note that, in general, you cannot assume that all objects are composed of quads; they could be composed on n-sided faces, or polygons. You cannot therefore assume that each face will have 4 indices into the vertex list. There will be at least 3 and at most n where n is unknown. For this reason we use the STL std::vector containers, which keep track of the size of the list.

Output

1. If you can parse the cube, then you should be able to parse any of the .obj files below.

2. See also:
   • 82porsch.obj
   • 83cama~1.obj
   • aheart1l.obj
   • al.obj
   • bpunkh1l.obj
   • bronny1h.obj
   • dart.obj
   • deathstr.obj
   • galleon.obj
   • mystery.obj
   • sword.obj
   • syringe.obj
   • warbird.obj

Turn in

1. A README file containing
   1. Course id--section no
   2. Name
   3. Brief solution description (e.g., program design, description of algorithm, etc., however appropriate).
   4. Lessons learned, identified interesting features of your program
   5. Any special usage instructions
2. Makefile
3. source code (.h headers and .cpp source)
4. object code (do a make clean before tar)

How to hand in

Grading scheme