Implement a DOM tree tracker to be used as the basis for virtual DOM diffing. DOM diffing will be compartmentalized based on tree (the whole document won't be diffed).

• Consider using MutationObserver for invalidating tree if the performance is there.

• All DOM changes must run through SquidElement or SquidJS functions, changes outside will trigger mutation observer and remove elements from tree.

A function that generates a function to initialize a DOM element from a model and and template. It also provides a framework for UI events.

What type of component behavior? should we allow UI events to change DOM inside component (dirty) or force UI events to trigger changes to outside state, and outside state changes are then used for re-renders.

May need Redux style state reducer tracking or Clojure style immutability. (Undo)

Implement Lazy.js/Immutable.js style sequences as the collection types used and returned by SquidJS functions.

Everything as/is a Sequence.

Auto-convert Node/Element/HTMLElement and their derived types to SquidElements.

• Who should track changes? Sequence or SquidElement?
• Should SquidElement lazily create virtual-dom object?
• Should Sequence call virtual DOM diff on each element for a Render or grab all SquidElements and pass them at once?
• What should peeking the element do? create virtual DOM representation at that point? Peek the actual element?

A Sequence needs to be aware that is operating on multiple elements, and apply those changes in a single requestAnimationFrame when Render is called.