Template usability improvements

New features

• List inside List property support: List<List<?>>
• @RepeatIndex as a shorthand for @EventData("event.model.index") for use with <dom-repeat>.
• Polymer template class methods can be annotated with @ClientDelegate to make them available as this.$server on the client.
• Subproperties in two-way data bindings are now officially supported

Fixes

• Make list bindings work in SDM

Breaking changes

• @EventHandler is now only used for exporting PolymerTemplate event handlers. Use @ClientDelegate for exporting an RPC target into the element.$server namespace.
  • Before 0.0.23
    • @EventHandler on a method in a class extending PolymerTemplate is exported as element.methodName.
    • @EventHandler on a method in a class extending Component (but not PolymerTemplate) is exported as element.$server.methodName.
  • After 0.0.23
    • @EventHandler on a method in a class extending PolymerTemplate is exported as element.methodName.
    • @ClientDelegate on a method in a class extending Component (including PolymerTemplate subclasses) is exported as element.$server.methodName.
  • Background: There are two different types of exported RPC targets intended for different situations. Prior to this change, it was not possible to use the $server approach together with PolymerTemplate because the @EventHandler annotation had different meaning depending on the context.
    • element.methodName functions are intended as Polymer event handlers. Any method parameters should be annotated with @EventData to define what value to extract from the Polymer event.
    • element.$server.methodName are intended to be directly invoked from JS. Method parameters are directly encoded as JSON and made available on the server.

Demos

• Minesweeper demo now uses list bindings
• jQuery table demo was fixed

Tutorials

• Updated the list binding tutorial to highlight the @RepeatIndex usage

All changes

https://github.com/vaadin/hummingbird/milestone/26?closed=1