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.
Please provide a way to display multi-line labels in the chart controls such as the bar chart category axis. The need is detailed in this post: http://stackoverflow.com/questions/13247577/line-break-in-category-label-of-kendo-ui-chart
Can we have a way to implement the org chart functionality (present in Rad Controls for ASP.NET) in MVC using Kendo
In order to visualize process workflow items and their sequence, a new Kendo UI control would be a big step forward. I was getting inspired by SAPUI5 control "process flow". Here the link: https://sapui5.netweaver.ondemand.com/explored.html#/sample/sap.suite.ui.commons.sample.ProcessFlowConnectionLabels/preview This UI is able to be used in different situations: 1. Visual display of workflow steps 2. Display of relations between business work items: connections and their frequency of usages between business workflow items . The UI should be able to define workflow items and their connection. It should also be possible to define templates for connection types and process item types.
I am using Kendo diagram for Workflow wizard. right now i am using my custom icons for Workflow shapes. I also want to use icon/image for connection lines between 2 shapes. Please provide this feature.
Current when using the HierarchicalDataSource you can only load one level of data at a time. I would like to be able to pre-populate the entire tree (but have the ability to refresh it via remote data, should I so need).
Cool Kendo UI Q1 2016 webinar today... could not ask any questions using IE11 so lost on prize chances. Very entertaining Thank you. Are there any good working examples of using the new Grid or Spreadsheet features utilizing an API such as government information as discussed?
Hi You have very nice charts colorful and detail but thing page like upperside we have combobox or radiobutton and i have bar chart so when i click selections i want to convert bar chart to area chart or scatter chart to do this dynamically way... It will be best
I am put off using KendoUI because of the limiting nature of theming and styling the controls especially the sprites They don't scale well, can't be coloured and are hard to replace without lots of css editing.
Since 'bind' and 'unbind' have been deprecated and replaced by 'on' and 'off' in jQuery, kendo controls should support the use of 'on' and 'off' for event binding.
Provides a easy way to filter a list with a simple client-side search feature (example add data-filter="true" attribute to the list). The framework will then append a search box above the list and add the behavior to filter out list items that don't contain the current search string as the user types.
When the are building the grid, will bu useful to have and option to set the page number that you want to display .DataSource(dataSource => dataSource .Ajax().PageSize(Model.PageSize).Page(Model.Page) .ServerOperation(true) // Paging, sorting, filtering and grouping will be done client-side .Read(read => read.Url("/results/gethomes"))
The library is getting pretty big - lots of great features, but still big. I would love to see the team take some time and offer more options to reduce the size of the ALL and CUSTOM builds. Perhaps look to drop old browser support and do a pass on tightening things up. Set a goal for the team to reduce the library size by 10%.