This article provides a collection of the most frequently asked questions (FAQs) and answers related to the Kendo UI suite for Angular 2.
The R3 2016 release of Kendo UI for jQuery will be available in the next version of AppBuilder. The tooling will provide tooling and service integrations with Angular 2 for both hybrid and native applications.
Currently, Kendo UI for Angular 2 is available as a beta release. At the moment, the integration of Kendo UI for Angular 2 in Telerik Platform through AppBuilder is not announced yet.
Are Kendo UI planning to extend the current API for already implemented components such as the Button and DropDownList components?
Kendo UI are always seeking the improvement of the APIs for existing components. For example, in the latest release of Kendo UI for jQuery, the API for the Upload widget is improved and the widget now supports common use-case scenarios such as dragging and dropping custom drop zones. New callbacks to respond to events that are associated with user actions are also added.
Currently, Kendo UI Builder supports Angular 1.5. At this time, Kendo UI have not announced any plans for the Kendo UI Builder to support Angular 2.
Kendo UI for jQuery supports both configurations. In the R1 2017 release, Kendo UI plan to introduce two new Sass themes for Kendo UI for jQuery—Default and Bootstrap v4. These will be integrated and available for Kendo UI for Angular 2 in the RC.0 release.
When are you planning to release a NumericTextBox, MaskedTextBox, and DatePicker components for Angular 2?
The NumericTextBox, MaskedTextBox, and DatePicker components are scheduled for delivery in the RC.0 release on January 18, 2017.
For more information on any future developments, refer to the Roadmap page of Kendo UI for Angular 2.
When can I expect the same level of maturity and completeness in Kendo UI for Angular 2 as in kendo UI for jQuery?
The plans for the future development of the new Kendo UI for Angular 2 suite are published and will be regularly updated on the Roadmap page.
Kendo UI for Angular 2 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 is shipped by Kendo UI for jQuery.
Kendo UI for Angular 2 provides support for all browsers supported by the Angular 2 framework.
How do I use npm within an organization as it cannot have the users' passwords stored in a source control?
Passwords do not need to be stored in plain text. NPM uses authentication tokens that can be set either through an environment variable or an
npmrc file. For more information, refer to the blog post on deploying with npm private modules.
Receive notifications from npm through hooks.
Yes, you can.
As of the 2017 Q1 release, you can include the Kendo UI components for jQuery in Angular 2 applications. To style your project, use the new Default theme—it is compatible with the Kendo UI components from both suites.
For detailed information on how to convert your AngularJS knowledge into Angular 2 mastery, refer to the migration guide on Angular 2.
It depends on what version of Angular you are currently targeting. For detailed information, refer to the migration guide on Angular 2.
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 2.
To get ready for the future migration to Angular 2 and Kendo UI for Angular 2, 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 2 suite are documented. All API configurations that made sense to migrate to the new suite are preserved. However, the approaches Kendo UI for Angular 2 uses towards major features, such as databinding, are different.
Yes, you can.
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 2 to work with Visual Studio, refer to the documentation by the Angular 2 team.
To integrate Kendo UI for Angular 2, follow the steps outlined in the article on getting started with Kendo UI for Angular 2.
Yes, they are.
The Sass themes are intended for adding to the next releases of the Kendo UI for jQuery and Kendo UI for Angular 2 suites.
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 2 support the same attributes, such as header attributes, row templates, as the Kendo UI Grid for jQuery?
No, it does not. Some Grid features are not supported by Kendo UI for Angular 2 yet. Such features will be added once prerequisite components, such as the DatePicker, are built.
The RC.0 release of Kendo UI for Angular 2 will add components that are required for the Grid to support operations such as filtering and editing.
No, they are not. Grid features, such as filtering, are not currently available in the beta release of Kendo UI for Angular 2. The reason for this is the missing prerequisites, such as the DatePicker component that is planned for shipping with the RC.0 release on January 18, 2017.
Yes, it is.
All components support Ahead of Time compilation without requiring additional steps.
Can I use Kendo UI for Angular 2 in Universal (isomorphic) applications?
Yes, you can.
The components work in Universal Angular 2 projects with the following limitations:
Server-side rendering is limited to the available data at the time of rendering.
The Charts do not render on the server.
Yes, you can.
This approach works well for developers willing to use ASP.NET Core, Yeoman, and Angular 2 with Kendo UI.
You can use Kendo UI in Visual Studio Code today. Features, such as statement competition, are supported by Kendo UI for Angular 2 through TypeScript.
To learn the steps on setting up such a project, refer to the article on getting started with Kendo UI for Angular 2.
The beta release of Kendo UI for Angular 2 is the initial offering of Kendo UI. The RC.0 release scheduled for January 18, 2017 will provide more features and new components.
Is it easy to use a single-code base to target desktop and mobile platforms when using Kendo UI and Ionic?
Angular 2 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 2 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.
However, Kendo UI do not plan to have a DataSource component in Kendo UI for Angular 2. Having a DataSource component, such as the one in the Kendo UI for jQuery suite, does not fit well in the Angular 2 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 2 with an event handler that will debounce, query an API, and update the member bound to
[data] with the results.