diff options
author | Nivesh Rajbhandari | 2012-06-13 13:51:39 -0700 |
---|---|---|
committer | Nivesh Rajbhandari | 2012-06-13 13:51:39 -0700 |
commit | 263ecfc95bd7eb5c726cd5688c3d74eb10296811 (patch) | |
tree | 7c907dd58e9b4f4a1d4802d8d22b9c84d3c2edf3 /node_modules/montage | |
parent | 1bb2778224982aea7b9781c6559bb659983a400f (diff) | |
parent | a827f2769d75848c0ba0bff03a927c1f2706322b (diff) | |
download | ninja-263ecfc95bd7eb5c726cd5688c3d74eb10296811.tar.gz |
Merge branch 'refs/heads/ninja-internal' into PI_HotTextFixes
Conflicts:
js/panels/properties.reel/sections/position-size.reel/position-size.html
Signed-off-by: Nivesh Rajbhandari <mqg734@motorola.com>
Diffstat (limited to 'node_modules/montage')
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 @@ | |||
1 | # v0.10.0 | ||
2 | |||
3 | - **New property change API** | ||
4 | |||
5 | In prior Montage releases if you wanted to be notified when the value of a property changed, or an array was | ||
6 | modified, you used the addEventListener() API to register a listener object (or function). This API has been | ||
7 | replaced with addPropertyChangeListener(), which does everything that addEventListener() did, plus more. | ||
8 | |||
9 | - **Changes to data binding** | ||
10 | |||
11 | In this release, bindings can only be serialized on the source object in the binding. Practically, this means that | ||
12 | the arrow in the binding serialization can only point from right-to-left, not from left-to-right. | ||
13 | Also, the double-arrow syntax (<<->, for example) is no longer valid. | ||
14 | |||
15 | - **__debugChangeNotifications__()** | ||
16 | |||
17 | To help debug and inspect change listeners that you’ve registered on an object, call __debugChangeNotifications__() | ||
18 | This is temporary stop gap which will be replaced by better debugging tools soon. | ||
19 | |||
20 | - **KeyComposer and KeyManager** | ||
21 | |||
22 | Montage now includes a mechanism for easily listening for and responding to keyboard events, including individual | ||
23 | keys, or key combinations that you specify. It consists of two Montage objects: KeyComposer and KeyManager. You | ||
24 | create a KeyComposer object and specify the keys, or key combinations, that you want to respond to, as well as the | ||
25 | listener object that defines the necessary handlers. A default instance of the KeyManager prototype listens for | ||
26 | native key events on behalf of all active KeyComposers. It then invokes a callback method on the listener object | ||
27 | you specified. | ||
28 | |||
29 | - **TokenField** | ||
30 | |||
31 | The TokenField component is a text input component that displays tokens as its content. | ||
32 | |||
33 | - **Flow component** | ||
34 | |||
35 | The Flow component now supports selection handling and a feature called “stride”. The stride of a Flow component | ||
36 | defines points at regular intervals where scrolling should stop. For example, suppose you are creating a carousel | ||
37 | of album covers and you want the scrolling to stop when it reaches a position where the next album is always | ||
38 | positioned at the center. In this case the stride value would be the scroll distance between an element at the | ||
39 | center and the next element at the center. If you wanted scrolling to stop at every second or third album you would | ||
40 | set a stride to double or triple of that value. That way you could have, for example, a page showing 10 albums, and | ||
41 | you would be able to scroll 10 albums at a time, never stopping in the middle. | ||
42 | |||
43 | - **DynamicElement** | ||
44 | |||
45 | The DynamicElement component takes a string of plain text or HTML and inserts it into the component’s associated DOM | ||
46 | element, clearing any existing content. | ||
47 | |||
48 | |||
49 | # v0.9.0 | ||
50 | |||
51 | - **Draw cycle changes** | ||
52 | |||
53 | After the willDraw phase all the components needing draw are sorted by their level in the | ||
54 | component hierarchy. They are then processed in reverse order. This ensures that all the | ||
55 | childComponents needing draw have drawn by the time the parent's draw is called. The didDraw | ||
56 | uses the same list but processes the componets in top down order (the reverse of draw) | ||
57 | |||
58 | - **Components** | ||
59 | |||
60 | Autocomplete Textfield Added | ||
61 | An Autocomplete Textfield extends the Textfield component to support suggestions for the user to pick values. | ||
62 | The HTML markup for the Autocomplete is the same as the standard HTML5 markup (<input>). | ||
63 | Wrapping the <input> HTMLElement as a Montage Autocomplete component adds Data Binding support for all | ||
64 | writable attributes of this element and allows the Developer to provide suggestions to the user based | ||
65 | on the entered value. | ||
66 | |||
67 | Popup | ||
68 | Support HTMLElement and Montage Component for the anchor property | ||
69 | Change willPositionPopup(popup, anchor, anchorPosition) to willPosition(popup, defaultPosition). | ||
70 | Change autoDismiss to autoHide | ||
71 | Support autoHide only for non-modal popups | ||
72 | Support string values (eg: 20px, 30%) for position parameters. If a number is provided, default to 'px'. | ||
73 | |||
74 | - **Template** | ||
75 | |||
76 | ``instantiateWithDocument(document, callback)`` method is added to use plain html templates without an owner. | ||
77 | |||
78 | Backwards compatibility for id attribute based references in serilization is removed, you should now use the | ||
79 | data-montage-id attribute. | ||
80 | |||
81 | # v0.8.0 | ||
82 | |||
83 | - **Data binding shorthand in serializations** | ||
84 | |||
85 | This release introduces a new shorthand syntax for declari |