Live data from Hacker News

The Colour Clock

thecolourclock.co.uk

31–40 of 95 posts

Re: The Colour Clock

#31
post #15

Awesome idea. I took some time to rewrite in HTML5: http://brisy.info/colors/ Though the colours I'm getting are different. I wonder why.

Honest question - what is the HTML5 part in here (as opposed to I rewrote it in HTML+CSS+JS)?

Even though the implementation above doesn't use any HTML5-specific features, the term is becoming a synonym for Dynamic HTML.

Re: The Colour Clock

#32
A shame that the fastest-moving value is placed in the portion of the spectrum where we have the least colour sensitivity. I'd have put hours in blue, myself. If I'd thought of it.

Re: The Colour Clock

#33
post #15

Awesome idea. I took some time to rewrite in HTML5: http://brisy.info/colors/ Though the colours I'm getting are different. I wonder why.

I appreciate the pointlessness of being yet-another recreator, but hey, why not: http://davidlynch.org/toys/colorclock/ :D

My quirk is that you can stick a fragment on the end to change the mapping of time to hex. e.g. http://davidlynch.org/toys/colorclock/#smh is seconds=red, minutes=green, hours=blue.

Re: The Colour Clock

#34
post #15

Awesome idea. I took some time to rewrite in HTML5: http://brisy.info/colors/ Though the colours I'm getting are different. I wonder why.

Here's a version that cycles through the colors continuously (without jumps). Now the numbers do not directly corespond to the color code anymore (they alternate going up-down). Also you can multiply by 256, as the maximum is not reached for any of the values.

I uploaded it here: http://lkozma.net/colorclock/

  d     = t.getTime()/(1000 * 60 * 60 * 24),

  ...

  body.animate({"background-color":
                 "rgb(" + 
		  (((d%2)==1) ? parseInt((h / 24) * 256) : (255-parseInt((h / 24) * 256))) + "," +
                  (((h%2)==1) ? parseInt((m / 60) * 256) : (255-parseInt((m / 60) * 256))) + "," +
                  (((m%2)==1) ? parseInt((s / 60) * 256) : (255-parseInt((s / 60) * 256))) + ")"});
  };

Re: The Colour Clock

#35
post #22
post #15

Awesome idea. I took some time to rewrite in HTML5: http://brisy.info/colors/ Though the colours I'm getting are different. I wonder why.

Haha, I just did the same thing: http://nerdlife.net/colorclock.html

Small bug: Single digit hex codes are showing without the leading zero - it's probably affecting the colors as well.

Re: The Colour Clock

#36
post #22
post #15

Awesome idea. I took some time to rewrite in HTML5: http://brisy.info/colors/ Though the colours I'm getting are different. I wonder why.

Haha, I just did the same thing: http://nerdlife.net/colorclock.html

[deleted]

Re: The Colour Clock

#37

A shame that the fastest-moving value is placed in the portion of the spectrum where we have the least colour sensitivity. I'd have put hours in blue, myself. If I'd thought of it.

I'm quite sure there are much more mappings from hh:mm:ss -> rgb which would be even more interesting or even practical. For sure the internet will iterate on this idea in just a few seconds :)

Re: The Colour Clock

#38

The switch from 22:59 to 23:00 was stunning. I can't wait for the switch at midnight (#FFFFFF -> #000000).

I missed it. It basically goes from white (well, very pale cyan) to bright red, right?

#FFFFFF to #000000 would be white to black.

Re: The Colour Clock

#39

A shame that the fastest-moving value is placed in the portion of the spectrum where we have the least colour sensitivity. I'd have put hours in blue, myself. If I'd thought of it.

http://davidlynch.org/toys/colorclock/#hms http://davidlynch.org/toys/colorclock/#smh http://davidlynch.org/toys/colorclock/#mhs

Or any other order, really.

Post reply on HN