add a VS extension to place and configure  widgets in the view with corresponding action methods.
The heavy data aware widgets (grid, scheduler) first.

The serialization of a grid should be more lightweight. Texts are serialized multiple times - for each column and in case of several grids on a single view all texts are serialized many times.

The serialization of "standard-texts" can be optimized:

"filterable": {
                        "messages": {
                            "info": "Zeigt Zeilen mit Werten, die",
                            "isTrue": "ist richtig",
                            "isFalse": "ist falsch",
                            "clear": "Löschen",
                            "and": "Und",
                            "or": "Oder",
                            "selectValue": "-Wählen Sie-",
                            "value": "Wert",
                            "cancel": "Abbrechen"
                        },
                        "operators": {
                            "string": {
                                "eq": "Ist gleich",
                                "neq": "Ist nicht gleich",
                                "startswith": "Beginnt mit",
                                "endswith": "Endet mit",
                                "contains": "Beinhaltet", "doesnotcontain": "Beinhaltet nicht"
                            },
                            "number": {
                                "eq": "Ist gleich",
                                "neq": "Ist nicht gleich",
                                "gte": "Ist größer als oder gleich",
                                "gt": "Ist größer als",
                                "lte": "Ist kleiner als oder gleich", "lt": "Ist kleiner"
                            },
                            "date": {
                                "eq": "Ist gleich",
                                "neq": "Ist nicht gleich",
                                "gte": "Ist nach oder gleich",
                                "gt": "Ist nach",
                                "lte": "Ist vor oder gleich",
                                "lt": "Ist vor"
                            },
                            "enums": {
                                "eq": "Ist gleich",
                                "neq": "Ist nicht gleich"
                            }
                        }
                    },

It doesn't seem possible to set the width or height of gauges through the MVC server wrappers. This is useful functionality that should be easy to implement.

When returning data for a grid using the "Model.ToDataSourceResult(request, ModelState)" syntax, if there are any ModelState errors, the grid fails to load any of the data.  In addition to validation errors, I would like to be able to send back feedback messages that can be extracted client-side that would not affect the binding of the grid.

html select has a groupoption tag, and also the possibility to add classes or styles to indivual rows in a combobox.

With it, you can combine the items in a combobox in groups/categories.

Styling could ofcourse be done by using custom-templates

It would be nice to be able to set options other than the window's title and set events on the window that is exposed by the grid editing options.

I want to load a particular ViewModel into a treeview but using the MVC wrappers does not allow for setting what field will be the Id, and the hasChildren property. The model information can be set via the JavaScript configuration though.

It would also be nice to mark additional data on the model that should be sent to the Read action along with the Id from my item.

it would be nice Editor -> DocumentBrowser & MediaBrowser  same RadEditor

In the ASP.NET MVC Wrappers for kendoWindow there is a Visible(bool) option which the docs suggest is to stop the window displaying on page load.  

However, setting it to true or false and the generated javascript is always the same and the window opens on page load.

I'm now creating them manually in javascript myself to get round that but would be nice to use the MVC wrappers as they are intended.

From what I can see, there is the possibility of providing the TimePicker a list of Dates when building it via JavaScript (http://docs.telerik.com/kendo-ui/api/web/timepicker#configuration-dates), but not through the MVC wrapper. It would be nice to have parity between the two methods, if possible.

When deleting or editing a series on the Scheduler, there is no option to edit/delete "all subsequent events".  Quite often, when editing a series, users will want to adjust the selected event and all subsequent events when editing a series.  iCal, Google Calendar, Outlook all support the option of editing a series in that manner. 

I would like the Kendo Scheduler Occurrence popup that contains the "this event only" and "entire series" options to also have options that include 
"all events in the series before the selected one"
"all events in the series after the selected one" 
like other calendar implementations.

Thanks

It could be convenient to have the editor templates directly added to the solution (in Views\Shared) when deploying the ASP.Net MVC nuget package.

The Kendo UI Grid currently supports posting the rows in the grid back to the server with the rest of the form, but in order to do this you have to add ClientTemplates for each column, with a hidden input to store the value.  If you want to use client-side validation with this setup, you have to add the validation attributes to the hidden inputs as well.  In an ASP.Net MVC situation, this adds up to a lot of manual synchronization between the validation attributes that exist on the viewmodel and the corresponding columns in the view.  It would be great if the grid could enable this type of behavior in a way that is more automatic and requires less manual synchronization between the viewmodel and view.  For example, if there was some kind of MVC helper that would take the display expression and name for the hidden input and would generate it automatically, complete with the validation attributes from the property being bound to, that would be great.

It would be nice to handle editor template directly in the grid's configuration. Very often we have to use a simple custom editor but we end up creating a new file every time.

Html.Kendo().Grid<Model>()
.Columns(cols=>
{
    cols.Bound(m=>m.SomeProp)
        .EditorTemplate(@<div>
            Html.Kendo().ComboBoxFor(m=>m) [...]
        </div>);
})

ClientTemplateId is fine when you are using kendo templates, but in our case we use handlebars templates, and in order to tell a listview that we need to do something horrible like 

<script type="text/x-kendo/tmpl" id="TPStrengthTemplate"> 
	#= Handlebars.templates.TPStrength(data) #
</script>

asside from interop, the script tag is untenable in large applications, as it may force us to create TONS of superfious script tags (some with the same id in the case of repeating partial views). Especially when template precompiling is a 'best practice' for client templating (hence our use of handlebars)

instead there should just be an option to specify a client handler pointing to Handlebars.templates.TPStrength

What's way to Apply DisplayTemplate(Annotation) for my Model with Ajax binding (Read) 

ASP.NET MVC DisplayTemplates should by evaluated and take effect in Grid columns (see: http://www.telerik.com/forums/using-a-displaytemplate). Thus for custom formatting, defining a ClientTemplate() should not be required.

The WPF implementation of the Kendo Grid has a "selectColumn" type that can be used to create a checkbox column that implements a multi-select functionality into the grid.  

It would be nice to get this kind of built-in functionality in the standard javascript version of the Kendo Grid, instead of having to manually create a templated unbound column.

Would be great to limit the Locale files and / or make them specific to the locales you are actually using. e.g. only EN-NZ or EN-US

In a treeview we have different model classes merged into a single model for consumption by the treeview. For example, an organization model and a person model. Based upon an attribute in the treeview model, we would like to present different templates. These templates would be set back on the server-side as the templates are stored in a database. The templates are designed by the end-users.

Thus, when an organization row appears in the treeview, it uses the orgTemplate, and when the persons under the organization appear, they use the personTemplate.