3.3-clock-Daniel Condit

[DanielCondit]

Deliverables

• [x] A visible build on GH Pages: with a link to the final build in your issue
• [x] A Pull Request link in your issues

  Requirements

• [x] Time should update every second on the clock
• [x] The clock should modify the colors of the background based on the time
• [x] Make it Tick
  • [x] Create and commit a new file in called main.js
  • [x] Created and committed and RAN main.js
  • [x] console.log the current time on page load.
  • [x] console.log the current time every second.
  • [x] Display the current time every second
  • [x] Display the current time, padded with zeros to be exactly two digits long, every second.
  • [x] console.log the percentage of a minute that the current seconds represents (e.g., if 30 seconds have elapsed, console.log 0.5)
  • [x] Using the percent above, dynamically modify the length of the timer bar.
  • [x] console.log a hexidecimal color that is based on the current second every second.
  • [x] Dynamically update the background color of the page using javascript.
  • [x] This can be just a toggle for now
• [ ] Hard Mode
  • [ ] Show the percentage of a second under the current time
  • [ ] Make the time show up in hex every other second instead of human readable: Check this out radix should = 16
  • [ ] Update your background to a color using hlsa

    Normal Mode

Recreate this clock driven by CSS and JS:

[DanielCondit]

https://github.com/DanielCondit/3.3-clock/pull/1

http://danielcondit.github.io/3.3-clock/

[rtablada]

@DanielCondit looks like on GH Pages I'm still getting a blank screen but it seem like your develop branch is further ahead.

I know you are sweeping through your assignments, so ping me when this is ready for review again.

[rtablada]

@DanielCondit let's look at this, we shouldn't be using JS in our HTML files especially setting onload, onclick, etc on elements. This is an old anti pattern and becomes very hard to maintain. Also not seeing any change of colors.

[DanielCondit]

Complete.