Start on Blaze.View
Test destroyed callback better

We weren’t actually testing that templates removed by control flow (like #each) get their destroyed callback called.

This test should make it to devel regardless of the fate of this branch.
parentView and onCreated / onDestroyed
Attempts at proper teardown
Rename Removal -> Teardown in DOMBackend
Teardown and callbacks for Views
Better cleanup accuracy

Recurse into nested views
Materialized callback

It should be pretty easy now to write #each in the form of a View.
ReactiveVar, View kinds, new #with
Make templates use Blaze.Views (break the world)

The path forward is to start with an empty app and get basic template tags working again, then finish rewriting the builtins (with/if/unless/each).
Make Blaze.View not require `new`
Make inclusions work in Blaze.View world
Break out Blaze.DOMMaterializer into own file
Support HTMLification

Breaks webapp_server pretty hard
Introduce OLDSTYLE flag to not break webapp

Making webapp_server work requires #if and #each that work with toHTML.  Don’t want to have to write that code just to be able to run client code again.
Implement lookup, more builtins

Move lookup to templates, not views!
Fix #with; set current view on autorun
Capitalize something
Tweaks to view kinds
Correctly null out template{Content,Else}Block