http://www.google.com/search?q=backbone+vs+knockout&aq=0&oq=backbone+vs&sugexp=chrome,mod=17&sourceid=chrome&client=ubuntu&channel=cs&ie=UTF-8
http://stackoverflow.com/questions/10320074/why-does-knockout-js-have-a-reputation-for-being-better-for-small-projects-back
http://lostechies.com/derickbailey/2011/11/22/backbone-vs-knockout/
http://smus.com/backbone-and-ember/
http://emberjs.com/
http://dev.hasenj.org/post/35572197519
http://www.google.com/search?q=knockout+js&aq=f&oq=knockout+js&sugexp=chrome,mod=17&sourceid=chrome&client=ubuntu&channel=cs&ie=UTF-8
http://knockoutjs.com/
http://knockoutjs.com/downloads/knockout-2.2.1.js
http://knockoutjs.com/documentation/text-binding.html
http://learn.knockoutjs.com/#/?tutorial=custombindings
http://www.google.com/search?q=javascript+change+css&aq=f&oq=javascript+change+css&sugexp=chrome,mod=17&sourceid=chrome&client=ubuntu&channel=cs&ie=UTF-8#hl=en&client=ubuntu&hs=kt2&tbo=d&channel=cs&sclient=psy-ab&q=javascript+manage+css&oq=javascript+manage+css&gs_l=serp.3...95121.99650.0.100416.21.16.0.5.5.0.338.3370.1j7j5j3.16.0.les%3B..0.0...1c.1.zDIDPB1pKRg&pbx=1&bav=on.2,or.r_gc.r_pw.r_qf.&bvm=bv.41248874,d.aWM&fp=ade360d3be480845&biw=1193&bih=944
http://stackoverflow.com/questions/566203/changing-css-values-with-javascript
http://stackoverflow.com/questions/2221160/how-to-change-a-css-class-style-through-javascript?rq=1
http://www.google.com/search?q=javascript+append+item+to+array&oq=javascript+append+item+to+array&sugexp=chrome,mod=17&sourceid=chrome&client=ubuntu&channel=cs&ie=UTF-8



jotting down notes on different libraries

revisting backbone...
has promise
but I'm leaning more toward knockout at this point.

I know that backbone doesn't enforce any one way to manage data on the client side and how that data is tied to the DOM. I can see where that could be a benefit for some developers with a stronger preference for one way or another. I don't have much preference at this point, and I would be happy to have something existing manage that for me.

http://www.google.com/search?q=backbone+js&aq=f&oq=backbone+js&sugexp=chrome,mod=17&sourceid=chrome&client=ubuntu&channel=cs&ie=UTF-8
http://backbonejs.org/
https://developer.mozilla.org/en-US/docs/JSON#toJSON()_method
http://underscorejs.org/#bind
http://lodash.com/
http://vimeo.com/44154599
http://www.google.com/search?q=javascript+_.&aq=f&oq=javascript+_.&sugexp=chrome,mod=17&sourceid=chrome&client=ubuntu&channel=cs&ie=UTF-8
http://stackoverflow.com/questions/5418279/what-does-means-here
http://backbonejs.org/#FAQ-why-backbone


keep coming back to python to javascript translators
but I think the real key is going to be to work natively with useful libraries created for DOM interaction.

http://jaredforsyth.com/projects/pjs/
https://github.com/jabapyth/PJs
http://chargen.blogspot.com/2011/08/survey-of-python-to-javascript.html

reading up


on this page there is a nice description of the single threaded nature of javascript:
http://javascript.info/tutorial/events-and-timing-depth


this snippet displays the latency on your browser for executing the next cycle:

var i = 0, diff = 0, d = new Date()

var timer = setTimeout(function() {
diff += new Date() - d
timer = setTimeout(arguments.callee, 0)
if (i++==1000) {
clearTimeout(timer)
alert("Resolution: "+diff/i)
}
d = new Date()
}, 0)


The key to the above, and many timing issues in javascript is:
setTimeout(function_call, 0)

also some considerations for making sure that changes to the DOM are re-rendered before continuing to the next display update.


http://www.google.com/webhp?sourceid=chrome-instant&ie=UTF-8#hl=en&tbo=d&output=search&sclient=psy-ab&q=browser%20event%20timing&oq=&gs_l=&pbx=1&fp=4ed87bf74c3b6306&bav=on.2,or.r_gc.r_pw.r_qf.&bvm=bv.41018144,d.aWc&biw=987&bih=887
http://www.w3.org/TR/workers/


looking at different python to javascript converters...
github.com/jabapyth/PJs looks promising...
just want something simple