Bishop Zareh
Bishop Zareh
There is a kind of strange interaction between the Frame.debug levels and the use of Frame.log here in perf. Frame.log needs re-thought-out, and it's use in perf should be considered.
performance.now() is a higher resolution timer. should be used when available. See: http://updates.html5rocks.com/2012/08/When-milliseconds-are-not-enough-performance-now
No reason not to include: https://gist.github.com/addyosmani/5528124
here is another Perf related library http://lafikl.github.io/perfBar/
and another one: https://github.com/dreamerslab/node.flow
Good tutorial about unit testing https://www.unboxedconsulting.com/blog/making-javascript-testing-in-the-browser-not-suck-with-sinon-js-part-1
yeah, Frame needs re-written to use RAF. Here are some references: http://paulirish.com/2011/requestanimationframe-for-smart-animating/ http://www.w3.org/TR/animation-timing/ http://hacks.mozilla.org/2011/08/animating-with-javascript-from-setinterval-to-requestanimationframe/
using requestAnimationFrame recursively (it's standard use) always pegs the computer at 100% CPU usage. 1. encase RAF in Frame 2. add a framerate limit to config options 3. re-write mrdoob's...
as does Q promise architecture: https://github.com/kriskowal/q And this article about Promises: https://gist.github.com/domenic/3889970
and https://github.com/kmalakoff/background