We were really happy to celebrate Kendo UI's fourth birthday in this fun party-themed webinar, which showcased everything new in Kendo UI for this quarterly release. Notably, we demoed the brand new spreadsheet widget, and showed integrations with Telerik's document processing libraries, new app templates for MVC and new scaffolding for the scheduler widget. We also discusssed Angular 2.0 and Web Components, and how they will integrate with Kendo UI in the near future. We demoed new data visualization features and showed off the new Nova theme too. It was a busy hour but we got through it! You can view the video below, and make sure to watch it to the end for Cody's big surprise.
We're always happy to hear your feedback, which you can submit on our feedback portal. You can also send us a support ticket if you are a customer.
Our code samples have been posted on Github as well.
Below we've answered some additional questions that we received about this release.
Q: Is ReactJS support on the roadmap for 2016? It’s kind of a big deal.
A: It is on the roadmap. We are looking very closely at React.
Q: Please support Shadow DOM.
A: Web Components are supported. However, integrating with Shadow DOM would require Kendo UI to be re-architected. It's something we're considering how to approach.
Q: Are the Kendo methods as robust as JQuery methods?
A: Yes, they are the same methods but they are just not inherited the same way.
Q: Hi, does spreadsheet support Italian dates and numbers format like dd/MM/yyyy and #.##0,00?
A: Yes, the formatter is very flexible and works great with dates.
Q: How does the spreadsheet perform with hundreds of thousands of rows?
A: Very well. You can control the number of rows via configuration. It's smooth with many thousands of rows.
Q: Can we load XLS/XLSX files, such as importing data from an existing spreadsheet and save to a database?
A: Yes, we have a demo here. This is for server import/export. Client-side import is coming in 2016. Saving to a database is something you would have to implement.
Q: Why use Excel in the browser? Why not just use a standard document workflow?
A: There are several reasons for this use case. Maybe you don’t want users to have to have an Office 365 account to access a spreadsheet. You might want them to be able to export data from a backend system to Excel. Or you just want to provide a familiar editing interface.
Q: Are there row limits with the spreadsheet? Older Excel has a limit of 65k rows.
A: By default, the configuration sets the number of rows to 200. However, you can change this to something else, including beyond 65,000.
Q: On the spreadsheet, can you print directly from the web?
A: Yes. However, you may wish to export to PDF beforehand, which is something we support.
Q: Can you copy/paste from Excel into the Spreadsheet widget?
A: Yes, we have a demo for this here.
Q: How about i18n support for localizing the spreadsheet controls?
A: Localization is supported by including localization scripts before instantiating the widget.
Q: Can you freeze rows in the spreadsheet?
A: Yes, the spreadsheet allows a setting for frozen rows and columns in the widget when initializing it.
Q: Can you export the Gantt to a MicroSoft project?
A: No. Right now you can only save as PDF
Q: It would be really nice if we didn’t have to manage all those script and style dependencies!
A: We agree! This is usually best handled by tools such as Webpack or RequireJS.
We have picked 100 winners of the Kendo UI T-shirts based on your awesome tweets, and we will be emailing you about getting those to you in the next few days.
The winner of the iPhone 6S for the best feature suggestion is Robert Rafferty!
The winner of the iPad + Pencil + Smart Keyboard is Loc Nguyen! Congratulations!
Jen Looper is a Developer Advocate at Telerik. She is a web and mobile developer and founder of Ladeez First Media which is a small indie mobile development studio. In her spare time, she is a dancer, teacher and multiculturalist who is always learning.
Copyright © 2016, Progress Software Corporation and/or its subsidiaries or affiliates. All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks or appropriate markings.