<kendo:grid-filterable extra="true"> <kendo:grid-filterable-operators> <kendo:grid-filterable-operators-enums neq="Is NOT equal to:" eq="Is equal to:" /> </kendo:grid-filterable-operators> </kendo:grid-filterable> AND <kendo:grid-filterable extra="true"> <kendo:grid-filterable-operators> <kendo:grid-filterable-operators-enums eq="Is equal to:" neq="Is NOT equal to:" /> </kendo:grid-filterable-operators> </kendo:grid-filterable> always gives the same result: neq is always the first element in the filter combobox and eq est the second item. Would be nice to control display order from the <kendo:grid-filterable-operators-enums /> JSP tag
Play framework is probably the fastest growing framework in the Java space due to its container-less deployment and non-blocking IO features. I think its an ideal vehicle for Kendo/Kendo MVVM to visit Java land for the first time! Normally this means adopting logic-less mustache templating (see https://github.com/pk11/play-scalate/) but other options may exist.
Consider “Java” wrappers for the KendoUI . The use case for “Java” wrappers is for existing Java server side applications that embed the UI code in the Java classes (no JSP / JSF), similar to the Vaadin philosophy, but without having to adopt Vaadin and yet be able to incrementally enhance existing / stable, line of business web applications, without a complete rewrite.
Allow generation of kendo:grid columns using JSP tags, such as c:forEach. Currently throws an error as grid:column needs its immediate parent to be a grid:columns tag.