CSCI 441 - Computer Graphics

This assignment is due by August 30, 2018 11:59pm.

You're quite humbled to have been invitied to compete in the Tuatha Dé Danann Cup. You felt your recent times were not fast enough. Perhaps that's why your times have been increasing - you've been too focused on finding the best line of the track and not focused enough on just driving fast. If you are going to compete at Findias Speedway, you're going to need to tune your vehicle.

After you've completely disassembled the engine and reassembled it, you realize you don't know what you're doing - you have parts left over. You decide to leave modifying the car to your little cloaked friends. You watch as they once again dissamble the engine, must quicker than you originally did, until one of the crew pushes you out of the garage.

Before you can even turn around to see what's going on, you hear the door close behind you. Now you don't know what to do. How can you prepare for the races if you're not practicing?

The answer comes to you in the sound of clip clop clip clop. A messenger approaches you on a horse.

Greetings. I come with additional information regarding the Tuatha Dé Danann Cup. Before you start racing, we need to promote you. Please provide us a banner to adorn your pit stall. Each stall is 700 troighid long and 150 ordlach tall. In addition to everyone expecting you at the track, your banner will then be used to merchandise (such as on a t-shirt, coloring book, lunch box, breakfast cereal, flamethrower, doll). Please provide us with a design in nine oídhche. Here are further specifications.

You take the letter from the messenger and begin reading.

For this assignment, create an OpenGL / GLFW program that displays your hero's name and optionally a crest of your choosing to represent your track. Create a window that matches the size of the pit stop for your vehicle - that is, make the window 700 pixels wide by 150 pixels tall. Do not use any predefined fonts, instead draw each letter using a filled OpenGL polygon. Each letter should be constructed using OpenGL primitives ( GL_TRIANGLES , GL_TRIANGLE_FAN , etc. Do not use GL_POLYGON) and a set of manually created vertices. The vertices can be hardcoded in the program or read from a file if you are feeling particularly fancy. Be sure to try out the different primitives that are available. There are many different types, so do not be afraid to experiment with all of them within your banner.

In addition, more than one color must be used when drawing the letters. The letters need to be translated, scaled, and rotated by calling glm::translate(), glm::scale(), & glm::rotate() appropriately and respectively. Make sure at least one letter is used in conjuction with each transformation.

It would be good practice to begin encapsulating data within subroutines and functions (for instance, have a function drawLetterC() that handles drawing the letter C and a separate function drawLetterS() that handles drawing the letter S). While a simple example right now, this will become much more important later on when we discuss model hierarchy and object-oriented program design.

Once your sign is created, your hero will proudly display their sign on their hero page, accessible from the leaderboard.

Feeling a sense of purpose once again, or at least eager to kill time until your engine is put back together, you begin putting together your banner.

In addition to making a sign, create a webpage that showcases your work. There is a template available for your website. If you wish to use it, download this .tar.gz file (or .zip file) and extract it. It will create a www/ directory with the stylesheet from the course webpage, which you can use if you like. You'll be adding to it for each homework assignment, with a screenshot or screenshots of your work, a short description of the assignment, and the opportunity to talk about any neat implementation details if you so choose. The websites are a way for you to keep track of the projects you've made over the course of the semester, but you should also aim to make the descriptions accessible to people outside of the course as a way to share and showcase your coursework. Hopefully you can use this as a portfolio along with your resumé.

Inside the www/ directory, there is an images/ folder. Place any screenshots and other images into this folder.

If you're not familiar with HTML, don't worry; the template shouldn't do anything crazy - a <br> signifies a newline, the <img> tag places an image. There are plenty of tutorials available for HTML if you want to add tables, change font styles, or play with the formatting. There are some comments in the template file to help you out as well.

If you choose to use the template or your own template, be sure to name the webpage <HeroName>.html where <HeroName> is the name of your hero without spaces in CamelCase. (For example, my submission would look like ElvishScout.html .) If you have a question about what you should name your file, please ask the instructor and he will confirm how your name should look.

With this and all future assignments, you are expeced to appropriately document your code. This includes writing comments in your source code - remember that your comments should explain what a piece of code is supposed to do and why; don't just re-write what the code says in plain English. Comments serve the dual purpose of explaining your code to someone unfamiliar with it and assisting in debugging. If you know what a piece of code is supposed to be doing, you can figure out where it's going awry more easily. (Interestingly enough, this code review of Doom 3's source code says the exact opposite - well written code should require no comments. Well, we don't work at id so we're going to comment.)

Proper documentation also means including a README.txt file with your submission. In your submission folder, always include a file called README.txt that lists:

• Your Name / HeroName
• Homework Number / Project Title
• A brief, high level description of what the program is / does
• A usage section, explaining how to run the program, which keys perform which actions, etc.
• Instructions on compiling your code
• Notes about bugs, implementation details, etc. if necessary
• How long did this assignment take you?
• How much did the lab help you for this assignment? 1-10 (1 - did not help at all, 10 - this was exactly the same as the lab)
• How fun was this assignment? 1-10 (1 - discontinue this assignment, 10 - I wish I had more time to make it even better!)

Your submission will be graded according to the following rubric.

Please update your Makefile so it produces an executable with the name a1. When you are completed with the assignment, zip together your source code, Makefile, and README.txt into a folder named src/ plus include your www/ folder. Name the zip file, HeroName_A1.zip . Upload this file to Canvas under A1. The structure of your submission should look as follows:

• HeroName_A1.zip
  • src/
    • README.txt
    • Makefile
    • main.cpp
    • all_additional_code
  • www/
    • images/
      • all_images
    • HeroName.html
    • all_additional_files

This assignment is due by August 30, 2018 11:59pm.