CS 467 - Project One: Timepiece

Due: 03/17/2023

Objective

For your first project, I would like you to visualize time.

Requirements:

• You can work in any granularity of time that you like, but it is important that your piece shows the time now. You can include a sense of history or other aspects, but some element must be something that could be interpreted as now.
• You may not use any text or anything that could be interpreted as text. Quantities, however, are fine.
• Your piece doesn't need to be readable to someone who randomly encounters it, but it must be interpretable to someone who knows how to read it. It is okay if this is a proportional thing -- it is more important to know that we are half way or completely through a minute than it is to know that we are at second 24.

Getting Started

1. Click the GitHub classroom link
2. Clone the repository GitHub classroom creates to your local computer (in your shell, type git clone and the name of the repository)

Details

I have included some code in the skeleton that prints out a collection of date and time values to the console. You are not restricted to this set, nor are you required to use them all.

Note that not all of these values are straightforward to interpret (e.g., January is month 0). I encourage you to read the documentation.

I encourage you to remove the console.log once you understand it. Writing out to the console is very slow and is not recommended in animation loops once you are done debugging.

Reflection

I would like you to write a brief reflection in the README file.

There is a section set aside for you to describe your timepiece and tell us how to "read" it, please use it.

The second section is where I would like you to answer the following questions:

• Do you think it is complete?
• If not, what is left to go and how are you going to address it?
• What was the hardest part?
• What, if anything, have you gained by completing this project?

Revisions

If you revise your submission, please add a dated addition to your reflection that describes what has been changed.

Submitting

When you are ready to submit,

• commit your changes to your git repository (git add and git commit -- see the guide for details)
• push your changes to GitHub (git push). For 312 alums, don't worry about PRs -- a straight commit is fine

Important: it is tempting to treat all of our deadlines as "loose" -- this is a dangerous path! Get something done by the deadline and submit. You can always go back to it, and you will get the benefit of my feedback. Just make sure that your reflection acknowledges that it isn't complete.