When I used the angularjs to bind template data to kendo-mobile-scroll-view, it will post error when scroll to the last page, it post error as Uncaught TypeError: undefined has no properties, I think there is an error existed, could you fix it? If it is not, or you could give a more clear example on demo part?
Just make it compatible!
MultiSelect field to be able to be inputted manually, if look up is not available
Select All Check box required in a grid and we can select a specific records by using the checkbox, and will go for export to excel or export to pdf.
Make ENTER activate a submit button on a page from all widgets including the dropdown list.
should have a basic component for split button
kendo.diagram.Path is an object that can be appended to a kendo.diagram.Group object and supports such things as SVG paths. This is undocumented and unsupported functionality that can be accessed in pure JS but is inaccessible in TypeScript. Can you please support this object and add its declaration the d.ts file?
Would be nice to have a replacement for standard checkbox, that looks deiiferent in different browsers (like jqWidgets has) and CheckBoxGroup widget. For example: <div data-role="checkboxgroup" data-bind="value: groupValues" data-row-items="5" data-text-field="text" data-value-field="value"></div> And the model: kendo.observable({ groupValues: [ { text: "Text1" value: 1 }, { text: "Text2", value: 2 } ] })
Please add support for named stacks in Area and Line charts. It should work similar to Bar/Column charts. For example, with the following series definition [{field: 'Whole', stack:'whole', name: 'Whole Part'}, {field:'Part1', stack:'parts', name:'Part 1'}, {field:'Part2', stack:'parts', name:'Part 2'}] Part1 and Part2 should stack but not "Whole".
Kendo Map - Auto-Center after loading the geojson file.
List view should have a Option for the checkbox to select the list with custom template for the checkbox with custom template for the checkbox which can behave as the toggle button for mobile and can be disabled if not required. Cause the existing system to select and deselect item is very non user friendly
It makes sense that grouped grids should be sorted by the group name for proper paging, however, it would be nice to be able to sort by group name THEN BY another field. Wouldn't mess up paging.
Kendo has places where you can specify cssSpriteClass, and other places where you can specify the actual icon by name. My proposal is to provide a way to say I am using halflings or font awesome or anything else for that matter, and just specify icon "fa fa-play" and its done. Currently its way too much work to implement kicon wrappers for font awesome fonts, and then they dont work everywhere anyway.
The grid and chart can be used in mobile apps and seem to work properly. (See http://kendoui-feedback.telerik.com/forums/127393-telerik-kendo-ui-feedback/suggestions/4522456-touch-grid-for-tablets-that-has-as-many-features-a for the suggestion that they do work). However, they don't adapt to the mobile appearance like the dedicated mobile widgets, which makes them hard to use in cross-platform mobile applications.
Topojson is a much more compact data format for spatial data. Supporting it would allow more complex spatial data to be loaded without slowing down the browser experience.
Support for injecting some custom header information in the export PDF and Excel? e.g. You are exporting some grid to excel or pdf and you want do display the search parameters in the header of the document.
I was wondering if there's a way to validate a form that has inputs with identical names. The following JS Fiddle is an example of identical names: http://jsfiddle.net/fmpeyton/5c9d2p0c/ I would hope there would be a way to handle this, since lots of backend languages have the ability to accept identical name attributes, as they concatenate the values or convert them into an array or collection (ASP.NET).
RTL support for the kendoui gantt widget
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