Successfully testing ControlNode internals and API
experimental changes to Route and Export onload. Now taking direct requests to routes on load, as opposed to only attempting route resolution onhashchange. There's logic to determine the target of the route template and then checks if the targeted node has a apl-default property. if so clear the apl-default proerty. Without this modification, Compile.compile() will see the apl-default value on the node and spawn a compilation thread to inject the partial located at the value of apl-default into the node, thereby clobbering the partial that was already loaded: in this case the partial pointed to by the route definition.
Templar page loading and routes, now works for IE. I haven't tested it for interpolation but it's a good start on cross browser compatibility.
Compilation now working in IE9. Had to move export to the end of dep chain. this is b/c IE9 won't call window.onload and workarounds are insufficient. The solution for now is to put export in IEF and put it last. This solution is ultimately inadequate as well as Export would have to be placed after any dependent code - an unrealistic burden to clients IMO. Anyways, the goal at this point is to get the product IE compliant so that fix will ultimately have to wait..... until the next commit.
rearranged ordering of Model classes so limit().to() could make use of update() and update the page on limit.
Model.limit now updates automatically and a minor change to filter that allows things to work right with IE9
Export now loaded last. Couldn't rely on window.onload b/c it's unsupported in <=IE9. Using structureJS.done() to execute the contents of export. Compile.js has a change that allows controls to be loaded correctly.
switched input handler to onkeyup as opposed to oninput b/c oninput doesn't fire when delete key is pressed. solution works cleanly in both IE and webkit browsers
moved getDataAttribute from Util to DOM. Also fixed hashchange bug
fixed double binding problem caused by immediately executing late bound handlers from ControlNode.listen. Calling late bounds immediately b/c during testing the handlers are bound after interpolation is finished (when the late bounds are typically fired). The solution now is to test if control nodes exist, and based on this we either fire or bind to interp_done system event.
minor, scope-related change. handler now doesn't use it's parent context's resolvedRoute variable.