Bézier Clock(jackf.net) |
Bézier Clock(jackf.net) |
It looks like it uses linear interpolation between the different glyphs, which makes it look a bit jerky. The author might want to try a sinusoidal interpolation so that velocity reaches zero at the key frames and the whole thing thus spends more time dwelling on the legible parts of the animation and looks smoother.
animationRatio = ratio * ratio; // can also replace with sqrt(ratio)
Again, just makes it a little bit 'snappier' (remember you have to hit spacebar to turn on continual animation), and scales it so you can determine the numbers a bit more clear earlier in the cycle because of the scaling on (0.0, 1.0]. This is certainly a fun piece of code to play with.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)
However, for this Bézier clock, it would be more practical if the animation was finished before it had to change again, so that we could read the numbers.
[1]: https://play.google.com/store/apps/details?id=ch.bitspin.tim...
So pretty.
http://www.animaclock.com/viewfont?font=anifont4_bez&clean=1...
http://www.animaclock.com/viewfont?font=mrcl_kk_ghost&clean=...
edit: oops, RTFM devin
Edit: oops, three of us got here at the same time
Uncaught SecurityError: Failed to read the 'localStorage' property from 'Window': Access is denied for this document. processing.js:9503
Not sure why processing.js needs local storage to work.
[1]: http://p5js.org/
I'm curious about the code organization: it seems that processing.js contains both the application code for the clock as well as the libraries for interpreting the Processing code. Is that true? Is that the best organization? Would it not be better to have have a processing.js which is the interpreter/libraries and a bezier_clock.js?
Making the sources to the clock available here: http://jackf.net/bezier-clock/bezier_clock.pde
[0]: https://play.google.com/store/apps/details?id=ch.bitspin.tim...
public class MyWebViewActivity extends Activity {
@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
WebView webView = new WebView(this);
setContentView(webView);
webView.getSettings().setJavaScriptEnabled(true);
webView.loadUrl("file:///android_asset/index.html");
}
}edit: 2048 does indeed restore the game, but it should still work without a cookie.
But why is the site blocking the Ctrl+D keystroke? Don't they want to be bookmarked?
If you've got an extended clock (days, months, years, centuries, millennia), morphing could take a while.