As the DropDownListFor object has both a "DataValueField" and "TextValueField", i find it frustrating that the AutoCompleteFor object only has a "TextValueField. This makes it cumbersome to actually get the ID and make it part of the MVC model binding. Have a DataValueField would greatly simplify MVC model binding for the types of projects that I'm involved in.
Create a package for Django will make easier to implement Kendo UI to a project.
A lot of our applications contain a number of prompts for activating certain processes. These include DropDownLists, DatePickers, etc. Most of these controls have <widget>For wrappers for binding to a model's properties for sending back to an Controller/Action. Some of the KendoUI widgets do not have this functionality so we are currently unable to easily submit data back for all of our controls in one model class. We would like to be able to do this for ListView and Grid. ListView to return a IEnumerable<class> for all of the selected rows. And the same for Grid. GridFor to return a IEnumerable<class> for all of the selected rows. We need some way to bind all of our widgets inside a form to a single model that has numerous properties so we can get/post to a Controller/Action and have all of that data available very easily witihn one class...and implemented in a consistent manner for all widgets. ListView and Grid are just 2 that we need right now, but would certainly like for all MVC Widget wrappers to always have <widget>For extensions as a standard practice. We believe this will make the KendoUI product stand-out among all of the available options and be the easiest to work with. We want to make our developers highly productive and this will go a long way towards that end.
As a suggestion for future development, make Kendo compatible with RazorGenerator.Mvc per this link: http://blog.mirajavora.com/re-use-mvc-views-across-projects-with-razor-generator
Kendo UI Menu currently supports only mouse over on child/sub menu items. Root items are configurable to open only if moust is clicked. But actually child items also should have the same type of configuration. In my organisation people simply clicking everytime on menu items, they dont wait for the mouse to open its child items. And when the child menu items opened they press mouse button by mistake and the menu gets closed that gets them irritating.
What's way to Apply DisplayTemplate(Annotation) for my Model with Ajax binding (Read)
I've downloded a free Kendo UI Trial. Unfortunately there aren't StockData.mdf in Template project. Can you fix this issue? I'm choosing component base for our company and it realy prevents me.
I need configure in my Razor View, with my Multiselect helper, the maxselectedItems property (like others properties: MinLength, Filter,etc)
Currently for the Window and Tooltip controls (possibly others, but those are the ones that I'm working with), the Height and Width properties are both integer properties which set the height and width in pixels. I would like the ability to be able to enter Height and Width in 'em' units, much like can be done with the grid column widths.
I would like to see a separate assembly that can be referenced both on ASP.NET MVC and Application server side and that the DataSourceRequest can be transformed into a DataSourceResult on the Application server side and sent back to the website. At the moment this is not possible due to the non-generic definitions of the DataSourceRequest and DataSourceResult classes. Referencing Kendo from the Application server side also requires references to System.Web and others that shouldn't be necessary. Statically typed transport serialization should be supported, as required by WCF, Message Queuing or even Protobuf. Such transport mechanisms are required by N-Tier environments. At the moment, if all DataSourceRequest's should be processed on a web server and propietary database licensing is in effect (ex. for MSSQL) where the cost is per port, it would end up being very costly.
Most of the time DefaultValue isn't known. Allow us to enter null or don't require it.
Include an x.js as well as x.min.js files in the upgrades. MVC's bundle config by default does not include the .min file in debug mode.
Right now a master grid can be configured in code using the GridBuilder, but the detail grid needs to be configured in a template and a whole lot of Javascript. As it is much easier to prevent errors writing (and compiling) server side code using the GridBuilder than using large parts of Javascript. In the good old MVC Extensions there was a method DetailView(detial => detail.ClientTemplate(MethodToCreateDetailGRidUsingGriudBuilder()) I would very much like the same approach in Kendo UI as it provides a more robuste method of building Detail Grids.
Update Kendo project template so that it is compatible with ASP.NET and Web Tools 2012.2.
I hope, for the grid's custom/template popup editor, you guys can include a footer section at the bottom of the window, and allow us to choose to align the buttons left, middle or right. Right now there's no separation for these buttons. It blends right in with the rest of the editor, and the buttons are default floated to the left. It can even be as simple as that, a greyed area at the bottom, just to indicate some separation between the body and "footer" Like this: http://twitter.github.com/bootstrap/javascript.html#modals I hope this can be applied to the window component as well Right now I have to completely implement my own custom popup/modal window because this isn't supported.
It will be helpful if we have insert table, add/delete rows or columns button on the toolbar. I have seen Radeditor toolbar for Asp.net Ajax by Telerik. It will be great if more useful buttons are added on the toolbar.
Given the release of ASP.NET and Web Tools 2012.2, is it possible to create custom project templates. It will be extremely nice if we can get editor intelligence with kendoui widgets when using plain JS, specially with the template engine. Some simple examples about this can be found at the end of thhis article. http://www.hanselman.com/blog/ReleasedASPNETAndWebTools20122InContext.aspx
I believe the intent of the component Kendo is very good, but this in a very early stage. For example, resource error in Portuguese language
instead of using the text parameter to apply filter in server side, use the filter parameter of the DataSourceRequest/DataSourceResult object for the comboBox.