It would be beneficial to add additional support for tooltips natively on the Bubble Layer in RadMap

It would be nice to have navigation methods like 'nextRecord', 'previousRecord' to select grid records. These methods must  take care of paging issues and load next/previous page automatically and select the correct record afterwards. I've implemented these methods on my side nut it would be easier to have them natively as part of the grid implementation.

Provide or change the current default value of Aggregation from 'Max' to 'None', so that user can select his desired aggregation from UI.

Implement an option to preload some data for mobile list view in endless mode. This would increase UI time because there is allready data defined in HTML to view, the user must not wait for a datasource to load

I love your controls except Validator. I have finally made my own, where I can write multiple functions to evaluate each input just like this in typeScript:
new Helpers.Validate([
                { name: 'postId', test: [(e) => { if (e == "") return "Chose a post."; }] },
                { name: 'creditor, test: [(e) => { if (e == "") return "Chose a creditor"; }, ] },
                { name: 'description', test: [
                    (e) => { if (e == "") return "Make a description"; },
                    (e) => { if (e.length < 15) return "Your description are to short "; },
                ]
                }, ]);
It is now a pleasure to make forms and perhaps you will consider to reevaluate the structure of your Validator that I have been struggling with workarounds on for so many hours the last two years. 
Kind regards from Kenneth

Expand your Moonlight theme for use with the Mobile UI

when the mobile view uses a header, containing a toolbar as header it would be nice to be able to have a view title like in the navbar.

Box Plot (Box and Whisker) works great but would like to have Vertical instead of horizontal.

If we need to run some code in all of views, there is no way to do it besides add the call to each and every view in the project. In a large scale project that might have 100 views in many seperate folders and sub folders - this become a nightmare.

You should add the ability to add a generic event to all the views (kind of a "base class" for view) or by implementing the attached event via the application definition [var app = new kendo.mobile.Application()...]

Thanks,
ilan.

What control would I use for an 'Infinite' data scroller?

Where you have a horizontal div that is loaded initially with 4 divs, 2 of which are viewable in Portrait mode and more in landscape mode, but when you pull from the right, flicking to the left to get more content an ajax call get more.

This example is common on Amazon product pages of related products, but there you have to tap on the right  cheveron/arrow to fetch more, where as a smoother approach is to load more into the non-visible part.

I have only seen examples so far of infinite scrolling from the bottom in jquery.

I imagine that you would have got this solved already, so can you give me an example of I guess your data source component feeding a div with extra divs from the right. There must be a suitable trigger point so the spinner is not going forever due to a slow load. So I guess when a 

I am trying to work out what divs need to be in the page preloaded, and what can be fetched from the server.

Enable chart interactive features with Canvas rendering.

I would like to the see a feature wherein I can set additional target lines for a bullet chart. This is helpful in scenarios where I need to indicate a target and benchmark. I was able to see similar questions in your forum http://www.telerik.com/forums/set-target-range and also one on stack overflow http://stackoverflow.com/questions/25303748/kendo-bullet-chart-with-two-target-lines 

I'm currently using a chart with "categoryAxes.select" as a navigator for multiple other charts.
Problem being, when I display too much data, the navigator (and other charts) become laggy.
To help prevent that, I'd like a way to make the "selectEnd" and "SelectStart" events only fire on mouseup.
That would prevent multiple redrawing and help with the performance.

The ability to use multiple navigators on a column chart. 
Currently the option to compare two ranges of data on the same chart is not available out of the box.

Right now it seems to support only Shapes and Textboxes, what plans do you have for supporting Charts and perhaps any plain HTML (that would then be possible to "kendoify")?

Similar to specifying legend to bottom of chart, we should be able to put X Axis (or category Axis) Labels on the bottom, regardless of where the axis crossing value is. Sometimes the axis crossing value has to be at zero but the labels get in the way if this is the middle. If the data is dynamic, there is no way to use margin or padding consistently

In my bubble chart, I'm trying to center each tooltip above it respective bubble.  However, each tooltip doesn't show up in the same relative position for each bubble.  This makes it very difficult to perfectly center each tooltip over its bubble.  It would be nice if there were an option to center the tooltip vertically above the bubble.

As nodejs + express + jade is here, i think you should have more examples with jade and nodejs...

Instead of pulling the validation message from the Title attribute, use the title in the formatted message. For people who are trying to write localized messages, this could be very beneficial since they can just replace the title with the correct field name and change the message in the options.errors just once for the localized error message.

   _extractMessage: function (input, ruleKey) {
        var that = this,
                customMessage = that.options.messages[ruleKey],
                fieldName = input.attr(NAME);

        customMessage = $.isFunction(customMessage) ? customMessage(input) : customMessage;

        return kendo.format(input.attr(kendo.attr(ruleKey + "-msg")) || input.attr("validationMessage") ||  customMessage || "", input.attr("title") || fieldName, input.attr(ruleKey));
    },