Mapping xml with namespace prefixes is not currently possible. Basic XPath predicates should be supported (no less than is already natively supported by jQuery). Kendo UI should have first-class support for XML. As it stands, Xml support is currently second class to JSON.
Currently when I choose a column filter and click on the filter button, a request is sent to the server and data is bound. However, if I work with large data sources and I know in advance that I want to filter by FirstName and LastName, for example, I would like to choose both the filters first, and when filter settings are finalized, I would like to rebind the grid with a button click, for example. This would enable to bind only once the grid, instead of n times, if the user chooses lazy filtering which would be very useful, especially in the case of large data sources
At the moment, the DataSource only uses one field for its ID property (if you enter several, then only one is used, apparently). This doesn't reflect reality, in that in many cases (where one record is a child of another), the key field for a database table is a composite (from 2 or more fields). The existing situation causes problems in inline editing of the KendoUI grid, because default values need to be set for foreign key fields, but if these are set to a valid value, then spurious calls to the Inline_Create method occur because the DataSource treats the record as a new record when it is not. In any case, allowing multiple fields would simply reflect reality.
It would be nice to have the IF and IFNOT bindings like KnockoutJS has. It would help keep the DOM cleaner instead of having to use the Visible binding.
Currently when there are any errors in data-bind attributes you usually get some array out of bound indexing error (in parseBinding()) or some other obscure error. This suggestion is to trap these errors more aggresively and provide better error messages.
Currently if you have combos that are bound via MVVM or knockout etc and have a kendo data source on them for doing suggest lookup they will query everything without a filter to get the display value for the bound value that is set to the value property of the combo. I should be able to pre-populate an initial set of data on the datasource which it will use when the value property is set. If and only if it isn't set, it should then go and do an odata query with filtering for the specific item and only the specific item based on the field that the dataValueField is bound to, not everything. Further the combobox and auto-complete should cache data and searches previously done so that it doesn't have to hit the data source again in these scenarios as the user types.
Mobile app should be able to save the data locally in the mobile device and when online network status is detected, should have the mechanism to synchronize the local data back to the server. I asked this during the webcast demo about supporting the html5 local web storage or the html5 indexeddb.
Instead of using JSON to create a pie chart in Dataviz, it would be so much easier to use an SQLDataSource, So that the pie chart can be dynamically updated.
Add a Kendo UI Mobile Listview with real time cross domain data binding and this could be a simple modification of your current listview demo, where instead of using the hard coded data, use the real time data which is hosted on a website (i.e. google or twitter) and bind that data (json) to the listview...
It should be possible to specify a validate() method on each viewmodel that gets triggered each time a new model value is .set(). In case of an unsuccessful validation an error event or binding could be triggered.
We are evaluating migrating from Asp MVC to KendoUI (MVC), which looks promising. However, there is one BIG problem we have encountered: Cell values of null are displayed as "Null" instead of as ""! I really urge you to change this since this would require large changes to very many places otherwise. At least an option to select the behaviour. Thanks /Victor
Is there planned support for JSON-RCP for DataSource? At least something that does batches? Using REST is fine for example code, but otherwise can result in many connections, etc. While a bigger problem in mobile, it still makes a difference in desktop. ExtDirect and json-rcp both seem to fit the bill.