The Kendo Validator cannot be used with the contents of a bound listview because there isn't a way to give unique names to each input. Knockoutjs handles this via the uniqueName binder: http://knockoutjs.com/documentation/uniqueName-binding.html I wrote a custom binder to accomplish this but it would be nice to have a delivered option. Basically I: 1) locate the parent data-uid and tack that onto the end of the name 2) update all data-for references to match.
Make the html date and time controls match the skins for the native Kendo UI look. This way a form built with Kendo UI will look pleasant across a mixture of html and Keno UI controls. In some cases it would be better to have the mobile style "scroll" to enter dates and times but the look is off putting.
The Drawer widget doesn't work in Intel XDK emulator. It works fine on the device using Intel App Preview, but not being able to select an item from the drawer in the emulator kinda is a show-stopper for navigating the app.
Expand Chrome Inspector to allow easy creation of DOJO. In the Inspector, we can see all the options as well as the data for the widget. The created DOJO should be simple (at least to start), meaning local data and all the options. At the very least, the Chrome Inspector should allow copying of the options and the data so pasting into a DOJO is as simple as possible.
Right now on a mobile device it will put just what it needs into the overflow box. I would like to see the ability to force everything into the overflow when it is activated at all.
It would be great if there was a kendoUI atmosphere package library for Meteor js
Would be nice to have a validator that validates not HTML elements, but model properties (after all when using MVVM HTML is bound to properties). Consider the following scenarios: A property is not directly bound to an HTML input. For example, I have a collection propery and my model is valid only if it contains at least N elements. Or if collection elements have date or time fields, overlaps are not allowed, and so on.
I'm writing a application and would love to have 'pull to refresh' activated when the user swipes up instead of down. In addition, endless scrolling would work when swiping down instead of up. Basically the reverse of how the listview works right now. I see this request often and users end up implementing their own solution.
Polymer support has already been requested but I would like to see Kendo UI support for Polymer.Dart.
Kendo OOXML should allow to give Pattern Style and Pattern Color for cell.
It looks like this was rejected over a year ago, but now that this feature is appearing in other frameworks it would be nice to reconsider. Each tab having its own history is core to making things work like it would in a native app. It is just so sloppy when a user loses their state going between tabs. You are able to do this with the ionic tabtrip http://ionicframework.com/docs/api/directive/ionTab/ so i would hope kendo can too.
We have come across problems where on ann individual vie wit would be good to strip out all the CSS styling on a listview. To do this presently is very difficult to find what styles are applied and when we do remove them it causes problems else where. Ideally it would be nice just to have a attribute on the widget which tells the widget not to use the in built styling.
On data management controls (like the grid and the listview), if they are bound to an ajax remote data source and an error occures, it will silently ignore it and accept the changes. You listen to the error event on the data source to display the messages, but that wont stop it from accepting the changes. You can add a single occurrence listener on the grid's data binding event to prevent it, but you are starting to get into weird hacks. Then theres the listview, which is an even uglier hack. Not only should this be standard behavior in the first place, but it's a pain to even get it to work with hacks. Please change the behavior or at least add an option to prevent accepting bad data that didn't even get saved in the database.
When multiple popovers are supported, clicking on a button to open popover1 should automatically close popover2. Your popover demo demonstrates the problem, but bypasses the pain point by positioning the popover buttons on opposite sides of the form. Often multiple buttons on a Nav bar will cause popovers, which will overwrite portions of each other when multiple are displayed simultaneously. I tried a quick workaround, which didn't work.
Is there any plan to provide WEB API server wrap? If so, we can use it in web and mobile at the same time.
At least, including: 1. Tab stop for mobilebutton, mobilebuttongroup, mobileswitch. 2. Selection support for mobilebutton (spacebar), mobileswitch (spacebar/left/right), mobilebuttongroup (left/right/up/down) MobileButtonGroup and MobileSwitch are elegant replacements for radio and checkbox inputs, but they need keyboard support to improve desktop accessibility.
In Kendo Web - Mobile as ListView - search field should not be scrollable, only listings should be scrollable. If user scrolls down couple of pages down and now he wants improvise the search, then again he has to scroll back to type in search field. If only listing scrollable then search field is always visible where user can type whenever wanted. I dont know how this is missed in the current release. This is very basic.
I need homogenous data items for multilevels in your tree control. Most data structures coming from our services are not homogenous. We use the following to create a homogenous structure for the tree. Maybe you could incorporate something like this - note that we use angular, and I use their $parse service in my implementation: // CALLER: var levelDescriptors = [ { item: "functionGroup", items: "functions" }, { item: "this", items: null }]; itemHierarchy = Portal.buildItemHierarchy( functionGroups, levelDescriptors, $parse); // UTIL CODE: buildItemHierarchy: function(hierarchicalItems, levelDescriptors, $parse) { var hierarchicalDataItems = []; if(Portal.isDefined(hierarchicalItems)) { hierarchicalDataItems = Portal.createHierarchicalDataItems(0, hierarchicalItems, levelDescriptors, $parse); } return hierarchicalDataItems; }, createHierarchicalDataItems: function(level, levelItems, levelDescriptors, $parse) { var levelDataItems = []; if(Portal.isDefined(levelItems)) { if(Portal.isDefined(levelDescriptors)) { if(level < levelDescriptors.length) { for(var i=0; i<levelItems.length; i++) { // extract datasource for current level. // create an associated node data item. var levelItem = levelItems[i]; var levelDescriptor = levelDescriptors[level]; var item = levelItem; if(levelDescriptor.item !== "this") { item = $parse(levelDescriptor.item)(levelItem); } if(Portal.isDefined(item)) { var levelDataItem = Portal.createNodeDataItem(item); levelDataItems.push(levelDataItem); // extract children for current level. // create associated (child) node data items. var items = $parse(levelDescriptor.items)(levelItem); if(Portal.isDefined(items)) { var itemsLevel = level + 1; levelDataItem.items = Portal.createHierarchicalDataItems( itemsLevel, items, levelDescriptors, $parse); } } } } } } return levelDataItems; }, createNodeDataItem: function(item) { return { id: item.id, text: item.name, dataSource: item, expanded: false, items: [] }; },
I'm creating a FAQ for a client and I need the Question and Answers to be collabsable inside a listview but I also need to filter the list by keyword... I would like something similar to the Collapsible Lists in jQuery Mobile: http://jquerymobile.com/demos/1.2.0/docs/lists/lists-collapsible.html
Currently the actions in an ActionSheet can only execute functions defined in the global space as stated in the documentation here: http://docs.telerik.com/kendo-ui/mobile/actionsheet#executing-actions "The callback can be either a function, or a method of a JavaScript object in the global scope." I want to be able to specify a data-model attribute so that the callback for my actions can be functions defined in a kendo observable (more specifically the kendo observable used by my view). This functionality would be similar to how data-model attributes work with modal views. As it is I don't want to be defining functions in the global scope - I consider it sloppy and messy. Does it not makes sense to use the scope of the containing view's model?