Page 27: Last Page (rubric)

You have made it to the end of the second workbook!

This workbook has introduced you to Transformations, a key concept in Computer Graphics. We explored them in 2D. In the future, we’ll explore using Transformations in 3D; this includes using transformations to map a 3D scene to the 2D space of the screen. What you’ve learned here will come back.

Here’s how Gemini summarized the workbook (I added the last point):

Here is a concise summary of the key takeaways for students, based on the workbook’s content:

The Big Idea: Manipulating the “Graph Paper” The most critical concept is that transformations (translation, rotation, scale) are best understood as moving the coordinate system itself - shifting, spinning, or stretching the “graph paper” - rather than moving individual points. This intuition is the foundation for understanding why the order of operations matters and how complex, articulated objects (like robots) are built by chaining these coordinate moves together.

Key Takeaways:

• Coordinate Systems: Always think about transformations as modifying the “current” coordinate system. For example, translate moves the origin of the grid you are about to draw on.
• Order Matters: Transformations are non-commutative. A rotate followed by a translate produces a different result than a translate followed by a rotate because each step alters the reference frame for the next.
• Hierarchical Modeling: Complex objects are built using parent-child relationships. A “child” part (like a propeller) inherits the coordinate transformations of its “parent” (the quadcopter body), allowing them to move together naturally.
• State Management: In Canvas, you must use save() and restore() to isolate transformations so that moving one object doesn’t accidentally move the next one you draw.
• The Math: Under the hood, these 2D affine operations are represented as 3x3 matrices using homogeneous coordinates, which allows translation to be treated as a linear operation.
• Retained Mode API: we saw SVG, a retained mode API. It represents the scene graph explicitly.

Hopefully, you got here by going through every page and completing the work on it. The boxes are the most significant component. Here is a list of all the boxes, and whether or not you checked the checkbox. This way you can keep track of what you’ve completed. We will not look at these checks: they are for student convenience.

Here is a list of all the box rubric items in this workbook. You should make sure that you have completed all the items you intend to do. They are checked off if you checked the checkbox. You should only check the boxes that you have completed.

Handing things in…

Please check one more time that your NetID is correct:

Please tell us how you used AI tools in doing this workbook. Remember, disclosing AI usage is part of the class policy on AI usage.

In the following type-ins you should give attributions for any included work. For example, if you took an image or model from the web.

Check that the local store is correctly written (and the json file moved to the correct location) - it probably changed after you filled in the AI Note and Attributions.

If you’ve done that, you are ready to submit your workbook!

Make sure to commit and push your work. Then press the “Submit” button to tell us that your assignment is ready for grading.

After pressing the Submit button, the File Status may say “The json file does not match the local store” because the submission time is now in the local store. You don’t have to worry about that.

If you’ve made something you are particularly proud of, we encourage you to submit it for the gallery.

Congratulations! You’ve completed Workbook 2.