Geertjan's Blog

  • August 25, 2015

Kendo UI Core in NetBeans IDE 8.1

Geertjan Wielenga
Product Manager

Good news for users of Kendo UI Core, everywhere. Problems in the initial release of the Kendo UI Core plugin have been fixed and, if you're using NetBeans IDE 8.1 Beta (or later), you'll have code completion for Kendo UI Core components, together with documentation, once the plugin is installed:

But... there's more! In code completion, in the place where you'd expect it, you also get code completion for the attributes of the currently used Kendo UI Core component, together with related documentation:

When you're using Visual Studio, you'll miss the above feature, i.e., context-sensitive code completion of attributes of Kendo UI Core components, since it's simply not supported fully or completely or correctly there:

Go here to get the plugin:


Many thanks to a variety of people involved in working on and supporting the Kendo UI Core Editor plugin for NetBeans IDE. In the first place, Johan Borchers for suggesting this feature for NetBeans IDE and also for trying it out multiple times, until we fixed the issues we initially had and now it works for him too in NetBeans IDE 8.1. Giorgio Del Cielo, thanks to you too, for trying out the plugin and reporting that it now works for you. Also, very many thanks to the Brazil team who worked on the documentation parsing of the Kendo UI Core Editor plugin during JavaOne Latin America, consisting of Mauricio Leal, Leonardo Zanivan, and All Pereira.

Many thanks to everyone. And there's still quite some work to be done, especially in the performance and caching of parsing results, i.e., these aspects are not optimal yet. Anyone wanting to get involved, there's a GitHub repo that contains all the code:


Anyone using the plugin, please help by providing any kind of feedback, either here or on the plugin's page in the Plugin Portal.

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.