adding Controller.replace back in w/ tests!
fixing "export" bug in IE by renaming "export" to "exp0rt". way cooler anyway.
another IE fix: trailing comma in Filtercollection options!
another ie fix?
oops, fixing for remove_event as well (IE!)
more IE provisions in adapter
fixing addClass assumption
getting close on IE stuff... (thanks Mohsen!)
converting typeOf call to typeof
updates to eq
eq updates, with extensive eq tests
rebuild
use moo for now when testing (ie shit)
Composer.eq test: disbale console logging, add a few more false tests, re-enable reverse value testing in `run`. looking/working good.
fix jasmine to use Moo if querySelector doesnt exist. this is now Composers mantra: if youre using ie <= 9, you must include moo. sorry.
adding new history html4+html4+native
Large number of fixes

Went through the test in IE compatibility mode. Was horrified. Special
thanks to Mohsen for spurring me to do this.

- controller: were actually working fine, but had to update tests to
  look for parent nodes with an empty tagName attr, vs null parentNodes.
  in other words, the nodes are being taken out of hte DOM fine, but in
  IE the el.parentNode still points to a node (with tagName ==
  undefined) when it's removed.
- router: fixed a large number of issues. it's required to use the
  html4+html5+native adapter for History.js. also, fixed a number of
  places where composer wasn't looking for hashbang URLs (a lot of this
  was ripped out in the 1.0 conversion). fixed now. also had to hack the
  router to make hashbang routing synchronous (MUST use Router.route for
  this to work!!).
- filtercollection:
    arr = [1,2,3];
    arr.splice(1)
  *doesn't work* in IE. you have to do
    arr = [1,2,3];
    arr.splice(1, arr.length);
  which i guess is part of the spec. who knew. thank god for tests.

that about covers it. as far as the tests are concerned, IE <= 9 should
be a viable option IF IT HAS MOO LOADED. if you don't have Moo and
you're using IE, god help you (I sure won't).
IE6-ifying jasmine a bit more
ie6 test fix (Composer.eq). i guess [undefined] == ??? in ie6.
adding playground for composer stuff, should make one-off tests that dont fit into the test specs a bit easier