Routing is important for building single page apps which is missing from framework right now. 

Routing component of Backbone is very nice. Simple and intuitive. A library similar to this that is integrated into the core framework would be great.

In case there are a couple of opened modal windows(win1, win2, win3, win4) after destroying one that was closed(win5) – two next in chain(win3 and win4) becomes enabled, instead of only the last one(win4).

I’ve analyzed the code of method kendoWindow.destroy and found following lines 

if (shouldHideOverlay) {
    that._overlay(false).remove();
} else if (modalWindows.length > 0) {
    windowObject(modalWindows.eq(modalWindows.length - 2), that.options.name)._overlay(true);                 
}

It seems that line 
modalWindows.length - 2 
should be changed to
modalWindows.length - 1
as modalWindows holds currenlty opened windows, and overlay should be turned on for the last one.

Currently, hashBang (#!) is supported in mobile but it can only contain view_id, it can't be configured as path although it is available in SPA.

It is limiting the SEO capabilities. Support for the following url scheme will be big boost to SEO optimized urls.

/view_id/:category/:item/

Would be nice to have a way to easily configure columns to be fixed (position and width), like a checkbox column to select rows.

This kind of column need to have fixed width and position (cannot be reordable).

But, KendoUI could has also a native support for rows selection, allowing us to just turn on this feature that could have a lot of sub-features: Remember selected rows by page, mark/unmark all, custom options in the column menu to massive mark, and so on.

add server side wrapper jsp for mobile, support MVC binding, when server side data change, mobile side widget auto change

Native mobile tabstrips each have have their own set of views and history per tab.  So for example if you are doing work on one tab, then click another tab, returning back to the first will show everything as it was before leaving.  


kendo mobile's tabstrip doesn't work that way.  Clicking on another tab destroys the content in the previous tab. It should not do that!  Rather, it should mimic the behavior of a native tabstrip.

We find with lots of UI vendors put up cool demos, but rarely a more realistic view. We like to see the controls in a LOB style layout with:
1. A Purchase order where you enter PO#, Date, Customer (Autocomplete), Customer Name (as result of autocomplete select), ShipToCountry.
2. Order lines (grid or other) with ProductID (autocomplete which then populates description and price), Quantity (which in turn calculates line price).
3. As a result of ajax submit, the server side validation returns error saying order value exceeds customer limit AND ShipCountry not valid for this customer. So the form displays message "Exceeds customer limit" and ShipToCountry input is highlighted with error message "Not valid for this customer".

And make it look good!

Example of existing:
http://jscrollpane.kelvinluck.com/

Standart scrolling in windows sucks (and takes mush space).
,Kendo Grid has to have designable scrolls, pls :)

T4 Templates to slect in the asp.net Wizard to provide views controllers and and data connections to services

hi, we are trying to create part tracking dashboard in mes tool. we want to have stacked bar plus  marker to track the shipping and stock level.  but we are finding the combine chart feature in this tool. kendo ui support team was reviewed our requirement in future.

We were recently going to upgrade from Kendo 2012Q2 to 2013Q1. Unfortunately we can't because we require support for IE8+. 

Our issue is the grid's dataItem method. In IE, it's just too slow. In order to use the newer version of Kendo, we have to upgrade to jQuery 1.9.1 (supplied in the Kendo package). In some cases, the selectors you are using are 13x slower than they were in jQuery 1.7.1.

http://jsperf.com/jquery-1-9-performance-issues

In the dataItem method, you're using the ">" selector instead of children. This, coupled with :not causes this method to crawl. 

In the jsperf test I linked above, I profile many different scenarios. You might want to take a look and see if perhaps you can make use of the .children() method and .not() instead of :not in future releases.

We want the Grid fix the remote virtual scrolling with groups. 
In this case the Grid stay launching requests indefinitely.

If you need to draw a horizontal line in Kendo DataViz Chart (to express desired target value for budget consumption, for example), you have now only two possibilities using line series or plot bands. Unfortunately both approaches have drawbacks:

1) Using additional line series
In this case the line doesn't start at the beginning of the image of the chart, there is visible margin. Also, the determining of number of values for the line series is painful in case you have multiple series with different value counts bind on server side.

2) Using plot bands
In this case the actual width of the band is dependent on the scale of the chart, which can be dynamic depending on data. So this approach is not usable if you want a line width specific width.

What we need is draw a simple line with given width, color and brush.

Allow the user to execute certain methods of the widget and inspect the result.

I would like the ability to make the End Date filed optional when creating a recurring appointment via the Kendo Scheduler.

Little Square handle in the corner of a cell to repeat / increase counter (numeric/date)
Just like Excel.

Hi Kendo UI Team,

maybe in the future, you can add offline documentation bundled with the downloaded package, i think it would be nice, thanks

Implement Excel-like functionality of selecting a cell, selecting the bottom right corner and then dragging down to either copy the value (string) or increment (number).  This feature saves a lot of time and is the main reason we use custom Excel apps as database data entry tools.  Implementing this in Kendo would allow us to migrate to the web

LESS is a very good idea to use, makes Kendo styles much more readable! However, right now the LESS syntax used to generate styles (ThemeBuilder for example) use a non-official branch of LESS syntax. Unfortunately this makes LESS impossible to compile any other way than using the changed JS libraries and harder to integrate with other LESS in the project.

I suggest you either convince the LESS community that the changes are good and merge them into the official branch or consider the possibilities to use official LESS syntax.