In the long term, SPA features are absolutely necessary, especially when it comes to HTML5 apps (also in regard to Windows 8 WinRT or upshot.js - a key part of the forthcoming Microsoft RIA stack). A good SPA addresses the following issues: - real permalinks - page titles - a working back button that fully degrades - different data states like http://bit.ly/zpybmz - client side caching - asynchronous updates/communication - ...what else? (please add if I missed something) Example SPA: http://pjax.heroku.com/
I think as we try to create more RIA with HTML5, having multi column dropdown is very intuitive Similar example: http://demos.devexpress.com/aspxeditorsdemos/ASPxComboBox/LargeDataSource.aspx
With the release of TypeScript by Microsoft it would be great if there would be a definition file for the different Kendo Libraries. I actually played around with it myself, implementing some basic functionality from the core and the Calendar widget. This is by no means complete or error-free, but it gives an idea of the possibilities. I was able to get all the nice features TypeScript has to offer (e.g. type checking, auto completion).
Tooltips which can be attached to elements to provide additional information on hover. Could either be taken from the title attribute, a string or a specified element. Can provide additional styling and interactions going beyond the current restrictions of browsers title hover.
KendoUI has window widget, but it's too simple, I suggest just like jbox or artDialog. jbox:http://kudystudio.com/jbox/ artDialog:http://www.planeart.cn/demo/artDialog/index.html
TabStrip: Add vertical tabs and activate tab on hover mouse (see the JQuery UI Tools from flow player)
Combob support for paging would show use the datasource paging settings similar to the grid control and show a label at the bottom as you scroll (Ex. "Displaying 10 of 100 items) and as you scroll increment the items in the list by the configured page size from the datasource.
A TreeView in ComboBox would be most helpful as both a stand-alone control and when editing within the Grid. something like this: http://www.brad-smith.info/blog/archives/193 (example from .NET Windows forms world) * Used for relative small tree data structure. * User may select one (many) item(s), without _loosing context_ (no interrupting dialog box, 'flat' interface). * User may accept selection by click on item, or pressing 'enter'. * User may cancel (hide) popup when click outside control/popup (ie in another control, that received focus) or pressing escape - like in combobox/dropdown. * It will be nice if user can select items using keyboard arrows. * After opening popup or selecting item, widget still has focus * When user types in combo (with open popup), data should be filtered. * No additional 'ok' or 'cancel' buttons to accept/dismiss selection.
Reopen from http://kendoui-feedback.telerik.com/forums/127393-kendo-ui-feedback/suggestions/10600184-grid-in-combobox Details about this widget were described in user comments.
Please consider adding a sample Line-Of-Business (LOB) application to your demo page. This more complex LOB app demo should show KendoUI widgets working together. Here are a couple ideas: - TabStrip contents containing Grids, Graphs, complex entry form, or another nested TabStrip. - Window having other nested KendoUI widgets in its content. - Nested wigets should 'lazy' load or load on demand? - MVVM events wiring between widgets? We're new to KendoUI, and it would really help to see how a proper LOB app powered by KendoUI is built, especially with that cool MVVM. Thanks.
My number one suggestion for Kendo UI would be a Kendo UI kind of bootstrap / foundation. We all know Twitter Bootstrap and Zurb Foundation. The main advantage of these html frameworks are in my opinion: #1. Rapid development of layouts #2. html elements are supported (forms, tables, buttons) #3. Reponsive (and in some cases fluid) grid. #4. Usuable threwout the internet (ie, firefox, chrome, safari etc). #5. User Friendly to start and work with. In the first place I am not suggesting to integrate one of those (that would be my second..) My first suggestion is, make one of your own (fork it or what ever? to start) So that we have not only a html foundation of the project, the elements are also fully integrated with each other. So you can have one uniform theme threw out the whole website / project. So.. That is my first suggestion, and ofcourse the second one related to this one is, when you guys dont want to create your own, integrate a (lets call it css/html framework) that is fluid (because in my opinion, kendo ui is really for business software, and with fluid width you can have more information on your screen..) Hopefully you take this suggestion in consideration. It would really make a different!
It would be great if it is possible to disable certain dates in the calendar. Maybe if it is possible to pass an entire array with calendar-date-objects, it would be more convenient to disable dates or highlight certain dates. e.g. CalendarDateObject could have 3 properties: - CSS class (this style would be applied to that certain date) - Disabled true/false; default = true (if disabled, date is not clickable) - Footer text (When you hover over the date, you can see this text in the footer) By using an array of objects, you don't have to check if a date is in a certain array to change the CSS-class of that date. In the way it is now implemented, you have to write all lines of code to check if the date is in an array.