61–70 of 73 posts
Earlier quoted context omitted.
Or change the motion curve so that it stays in the recognizable state for longer, like 90% of the time.
I'd suggest capping the animation duration. 90% of 10 hours still leaves an hour for the animation. If you've got an extended clock (days, months, years, centuries, millennia), morphing could take a while.
edit: 2048 does indeed restore the game, but it should still work without a cookie.
Earlier quoted context omitted.
The 4 actually becomes its true form at 40 (read the text below the clock), so what you were seeing was not 48 but rather 38.
Yes. Perhaps hitting the optimum form at 45 would be ideal. So 4 would start becoming clearer at 40 and then start degenerating after 45.
Why does this need a cookie to function? I block cookies by default and I get annoyed every time some site requires a cookie for something mundane like displaying the time or playing a game that doesn't even preserve state across browser sessions (like 2048) edit: 2048 does indeed restore the game, but it should still work without a cookie.
My crappy addition to clocks: http://myoldclock.appspot.com/ Did it in about 12 hours for a Google I/O competition 3 years ago. It's a countdown clock instead of a normal clock, but similar idea.
Nice animation. Something similar is JWZ's dali clock: http://www.jwz.org/xdaliclock/
My crappy addition to clocks: http://myoldclock.appspot.com/ Did it in about 12 hours for a Google I/O competition 3 years ago. It's a countdown clock instead of a normal clock, but similar idea.
I'll throw mine in too then – an "analog" clock drawn by 64 fast-moving LEDs: http://www.thisissurreal.com/shai/hologram/hologram.html (clock is at the bottom)
But why is the site blocking the Ctrl+D keystroke? Don't they want to be bookmarked?
Earlier quoted context omitted.
One trick I've noticed to make animations/transitions "snappier" and more natural is to use quadratic/square (power of 2) scaling. For fun I did it on this clock just saving it locally - you can do it by modifying line 140 of `bezier_clock.pde` to square the ratio instead of simply assign it: animationRatio = ratio * ratio; // can also replace with sqrt(ratio) Again, just makes it a little bit 'snappier' ( remember y…
I've updated it with quad, cubic and sinusoidal modes. They all look good. Only problem is that because it's no longer linear, the various points can change at different rates and thus create 'kinks' in the curve. When it's linear, the 'line points' and the associated 'control points' are always in a line locally tangential to the curve (don't know the proper terminology but hopefully you understand).