Currently it does not support group/ungroup excel feature using kendo.ooxml.Workbook. Please refer http://prntscr.com/iykrqy for more detail requirement.
For Vue components, the v-model on a multi-combo box and every component must bind to the underlying object. :value-primitive="false" doesn't work as per some suggestions. v-model binding to the underlying object is a MUST HAVE, Top priority, number one with a bullet. Without it, your components are a PITA to use and my current proof of concept might end here and we won't use your components with some bigger projects coming down the line.
I'm trying to export the kendo-ui platform into the golang programming language and would like to know if the kendo-ui documentation exists in some other format easier to handle. At the moment, I made a robot that goes into the documentation, filters the hml and assembles the corresponding code in golang, but I would like to be able to optimize the process. https://godoc.org/github.com/helmutkemper/telerik https://godoc.org/github.com/helmutkemper/telerik#example-KendoUiDialog-String https://godoc.org/github.com/helmutkemper/telerik#example-FrameworkForm-ToForm https://godoc.org/github.com/helmutkemper/telerik#example-FrameworkForm-ToScript
There are many properties that can be set during initialization that cannot be changed through the API afterwards. Take the Kendo UI ToolBar for example. You can add a button to the toolbar and set the text, but you cannot change the text afterwards unless you update the element directly. It may seem like a simple thing to change the text of an element, like so: $("#myButton").text("New Text"). However, if you had set the imageUrl as well, setting the text like I did above would remove the image. Knowing that, you could get the text node and update the nodeValue. That may work today but could easily be broken during a Kendo UI update (for example, if the update included a change that wraps the text in a span). Having to deal with native elements after they have been created by the Kendo UI components is a dangerous practice for developers as it requires an internal knowledge of how elements are rendered based on the different options set. As mentioned above, it is also dangerous as any update could break our code. Therefore, it is imperative to expose methods that allow us to modify any properties through the API (where possible) to allow us to create clean and easy to maintain code. If you search the feedback, you will see many requests to add a method here and a method there. There is even a related one to this called "Kendo Mobile: Methods to set properties dynamically". Suggestion: When you have child elements, such as buttons on the toolbar, please allow us to update those widgets directly rather than through the parent. For example, instead of $("#myToolbar").data("kendoToolBar").enable("#myButton"), allow us to do something like this $("#myButton").data("kendoToolBarItem").enable();
It would be nice to have the option to add new rows at the bottom of the grid, just like Jquery grid has that option "createAt": "bottom".
We'd like radial gauges to have pointers we may customize, and/or to have a variety of pointerType settings, e.g., a marker that follows the circumference next to the scale; a custom image or shape that may be imported in place of the standard needle, such as the outline of a boat for heading.
currently is 1px to 1pt mapped in the kendo.drawing.drawDOM method. Actually, this should make it simpler, as described in https://docs.telerik.com/kendo-ui/framework/drawing/drawing-dom#dimensions-and-css-units Unfortunately, this prevents the use of the units cm, in, mm and pt.
It would be very useful from a visual and functional perspective to be able to view scheduler items in a multi-year view, that seems to be currently unsupported.
Please add the multiple date selection option to the kendoDatePicker component as for the kendoCalendar. It would be useful in the table column header to filter date values. Currently, I have to use two DatePicker to select min and max date. Calandar is not an option in my case.
Indeed today, to correctly display red or other points depending on the template, it is necessary to make lines of codes so that the rendering is present. It should be done automatically as soon as the array of dates changes (as it is linked to the calendar), I'm talking about the small calendar that is in the header of the scheduler.
Kendo UI jQuery Scheduler: grab a task (appointment) to cells, without displaying the lines of separation. Set an interval property for the drag and drop, which will be defined, 15 or 30 minutes or even smaller, without necessarily having to display the lines of separation (minorTickCount) increases in this case the height of the cells.
All the themes has Mobile support except the kendo.bootstrap-v4, we need the mobile support for new bootstrap v4. current bootstrap 4 css : https://kendo.cdn.telerik.com/2017.3.1026/styles/kendo.bootstrap-v4.min.css Expected Mobile Support css : https://kendo.cdn.telerik.com/2017.3.1026/styles/kendo.bootstrap-v4.mobile.min.css
tabstrip in mobile device easy to use for client if tab is scroll on touch instead of arrow button of left and right