University of Waterloo
CS488/688 Fall 2017
Who Can Contribute to the Gallery?
You must be a past or present CS488/688 student.
Note that when you make a contribution, everyone on the
web can access and/or copy that information. So you should consider
every contribution as a release into the public domain. If
you want, you can place additional restrictions on use in your
documentation. If you feel especially paranoid,
you may also want to mark your image(s) with the
``annotate'' function in display to discourage
illicit copying and reuse without citation.
What Can I Contribute?
Naturally, images output by a renderer are nice, but screen grabs
of interactive applications are also quite welcome.
Both the unique scene from your raytracer (A4)
and the results of your projects are welcome.
The images don't have to be the result of an assignment.
We reserve the right to refuse a contribution if it is of
poor quality and/or takes too much disk space and/or is
exceptionally tasteless and/or has little to do with
Also, we obviously can't install documentation that makes it
trivial for later students to do the assignments. Source code
for part of an implementation of an assignment, for example,
would have to be refused. MPEG animations will be accepted if
short and well compressed.
Note that multiple images can also be contributed,
and we don't mind extensive
documentation if you can make it available in an online form (see
below). Basically, within a contribution weblet you can put anything,
should be at least one ``representative image'' which is an
entry point to your work.
How Do I Make a Contribution?
If you want to contribute something, please put together in a directory
- 1. A representative image (or images) in JPEG format.
- Name the image after your userid, i.e. userid.jpg.
If you have more than one image, use a number:
userid0.jpg, userid1.jpg, etc.
Note that a quality level of 85 may corrupt some
computer graphics images. Use 90 or even 95 if
you feel it's warranted.
- 2. A thumbnail image (or images) on the order of
100x100 in GIF format.
- Use display/convert to reduce
the number of colours and do good colour quantization, and properly antialias during reduction.
Use the same filenames as above, but use .gif
as a suffix. Try to keep as close as possible to 100x100,
or 10000 pixels if your source image is not square.
Smaller images are incomprehensible, but larger ones take too
long to download.
- 3. Some background information and documentation.
- This can range from a plain text
description to an HTML page. You may want to include the
Tcl script used to create the scene.
If you use an HTML "weblet"
with multiple pages, preceed each filename with your userid,
If you use HTML, you may include links to your images, just be
sure to label everything with your userid and use relative
- 4. A README file.
- This file should contain your full name
as you wish it to appear, the titles of (each of) your image(s),
and the entry point of your documentation, if you use
HTML documentation. Say whether multiple images all should
point to the same documentation, different documentation,
or different parts of the same documentation. The contents
of this file will be used for installation, but will not
be placed in the gallery.
Try to set things up so we can just plop everything in a directory and link
it into the gallery. If you don't know HTML, don't worry: a 1-paragraph
descriptive text passage is fine. Use a .txt suffix in this case.
and let us know where all this stuff is. We'll grab
it and email you when it's installed for posterity in the gallery.
Revision 1.4 by cs488 on 1997/08/16 00:20:39 (UTC).