Hi,
We are currently in the process of redesigning our front-end and are currently learning towards using Vue. We use Kendo extensively throughout our application so integration between the two will heavily influence our final decision. With that said what are some of the current limitations with the Vue wrappers? I noticed on some component demo pages specific functionality is left out (like the Grid). Is it because this functionality isn’t available in the wrapper or just a demo hasn’t be made to showcase it yet? Also what are the performance implications of being a wrapper and not a native component? I am not expecting numbers but is the performance difference between say a React native component and a Vue/React wrapper that noticeable in a real world scenario?
Thanks
8 Answers, 1 is accepted
One of the benefits that the Kendo UI for Vue wrappers provide is parity with the jQuery widgets - all of the jQuery widgets and their respective API options can be used in their Vue counterparts. This on the other hand allows to easily translate the jQuery implementation to Vue, by transforming the jQuery API options to props. Here is the relevant documentation to get you started:
Concerning the available demos in the Vue website - we are currently in the process of improving the documentation resources and adding new demos for every component. We are gradually releasing the new content. For example, you can check out the new 30+ Grid component examples that were just added:
On the topic of performance - the Kendo UI Vue components are wrappers around the jQuery widgets and as such they contain additional logic that is used to make the components support the native Vue reactivity. This is basically what causes the performance difference when comparing native components versus wrappers. In terms of a real world application, there should not be a noticeable difference. I would suggest to setup a complex page with the Kendo Vue components in order to test and verify that the performance matches the project requirements.
In addition to the above, you might also find the following resources useful:
Regards,
Dimitar
Progress Telerik

Hi,
We are in the same boat as Trevor above - and we started mapping our transition to Vue with KendoUI - one of the things we have noticed is that there is no wrapper we could find for the scroll-view component. Is it not supported within KendoUI for Vue - or am I missing anything?
The ScrollView is part of the Kendo UI Hybrid suite and those widgets are currently not implemented as Vue components. I would suggest to add this as a feature request in the Kendo UI Feedback Portal, so that we are able to evaluate the users demand.
Regards,
Dimitar
Progress Telerik
The ScrollView is part of the Kendo UI Hybrid suite and those widgets are currently not implemented as Vue components. I would suggest to add this as a feature request in the Kendo UI Feedback Portal, so that we are able to evaluate the users demand.
Regards,
Dimitar
Progress Telerik


Hi,
We are currently in the process of redesigning our front-end and are currently learning towards using Vue. We use Kendo extensively throughout our application so integration between the two will heavily influence our final decision. With that said what are some of the current limitations with the Vue wrappers? I noticed on some component demo pages specific functionality is left out (like the Grid). Is it because this functionality isn’t available in the wrapper or just a demo hasn’t be made to showcase it yet? Also what are the performance implications of being a wrapper and not a native component? I am not expecting numbers but is the performance difference between say a React native component and a Vue/React wrapper that noticeable in a real world scenario?
Thanks
[/quote]
Hi Trevor, how did you solve this?


[quote]We are still prototyping but most likely going to use the Kendo Vue wrappers. We are going to try some native alternatives for more complex components to see if there are any noticeable performance.
[/quote]
That's actually very cool.