74 files changed, 1511 insertions, 1346 deletions

diff --git a/node_modules/montage/CHANGES.md b/node_modules/montage/CHANGES.md
new file mode 100755
index 00000000..5b544221
--- /dev/null
+++ b/node_modules/montage/CHANGES.md
@@ -0,0 +1,347 @@
+# v0.10.0
+
+-   **New property change API**
+
+    In prior Montage releases if you wanted to be notified when the value of a property changed, or an array was
+    modified, you used the addEventListener() API to register a listener object (or function). This API has been
+    replaced with addPropertyChangeListener(), which does everything that addEventListener() did, plus more.
+
+-   **Changes to data binding**
+
+    In this release, bindings can only be serialized on the source object in the binding. Practically, this means that
+    the arrow in the binding serialization can only point from right-to-left, not from left-to-right.
+    Also, the double-arrow syntax (<<->, for example) is no longer valid.
+
+-   **__debugChangeNotifications__()**
+
+    To help debug and inspect change listeners that you’ve registered on an object, call __debugChangeNotifications__()
+    This is temporary stop gap which will be replaced by better debugging tools soon.
+
+-   **KeyComposer and KeyManager**
+
+    Montage now includes a mechanism for easily listening for and responding to keyboard events, including individual
+    keys, or key combinations that you specify. It consists of two Montage objects: KeyComposer and KeyManager. You
+    create a KeyComposer object and specify the keys, or key combinations, that you want to respond to, as well as the
+    listener object that defines the necessary handlers. A default instance of the KeyManager prototype listens for
+    native key events on behalf of all active KeyComposers. It then invokes a callback method on the listener object
+    you specified.
+
+-   **TokenField**
+
+    The TokenField component is a text input component that displays tokens as its content.
+
+-   **Flow component**
+
+    The Flow component now supports selection handling and a feature called “stride”. The stride of a Flow component
+    defines points at regular intervals where scrolling should stop. For example, suppose you are creating a carousel
+    of album covers and you want the scrolling to stop when it reaches a position where the next album is always
+    positioned at the center. In this case the stride value would be the scroll distance between an element at the
+    center and the next element at the center. If you wanted scrolling to stop at every second or third album you would
+    set a stride to double or triple of that value. That way you could have, for example, a page showing 10 albums, and
+    you would be able to scroll 10 albums at a time, never stopping in the middle.
+
+-   **DynamicElement**
+
+    The DynamicElement component takes a string of plain text or HTML and inserts it into the component’s associated DOM
+    element, clearing any existing content.
+
+
+# v0.9.0
+
+-   **Draw  cycle changes**
+
+    After the willDraw phase all the components needing draw are sorted by their level in the
+    component hierarchy. They are then processed in reverse order. This ensures that all the
+    childComponents needing draw have drawn by the time the parent's draw is called. The didDraw
+    uses the same list but processes the componets in top down order (the reverse of draw)
+
+-   **Components**
+
+    Autocomplete Textfield Added
+        An Autocomplete Textfield extends the Textfield component to support suggestions for the user to pick values.
+        The HTML markup for the Autocomplete is the same as the standard HTML5 markup (<input>).
+        Wrapping the <input> HTMLElement as a Montage Autocomplete component adds Data Binding support for all
+        writable attributes of this element and allows the Developer to provide suggestions to the user based
+        on the entered value.
+
+    Popup
+        Support HTMLElement and Montage Component for the anchor property
+        Change willPositionPopup(popup, anchor, anchorPosition) to willPosition(popup, defaultPosition).
+        Change autoDismiss to autoHide
+        Support autoHide only for non-modal popups
+        Support string values (eg: 20px, 30%) for position parameters. If a number is provided, default to 'px'.
+
+-   **Template**
+
+    ``instantiateWithDocument(document, callback)`` method is added to use plain html templates without an owner.
+
+    Backwards compatibility for id attribute based references in serilization is removed, you should now use the
+    data-montage-id attribute.
+
+# v0.8.0
+
+-   **Data binding shorthand in serializations**
+
+    This release introduces a new shorthand syntax for declaring data bindings in a serialization. The new syntax
+    includes an arrow symbol that indicates the source of the binding and whether its one-way or two-way.The symbol can
+    take one of the following forms:
+
+    `<-` – One-way data binding, bound object on right
+
+    `->` – One-way data binding, bound object on left
+
+    `<<->` – Two-way data binding, bound object on right
+
+    `<->>` – Two-way data binding, bound object on left
+
+    Example:
+
+    ```ja