Aaron Craelius

See https://github.com/aaronc/freactive/issues/7

FYI in `0.2.0-SNAPSHOT` all node life-cycle callbacks have been moved to the attribute map itself (where other DOM attrs are stored). Currently supported life-cycle callbacks are `:node/on-attached` which takes a...

Sounds good. Would you want to make a pull request so you'll get credit? ;)

We could also try to capture vendor prefixes and make sure there's a performance timestamp (although I'm not really sure this part is necessary): https://gist.github.com/timhall/4078614

I think attachEvent might need the "on" prefix: http://stackoverflow.com/questions/2657182/correct-usage-of-addeventlistener-attachevent. I also intend to allow people to optionally plug-in goog.events or another handler system if they want a well tested event...

So I agree with what you're saying about precise timing. We could just try to pull in the vendor prefixes and if not, use the setTimeout with 16ms like Om.

Okay, sounds good. I think that polyfill looks pretty good so I'm going to go ahead and merge it.

Cool. How much is that gzipped? We can just have a separate namespace that calls set! on the listen! var - not very Clojure-like I know, but I think it's...

Is that your whole project? On Sunday, November 23, 2014, Ruslan Prokopchuk [email protected] wrote: > ul@cybercraft ~/S/f/bench> du * > 48K goog-frk.min.js.gz > 44K native-frk.min.js.gz > > delta is the...

So, I looks like freactive by itself isn't that heavyweight right now. On Sunday, November 23, 2014, Ruslan Prokopchuk wrote: > Hmmm... I'm already using goog.events for routing, so size...