Simple edit like <input type="text" but with full support of skins and Mask. With this the current date piker and roadmap numeric input you gave a full control scheme with all the skins applied.
Hi ! I was trying to create a scheduler using Kendo Scheduler. It seems that there is no way for me to create a timeline view like Telerik
I like the Wpf/Silverlight version. But it should be possible in HTML also: Telerik has in the ASP.NET for Ajax a RadDock. Can we have something like this sort of MDI interface in Kendo
HI Telerik, We are coming over from the AJAX suite and have to say that the demos and documentation are horrible at best. One of the greatest strength we have seen with Telerik has been your demos of almost every variation and sample most people could come by with news ones added quite often. If there wasn't a demo you were almost sure to find it in the Documentation. The last place to look before contacting Telerik is the FORUMS but this is impossible with the way KendoUI forums use the search. It search ALL forums not just the current sub forum and pulls things back like Client Log-in pages etc.. The forum search needs to work more like the Main Telerik Forum site otherwise its impossible to use the forum unless you want to go through each forum page by page The keno UI demos are geared towards just the client side. There is very little show how to do things with the server wrapper for MVC. It would also be nice to show the service code as well for things like the data source read, create, update and destroy events for widgets like the grid etc.. Here is a sample. http://demos.kendoui.com/web/grid/editing-custom.html The demos shows the client side HTML version and if you choose the RAZOR syntax it is a completely different code than what is in the demo above. The lack of documentation makes it very frustrating to use the KendoUI. New features are great but if there isn't adequate documentation to support how to implement then many features will go unused. I hope you guys will take a serious look at the KendoUI Demo and documentation and consider making it an immediate priority to address.
As discussed on the forum (http://www.telerik.com/forums/virtualization-for-treelist) please improve the rendering/scrolling/expanding/collapsing performance of TreeLists with many expanded rows. Grids support virtualization and work well with hundreds of thousands of rows (http://demos.telerik.com/kendo-ui/grid/virtualization-local-data). Perhaps virtualization can be added to TreeLists to achieve similar results?
Currently in Kendo UI if a user sorts a grid column and leaves the page, when they come back the sorting has been reverted. I think there should be a way to automatically save the grids sorting state (potentially in cookies) so that when a user leaves the page and comes back, the state is how they left it.
Ability to take over the default sort and do a custom sort on the grid. This will be really helpful for formatted columns that requires a separate sort logic.
Hi Andrew, Can you give me a scenario where a writable computed observable would be required? As the KO site states, these are very uncommon, mainly because the computed nature of the observable makes them unnecessary. If you need an update, set one or more of the dependent observables, and the computer observable also reflects the change.
It would be nice if you could add a disabled state for k-button. That way, we don't have to hide the buttons from the users to force them to enter some information before clicking a button.
I would really like a ProgressBar control. The reason why I want a progressbar control in kendo ui is so that the look and feel of my application is consistent throughout.
Option to refresh one item from a datasource from the server using a GET request using the transport read url appended with the item ID field value. See: http://www.kendoui.com//forums/framework/data-source/how-to-refresh-an-item-in-a-datasource-with-server-data.aspx
It would be great to be able to simply connect the menu widget to a DataSource to populate. It will allow for a data driven menu, instead of having to handle that logic on the client side.