v0.8 because of backwards incompatible change to event handler signatures
Tests: PhantomJS can now run our event tests, maybe something improved with the way we simulate the events
Bug: finding existing scopes for nodes was not correct if the scope had been replaced, such as it is when using repeating nodes
scope.$.get and scope.$.set behaviour changes to address bug reported by @snikch relating to child scopes and value functions

Change scope.$.get method to evaluate value functions, in this way it behaves more like accessing a snapshot. This actually matches the way that it has been used; in watchers and initialising repeats.

Change scope.$.set so that it looks for value functions in parents to call to "set" the value. This is important, as we will try to set the value in the scope during an update, which occurs if you toggle a form element, and if that value was driven by a value function in a parent, then we would set a local static value and then that value would shadow the value function in the parent.
Test: test the child contexts with value functions and update bug fix in the previous commit
Call scope.$.set to set back the results of a allAttributes and allProperties

If these are the result of a value function, then changing the object is not necessarily enough. We should call set and set the object back.
README: update for get and set changes
v0.8 minified files