Having the ability to create "WYSIWYG Text and HTML Editor" would be excited.
http://www.kendoui.com/forums/integration/integration/kendo-ui-requirejs.aspx
when invoking kedno there is an error 'b is undefined'. You should provide information about which version of jquery is required to run kendo safely.
I use a timebar + sparklines in all our dashboards. http://demos.telerik.com/silverlight/#TimeBar/FirstLook http://demos.telerik.com/silverlight/#Sparklines/Gallery would be great to see an html5 version of the executive dashboard
Buttons that works like checkbox. First click it is on an highlighted second click it is off
What i think of it is converting checkboxes list into more friendlu UI element. For example we have list of checkboxes with the same name but different key Name="checkname[1]" and so on. So i set something like $(".checkbox[name=Checkname]").kendoCeckboxes() Then kendo convert it in to togle buttons. You can set how namy columns for example. And it will convert to something like table with every cell as toggle button and selected options are highlighted. Of course you do not use table html elemnt i just describe idea. This will be more friendly as on desktops as on tablets.
Elements for trivial 2 choice radio buttons like show/hide, Yes/No, etc... Of course i can use radiobuttons but for this trivial task somethong like iPhone on/off button would be more intuitive.
Element to chose color. That is usefull forvisual template bulders and CSS editors and more. I am curently needing this UI
That would be great if you create UI element Ribbon. With automatic buttons scaling on window resize.
For example. I have article and I attached 3 files to it. Now i open article for edit because I want to add 2 more files but delete one. Of course i could make separate list of already uploaded files. But better would be to give to this UI element list of files to be populated on initialization.
Posted 1 hour ago (permalink) Another important thing for upload element is file list template. Somethink like <script id="template" type="text/x-kendo-template"> <div>#= filename #, [#= filesize#] <span class="menu"> <ul> <li>#= button_delete #</li> <li><input class="k-button" value="Insert into text" onclick="insert()"></li> <li><input class="k-button" value="Copy path to bufer" onclick="copy()"></li> </ul> </span> </div> </script> This way i can path either tmplate ID or template object and affect list of files. Because upload is a very important thing nowadays and usually require more options than just upload.
When working with AJAX it's essential to be able to validate a form on the fly, return errors, and deal with them without needing to actually submit the form. Please make sure the validation library works as a callable method rather than just a form submit event binding.
If it is at all possible, please implement drag & drop inside the grid to enable users who need to manually sort items in order of importance (for instance a list of books I they wish to show in certain order).
Please allow for the creation of custom UI widgets and plugins that can be tied closely with the rest of the framework similar to how jQuery plugins work but better ;) Start off by providing good documentation of the different classes (both JS and CSS) that developers can and should use and provide guidelines for writing custom code so third party controls and extensions follow similar style (visually and programatically). Also adding a Kendo Marketplace or something like this where developers can publish their plugins and other can vote/comment on them would be great for everyone. jQuery UI and the plugins that are available there are great but I think Kendo UI and the Kendo community can do better especially if we set the bar a little higher from the get go.
Just test the basic usage sample on the web site. If you are able to set all splitters as you wish, you are the king! All other controls work as expected.
Please add toolbar functionality to the Kendo Grid (similar to the Telerik MVC Grid using custom toolbars - http://demos.telerik.com/aspnet-mvc/razor/grid/customtoolbar). Even if the toolbar has to be using strictly a template-based approach, it will still be very usable to be able to plug toolbars inside the grid itself. I know there is a talk already about custom toolbars and buttonsets in the mobile widgets. Maybe this work can then be applied to the desktop widgets as well? With Windows 8 (and iOS/OS X) moving towards the tablet form factors as well as recent and recently announced laptops and all-in-one desktops being touch-enabled nowadays, having touch-friendly functionality UI elements suchs as toolbars and buttonsets on desktop-class widgets too will makes more and more sense as those new devices start making their ways into consumers' hands this coming year.
Having the ability to create "right mouse click" context menus would be very nice.
We find with lots of UI vendors put up cool demos, but rarely a more realistic view. We like to see the controls in a LOB style layout with: 1. A Purchase order where you enter PO#, Date, Customer (Autocomplete), Customer Name (as result of autocomplete select), ShipToCountry. 2. Order lines (grid or other) with ProductID (autocomplete which then populates description and price), Quantity (which in turn calculates line price). 3. As a result of ajax submit, the server side validation returns error saying order value exceeds customer limit AND ShipCountry not valid for this customer. So the form displays message "Exceeds customer limit" and ShipToCountry input is highlighted with error message "Not valid for this customer". And make it look good!
The current drop-down list works great. However, in situations where the options are hierarchical there are (at least) two obvious solutions. 1) Have two drop-down lists (perhaps with some js altering options based on selections). 2) Display a tree of options from the drop-down. (much like a menu) Here is an example of #1 http://www.jgeppert.com/jquery-doubleselect/ Here is a very good example of option #2 http://www.givainc.com/labs/mcdropdown_jquery_plugin.htm The advantage to #1 is that you can easily fire off js after selected options. The advantage to #2 is that you can determine all available options on the server and return a structure for rendering. Also, #2 does not take up more screen real estate. I think addressing these interface scenarios would help Kendo become even more usable than it already is. Thank you.