Issue 1

[adriatic]

to be written by @JeroenVinke

[JeroenVinke]

Category

missing API / templates / bug / other

Description of the problem

Cause

Solution

[JeroenVinke]

Category

templates

Description of the problem

Aurelia's templating syntax is different from Kendo's own templating syntax. When we pass Aurelia templates to a Kendo control, Kendo will try and parse that template as if it's a Kendo template, causing in errors: http://dojo.telerik.com/oNOGe

Cause

Kendo's own templating system is always active

Solution

A property that we can set while initializing widgets, or a property on the kendo global that disables Kendo's own templating system entirely. Currently we pass templates as function callbacks (template: () => '${myAureliaTemplate') to the Kendo controls which disables Kendo's templating system for that one specific template. This is something Telerik built in for Handlebars support, but it feels like a hack.

It also prevents users from serializing the grid to JSON since functions are not serializable.

[JeroenVinke]

Category

missing API

Description of the problem

A very simplistic example of a missing API function is for the Kendo Button. When you initialize a Kendo Button you can specify an icon. But when the button has been created there is no way to change the icon, without having to destroy and recreate the button. This effectively prevents us from ever being able to two-way bind the icon property, as we really don't want to recreate controls whenever a single property changes

Cause

There is a missing API function to change the icon of a button

Solution

Add a function to change the icon of a button

[JeroenVinke]

Category

other

Description of the problem

In the destroy widgets manually document it states that in order to destroy a widget you need to empty out the div that the widget was initialized on. Which is fine for Grids that use a datasource because the data is in the datasource. But when the grid is initialized from HTML you don't really want to clear the HTML because you'll lose the data.

Cause

Sometimes you need to clear the div that a widget was initialized on, but sometimes you don't.

Solution

Kendo improves their destroy function to be more consistent (so we can reuse elements) or the bridge adds logic to always initialize widgets on new elements.