Q: Are these wrappers or new controls that are native React UI components?
A: These are wrappers. However, they have equivalent support compared to native implementation, including props binding, state management, custom components, and more.
Q: Can Syncfusion controls be used with web tools outside of React?
Q: Why does it reference deprecated modules?
A: This was a bug, but it has been resolved now.
Q: Will this cover any WPF application builds, or is it only a web-based discussion?
A: This is only a web-based discussion.
Q: Is it good practice to customize Syncfusion components as needed?
A: Yes, you are welcome to do that. Our components can be customized using templates and events. Templates can be used to customize their UI appearances and events can be used to customize their behaviors.
Q: Can I create a custom component which is an abstraction of a Syncfusion component?
A: Yes, you can do this. If you need to group multiple components or you have multiple customizations for a component, such as adding templates and events, you can create a custom component and reuse it across your application.
Q: Suppose I want to add a functionality which isn’t available in a Syncfusion component. What would be the best approach: customize the component file, or create a custom component to be the wrapper around a Syncfusion component?
A: If you need new functionality that is not possible with our public APIs, it is best to create a support incident for it and get ideas from our team.
Q: Let’s say I customized a component. What will happen when I update the package in the future? My code gets overwritten, correct?
A: If you used only public APIs of EJ2 components, you would be safe. These would not be overwritten or broken.
Q: Do Syncfusion controls work on mobile devices?
Q: Can your Angular/JS tools be used with the Ionic framework?
A: Yes, they can be used with Ionic.
Q: Will customization degrade app performance?
A: No, customization will not degrade performance, although incorrect usage could. If you do encounter a performance issue, please create a support incident with code samples so that we can address the problem.
Q: Is the diagram control going to be included in Essential JS 2?
A: Yes. A preview is already available in the Volume 2 release.
Q: What are the required system configurations for developing React.JS applications?
A: Node.js, npm, and any IDE.
Q: What is the purpose of webpack?
A: Webpack is for bundling script and CSS files.
Q: Will the kanban control be available, and if so when?
A: It is planned for a 2019 Volume 1 release.
Q: Is Essential JS 2 Reactive native for developing mobile support apps?
A: No, Essential JS 2 requires a web browser to render component. So, it is not supported in React natively.
Q: Will JS 2 be generally API compatible with JS 1? (Except for new features, of course.)
A: No, we don’t have API compatibility with JS 1.
Q: Will the tree grid control be available, and if so, when?
A: The tree grid control is planned for our 2018 Volume 4 release.
Q: What about the pie chart control?
A: It is already available. Please check our sample browser. https://ej2.syncfusion.com/16.1.32/react/demos/#/material/chart/default-pie
Q: Is there a navbar control? I didn’t see one in the docs.
A: Please find the documentation link here. https://ej2.syncfusion.com/16.1.32/react/documentation/sidebar/
Q: Is there Aurelia integration?
A: Currently, we don’t have any plans for Aurelia.
If you liked this post, we think you’ll also enjoy:
- [Ebook] React.JS Succinctly
- [Ebook] Angular 2 Succinctly
- [Ebook] Node.JS Succinctly
- [Blog Post] Essential JS 2: Effective Ways to Utilize Responsiveness in the Angular Grid
This post was originally published on April 27, 2018.