We create a dashboard like this:
We need to export in PDF format and we use the component:
Now we need to export in PNG or JPG format.
And this is our request: a Kendo Component that exports a dashboard with the same quality of the PDF component.
Thanks in advance.
It would be great to have a clear button in the DatePicker, as today erasing value requires 3 select-delete operations (one for the day, one for the month, and one for the year)
It would make it consistent with TextBox, ComboBox, MultiSelect & AutoComplete, which renders in a comparable way
The Spreadsheet component is among the last components in the Kendo UI for Vue suite that is available only as a Wrapper component.
Providing a Native version of the Spreadsheet will be a big improvement to the suite.
The current implementation of the Native Grid doesn't support the row reordering functionality when the Grid is configured to work in virtualization mode.
Please provide the row reordering functionality in a scenario with virtual scrolling.
The current implementation of the Kendo UI for Vue Native Scheduler doesn't provide the 'Date Grouping' option that is available in the Kendo UI for jQuery Scheduler component.
Providing the discussed 'Date Grouping' option will make the Vue suite consistent with the jQuery one and will help the users in the migration of their projects from Wrapper to Native Scheduler.
so the orgChart generates a great organizational hierarchy, but I want to be able to drag and drop elements to other parents like you can do with the Asp.net ajax version of the orgChart. How do I do this please?
I would like to offer some suggestions for a few new icons to be added to the Progress Design System. I am currently trying to replace other libraries with the Kendo UI for Vue components, and these are a few icons I use for which I could not find a suitable replacement in the ones you provide. Please see the attached image for examples.
Also, it would be nice to have a "filled-in" version of some of the existing icons. For example, some current icons like "file-add" or "comment" are good, but they don't stand out at a smaller size. Having a solid color version (instead of just an outline) would provide options for bolder colors and make them more visible.
In the current implementation of the GridColumnMenuCheckboxFilter component when its searchBox prop is set to true, the input that appears filters the component's values using the "startwith" filter operator.
Providing a property that can define the filter operator of the searchBox inside the GridColumnMenuCheckboxFilter will be a very useful feature.
The change event of the DropDownList is emitted when navigating between DropDownList options using the keyboard.
The DropDownList should have a select event like it is in other Kendo UI suites and this select event should be emitted when using the keyboard with an expanded popup. Once a value is selected with, for example, click or 'Enter' press, then the change event should be triggered.
With the current implementation of the Native Stepper component, the way we can show/hide a step is by filtering its items.
Providing a "hidden" option that controls the visibility of the Stepper's Step will make the work with the component easier.
Nuxt 3 has a robust module system, which is highly beneficial for importing components easily. I have previously used modules like element-plus, headlessUI, and Vuetify. However, as we are currently transitioning to Kendo UI, we have encountered difficulties in finding a similar module. It is essential for us to be able to import Kendo UI components seamlessly and efficiently. Therefore, we have developed a module similar to the one for element-plus. During the process of writing and testing the code, everything has fallen into place. However, we have encountered an issue with importing the UI DropDownList from the module. It would be greatly appreciated if Kendo UI could provide an official Nuxt 3 module.
out test module
KDropDownList not work but else compoents work good.
Currently, the Stepper's Change event, event handler contains only the index value of the selected step.
Providing the object that defines the specific step, inside the event handler's object, could help in the implementation of different scenarios.
The current implementation of the Native Grid doesn't provide the option to access its messages and use them in custom scenarios like Column Menu templates.
Providing the option to take the components' messages would be a nice to have feature.