Add widgets and code to allow real Metro-style UI in web development.
Boxes, fonts, widgets, panel-flow.

The idea is to have demos of the different widgets made with Typescript. Nothing fancy just the simple demos so we can understand the different ways to create the objects and their interactions.

Currently if you use a DropDownList in a mobile app, the picker popup is changed to an ActionSheet automatically. This may work well for phone-based applications but when creating tablet-based apps, this can be a clumsy and less than ideal selection presentation. Please allow for some configuration option to all the DropDownList to use its normal browser behavior even when running in  mobile application. Referenced here: http://www.kendoui.com/forums/kendo-ui-web/combobox/prevent-actionsheet-selection-in-mobile-app.aspx

It would be nice to config a validation message to either hover or be in-line. It can be accomplished with some extra CSS currently, but it would nice to just pass in your preference.

The current Kendo Typescript module definition file assumes that all of Kendo is loaded into the global namespace, and hence does not work correctly if you are loading Kendo script via an AMD loader such as requirejs.

See here for full details: http://www.telerik.com/forums/robust-support-for-kendo-typescript-requirejs

I know you have special tag structure so that you can implement certain features.  However, for UI elements like the drop-down, numeric input and date-picker, it would be really great to use (or have an alternative control to us) native html elements and data- attributes that are easily recognized by mobile devices and newer, desktop browsers.  For example, for the drop-down, it would be great for it to render a select so that when received by a mobile device, the native option selector can take over.  I am posting this in the Web controls for those of us creating responsive apps where the input surrounded by spans doesn't really work out very well when the page is rendered on a mobile browser.  I realize that are trade-offs so maybe instead of completely disregarding the current controls, maybe another, pure control, or some configuration option to the current controls would be preferable. That way, the developer could decide what was more important - the UI enhanced feature or compatibility with device.

If the base css has something like the following:
	box-sizing: border-box;
	-moz-box-sizing: border-box;
	-webkit-box-sizing: border-box;
This will break the layout of the kendo controls.

Adding the following override will fix it:
	[class^="k-"], [class*="k-"] {
		box-sizing: content-box;
		-webkit-box-sizing: content-box;
		-moz-box-sizing: content-box;
	}

This catches all elements that have classes with "k-" at the start and overrides the box-sizing back to default.

Consider adding this to the kendo css (either the wildcard version or to each k-* class).

A very nice feature to have on the Dataviz gauges would be events for when the value changes from one range to another.  For example, if I have a gauge with range thresholds at 10 and 40, it would be nice if an event gets triggered when either one of those thresholds are crossed in either direction.  Let's say 0-9 is green, 10-39 is yellow, and 40+ is red.  If my value goes from 9 to 10 the gauge should raise an event that gives me the current range I'm in so I can act on it.

Table editor allows to select multiple cells, horizontally, vertically, or even individually while holding down the Ctrl-key.

If based on such selection the table wizard is opened, one would expect that any choices made would apply to all the selected cells.
Instead, the changes are applied only to the first cell.

Please, either disallow selecting multiple cells or better allow batch editing of the selected ones.

It would be nice if the player read the video not only via URL, but also directly from the internal location. and Then it would be nice to be able to directly pass the video (in byteArray)

I'm going to explain this in a number of different ways just to help clarify what I'm asking for: 1) When exporting Kendo grid to Excel, add support for setting the cell comments. 2) Please add support for a "comment" property to sheets.rows.cells. The value of the "comment" property would be used to set the cell comment in the generated Excel file. 3) In the link below, there is support for sheets.rows.cells.format. Add a similar property named sheets.rows.cells.comment that is used to set the cell comment in the exported Excel file. http://docs.telerik.com/kendo-ui/api/javascript/ooxml/workbook.html

Often when you get a plotAreaClick, a specific dataItem is highlighted with a tooltip showing.

When this happens, if you click on the plot area, but miss the actual data point, I would like to execute code like if seriesClick was triggered.

Example: in my tooltip I tell people to "Click to search", which opens a dialog with extra information about that data point. This works great in my seriesClick handler, since I can access the data point. If they miss the point, it triggers a plotAreaClick. They still see the tooltip for the item, but I can't open the search as I don't know which dataItem is current.

An alternative solution would be to expose whichever dataItem is currently responsible for the tooltip.

Support for more styling options for labels, for example, ability to add "text-decoration" to make the label look like a hyperlink.

So that the dates are still visible when a user scrolls down through the resources.

Hello,

It would be very nice to have a MultiSelect control such as Bootstrap MultiSelect by David Stutz:

https://github.com/davidstutz/bootstrap-multiselect

 

The problem with current multi-select control is that while it is very useful for applications with lots of screenspace, it is not ideal for business applications where every inch is very important. The Telerik multiselect is then at the following disadvantages:

1. It does not support Select All/Disselect All out of the box

2. It does not support "99 out of 100 selected".

3. It expands height when more items are selected, which is unacceptable for highly intensive data business applications, where numerous filters and rows of data need to be present at the same time on the page.

Are any plans to build such a control in addition to current MultiSelect?

Thank you

Menu, ContextMenu, TabStrip, PanelBar, Splitter have append, insertAfter and insertBefore methods.
kendoToolBar has only add, so there is no way to insert new command after/before other command.

Please add methods insertAfter and insertBefore to the kendo.ui.ToolBar widget.

Related forum post:
http://www.telerik.com/forums/insert-item-at-the-beginning

Hi,

The `alwaysVisible` option is ignored when we have an external DataSource.

Consider the following code:

```

var dataSource = new kendo.data.DataSource({
   pageSize: 2,
   data: [
       { name: "Jane Doe", age: 30 },
       { name: "John Doe", age: 33 }
   ]
});

$("#grid").kendoGrid({
   columns: [
       { field: "name" },
       { field: "age" }
   ],
});
var grid = $("#grid").data("kendoGrid");

grid.setDataSource(dataSource);

grid.setOptions({
   pageable: {
       alwaysVisible: false
   }
});

```

Here, since the `pageSize=2` and we have `2` records; I don't expect to see not the pagination and other pager options after `alwaysVisible` is set to `false`.
However, I do see them since `alwaysVisible` is completely ignored.

When I move the datasource back inside the `$("#grid").kendoGrid({})` everything works as expected.

Please let me know if this is an bug or I have mistaken in understanding something about the options.

Thanks,

Ajay

Chart series labels template to include html elements. At the moment, adding HTML elements in a chart series label template is possible but you cannot do anything on those elements. Would be nice to be able to re-template the labels by adding HTML elements in them and be able to design these elements or attach events to these elements.

Being able to trigger actions in other modules of one application is important.  Also, good design principles dictate that tight coupling of modules is not good.

In order to allow various modules to communicate with each other some sort of pub/sub or event routing framework should be implemented.

The Observable class is can be used as a starting point.

This new class should be tied to the presence of a DOM element.  This should be similar to how AngularJS handles events with $broadcast, $emit, and $on.

This could also be similar to the schemes describe in the below links:

https://keestalkstech.com/2016/03/strongly-typed-event-handlers-in-typescript-part-1/

http://www.wintellect.com/devcenter/jlikness/building-a-javascript-event-aggregator-using-typescript

Our business partners would like to be able to have gradients as part of the radial gauge color bar.  Similar to the following: 
http://i.imgur.com/DWfxi53.png