CS 381 Fall 2012
Assignment 7
Assignment 7 is due at 5 p.m. Tuesday, December 11.
It is worth 20 points.
Procedures
E-mail
answers to the exercises below to
ggchappell@alaska.edu,
using the subject
“GA7”.
- Your answers should consist of the source code for the
web page and any associate program(s),
as required by Exercise A,
or a single archive file (ZIP?) containing these.
These should be attached to your e-mail message.
- Send only the above!
I do not want project files or executables.
I also do not want things I already have, like
glut.h.
- Be sure to include your name in your e-mail.
- I may not read your homework e-mail immediately.
If you wish to discuss the assignment (or anything else)
with me, send me a separate message with a different subject line.
Working in Pairs
This assignment may optionally be done in pairs.
If you work with someone else:
- Put both names in the submission e-mail and in the source code files.
- Cc: the submission e-mail to the other student,
so that I can send an acknowledgement to both.
- Under normal circumstances, both authors will receive the same grade.
Exercises (20 pts total)
Exercise A — Web Page with Canvas
Purpose
In this exercise, you will create a web page with
a canvas element containing
programatically generated graphics.
Instructions
Write an HTML5 web page
and associated program code
(most likely either JavaScript or Processing)
that meet the following requirements.
- Your web page must include at
least one canvas element that displays
graphical content
that is both
nontrivial
and
original.
- The content must change somehow:
either with time, or in response to user actions.
Notes
- Yes, this assignment is very open-ended.
- Your program code
may be included in your HTML file
or in a separate file;
do as you think best.
- I have
processing.js;
if you use it, you do not need to send me the source for the compiler.
- Most of the requirements for previous assignments
(OpenGL, rules for callbacks, etc.)
do not apply here.
- However, general
standards for code are as for
the first assignment
(must compile, readable, following conventions,
avoid extra output,
clear how program is used, not buggy-looking, give credit, etc.).