Select: use attach-point instead of data-attach-point; specify focusNode via template instead of code
Update deliteful to match changes between delite 0.3.0 and 0.4.0-alpha.
Merges https://github.com/ibm-js/deliteful/pull/333
Fixes https://github.com/ibm-js/deliteful/issues/261
:before/:after pseudo-classes: use CSS3 syntax consistently (instead of CSS2 syntax)
List sample: remove height specification for ViewStack now that ViewStack's theme sets height:100%
Change details view step to use selection-change instead of click.
fix typo in jsdoc
Setting idProperty is not needed any more since https://github.com/ibm-js/deliteful/issues/255 is fixed.
Removed link to runnable demo for part8-1, as all runnable apps are already using build versions.
Add a single part8 runnable link that points to the fully built (layer) demo.
Add Button unit and functional tests.
Fixes https://github.com/ibm-js/deliteful/issues/70.
Update tutorial docs to reflect move of width100/height100 CSS classes to deltite/themes/defaultapp.css
Refs https://github.com/ibm-js/deliteful/issues/310, https://github.com/ibm-js/deliteful/issues/319
Remove LinearLayout Widget inheritance since it's already retrieved from DisplayContainer
update dependency to decor 0.3.0-alpha
Fix #276: Fix ViewStack under IE9 by removing animations + some doc fixes.
Fixes #291 - no protected member should start with underscore
Adapt deliteful to delite changes between 0.4.0-alpha and 0.4.0-alpha.2 changes.
Select: ensure the API of delite/Selection is always called for data items, not for StoreMap's render items; fix of getIdentity() to ensure store's idProperty is taken into account. Refs #255
some README cleanups
Select: fix mistake in previous commit (and improve messages in unit test)
Add ResponsiveColumns container, Close #269
Fixes https://github.com/ibm-js/deliteful/issues/303, https://github.com/ibm-js/deliteful/issues/322

The cause was essentially that divs had wrong heights:
- The toplevel widget had a height of 1em, which means the height of the toplevel widgets's font, which was 40px even if the star icons had a bigger font, so the widget was smaller in height than it actually looked.
- On mobile browsers, the widgets were also incorrectly spaced, because apparently the line heights were computed from the widget's (incorrect) heights, whereas on desktop the total height (including child divs) is used.

The changes to fix this are:
- Remove all height settings from widget's CSS, so all div heights are computed from the line-heightof the star icons (exception: the _zeroSettingArea div, which has no content, has a height of 1px; this is only for functional tests that want to click this div, which fails if the div has a zero size - we could remove this 1px height if it was possible to click on the left of the widget's focusNode, but click() seems to always click the center of an element).
- As a result of the CSS changes, the _zeroSettingArea clicks on the left of the stars will most likely not have the _zeroSettingArea div as target, but the underlying focusNode instead, so we also set the value "0" on the focusNode.
- Cleanup: remove unused _zeroAreaWidth property.