This article provides a collection of the most frequently asked questions (FAQs) and answers related to the Kendo UI suite for Angular.
When can I expect the same level of maturity and completeness in Kendo UI for Angular as in Kendo UI for jQuery?
The plans for the future development of the Kendo UI for Angular suite are published and regularly updated on the Roadmap page.
Kendo UI for Angular is a new addition to the Kendo UI family of commercial products. When the product is officially released in 2017, it will be backed by the same level of professional support and scheduled updates that are shipped by Kendo UI for jQuery.
Kendo UI for Angular provides support for all browsers supported by the Angular framework.
New releases of Kendo UI for Angular are announced on the Telerik blog.
Subscribe for NPM notifications through hooks.
Yes, you can.
For more information on how to use the components side by side, refer to the help topic on integrating Kendo UI for Angular with Kendo UI for jQuery.
No, you cannot.
To style your project, use either of the themes that ship with Kendo UI for Angular—Kendo UI Default Theme or Kendo UI Bootstrap Theme. Both themes are compatible with the Kendo UI components from both suites.
To create a theme that matches the looks of your desired project, you can also use the ThemeBuilder application.
For detailed information on how to convert your AngularJS knowledge into Angular mastery, refer to the migration guide on Angular.
It depends on what version of Angular you are currently targeting. For detailed information, refer to the migration guide on Angular.
Yes, it does.
Kendo UI for jQuery is the same product it has always been. The Kendo UI for jQuery name was given to the suite to differentiate it from Kendo UI for Angular.
To get ready for the future migration to Angular and Kendo UI for Angular, target Angular 1.5 and Kendo UI for jQuery.
The conceptual aspects as well as the API calls of each component from the Kendo UI for Angular suite are documented. All API configurations that made sense to migrate to the new suite are preserved. However, the approaches Kendo UI for Angular uses towards major features, such as data binding, are different.
Yes, you can.
The Default theme can be customized.
Why do I have to include the CSS for Kendo UI components? Why are CSS not included in the
@Component that is created?
Both approaches are possible. The inclusion of the CSS at the component level allows the style encapsulation of the native or emulated Shadow DOM.
To set up Angular to work with Visual Studio, refer to the documentation by the Angular team.
To integrate Kendo UI for Angular, follow the steps outlined in the article on getting started with Kendo UI for Angular.
You can customize the styles by using CSS overloads or Sass. For more information on the styling options, refer to the introductory article on themes and styles.
Not at this time.
Server-side operations are supported through the Angular HTTP client and endpoints that accept query string options. For more information, refer to the example on using server sorting and paging through an OData service in the Grid.
Does the Kendo UI Grid for Angular support the same attributes, such as header attributes and row templates, as the Kendo UI Grid for jQuery?
No, it does not.
Some Grid features are not supported by Kendo UI for Angular yet. Such features will be added once the prerequisite components, such as the DatePicker, are built.
No, they are not.
Grid features, such as filtering, are not currently available.
However, Kendo UI do not plan to have a DataSource component in Kendo UI for Angular. Having a DataSource component, such as the one in the Kendo UI for jQuery suite, does not fit well in the Angular context. The framework already provides most of the DataSource functionalities such as the ability to fetch data, change tracking, and others. You can also use other libraries and patterns for working with data.
The ComboBox component supports a primitive AutoComplete-like functionality as well as binding to an asynchronous source. It is possible to bind to the
filterChange event of the Kendo UI ComboBox for Angular with an event handler that will debounce, query an API, and update the member bound to
[data] with the results.
Yes, it is.
All components support Ahead-of-Time compilation without requiring additional steps.
Yes, you can.
The Kendo UI components for Angular work in Universal Angular projects.
Yes, you can.
For general information on how to use Angular in ASP.NET Core, see the official Angular guide.
For information on how to bind data from ASP.NET Core to Kendo UI for Angular, refer to the DataQuery integration with ASP.NET Core help topic.
Is it easy to use a single-code base to target desktop and mobile platforms when using Kendo UI and Ionic?
Angular facilitates the use of the “underlying plumbing” for your application that will be used across platforms. However, to target mobile, it is advisable to use NativeScript. For more information on migrating hybrid applications to native, refer to the guide on upgrading hybrid applications to native with NativeScript.
The Kendo UI Grid for Angular relies on the built-in browser scrollbar. For more information on how to style the scrollbar in Internet Explorer, WebKit (Safari, Google Chrome), and Opera, refer to this issue on Stack Overflow.
No, you cannot.
You have to import each component separately.