17 Answers, 1 is accepted
we will consider the scheduler component in the second half of 2017, once we are done with the angular 2 essential set of components - grid and forms. Most of these are prerequisites for the scheduler anyway.
Telerik by Progress
Thanks for answering. :) The problem is that my customer doesn't want to wait till you release Sheduler.
What if I add Kendo UI for jQuery into my Angular 2 app? I already have Kendo UI for Angular 2 integrated into the app. I use Grid, Calendar, Chart controls along with DataQuery.
Do you think both Kendo for jQuery and Kendo for Angular 2 are able to work side-by-side in the same project?
mixing jQuery widgets with the native Angular components should work in general, but we don't provide support or recommend it. There are plenty of limitations with this approach which is the reason why we chose to start with the native approach.
Telerik by Progress
What did you end up doing? Did you have success mixing the jquery version? Would you like to share your experience ?
A bit painful, but in general it works. I had to add some crunches to fix styles interference between both the frameworks.
I have jquery/kendo Pivot, Grid, Date/Datetime picker working side-by-side with Kendo for Angular 4 framework in my Angular CLI project.
There is a step-by-step tutorial, and a sample application in the following section of our documentation:
As already discussed, integration is possible, but comes with certain limitations, and is not officially supported.
Any updates for the scheduler component for Angular 2? This component is critical to our healthcare project? As we're in the second half of 2017 has the scheduler been considered For Angular 2, React, or Vue? Any advise greatly appreciated.
Unfortunately the Scheduler component is not a part of our immediate plans, but instead is a part of our long-term strategy:
The situation is similar for the Kendo UI for React and Vue suites, but they are in much earlier stages of development, and currently only wrappers for some of the Kendo UI for jQuery widgets are available:
Native elements for React are planned for January, but initially only the basic components such as the Grid and Inputs will be introduced.
Currently, the only available approach is to use the Kendo UI for jQuery Scheduler in the Angular application, as previously discussed, and explained in the following article:
In general, our roadmap and priorities depend largely on the business value and customer demand for specific components and features.
However, I would like to present you an offering that may be relevant and applicable to your needs - our Feature Acceleration program.
It allows a customer to negotiate a certain component or functionality to be implemented on demand or sooner than our roadmap implies.
Feature acceleration fits well in scenarios where a feature or enhancement is important for an application's success, but it is not planned to be available at the time of the application's completion.
Let me know if you are interested in pursuing this option at any time and I will put you in touch with our Professional Services team to discuss your exact specifications and possible timeframes.
Thank you for your reply and I'll put together something for the Feature Accelerator as it relates to healthcare, obviously critical for patient scheduling. However scheduling in general is import for all team based initiatives as well.
The reason for my question was in part based on my reading the following Telerik blog, http://www.telerik.com/blogs/have-it-your-way-with-the-r3-2017-kendo-ui-release.
For React and Vue is saw the following and wondered since both are using wrappers I could therefore use the scheduler as noted in the blog statement below:
"This initial release of React and Vue support are an official set of wrappers around Kendo UI that gives immediate support for the large set of Kendo UI components that already exists. The Grid, Scheduler, and many of your favorite widgets are all available with this release."
Is this saying for React and Vue using wrappers would give us access to all components including the scheduler? Been thinking of taking a shot with Vue for a project and if I can use the scheduler this may be the one to start.
Both React and Vue wrappers have scheduled the release of currently missing wrappers for several Kendo UI for jQuery widgets for their next major release in mid-Januyary.
The widgets that the focus will be on are TreeView, ListView, Editor and Charts, while the Scheduler and TreeList are next in the line, and the teams are aiming to provide them in January as well (but it is not yet certain).
Currently the most time-efficient solution seems to use the Kendo UI for jQuery scheduler in an Angular application along with the native Angular components that are already released.
The following section of our documentation, mentioned in one of the previous posts as well, demonstrates using a Kendo UI for jQuery Scheduler in an Angular application:
Of course, the Feature acceleration program remains an option as well.
I cannot commit to a specific timeline, as the Scheduler still remains a part of our long-term plans:
... but as we understand that it is one of the most desired and business-critical components, we will do our best to start initial R&D this summer.
Probably more information will be available after our next official release, scheduled for May.
We will update our Roadmap accordingly once we fulfill our immediate priorities and start working on the next series of more complex components like the Editor and the Scheduler.
we are very happy that you will start initial R&D, but we took a decision to start migration to Angular version as you write some time ago that Scheduler should be available end of 2017, and it looks like that will have 1 year delay?
i think that quite big number of developer did the same :-)
we were start using your components maybe even 10 years ago and you never ever had so big delay,
thanks and best regards, jakub
Indeed, when we first introduced the Kendo UI for Angular suite, providing a dedicated Scheduler component was among our more immediate plans, but as described in the disclaimer, published in our Roadmap page:
"We operate in a dynamic environment, and things are subject to change. The information provided is intended to outline the general product direction. It is intended for informational purposes only and should not be relied upon when making any purchasing decision. We may decide to add new components at any time depending on our capability to deliver products meeting Progress quality standards. The development, releases and timing of any features or functionality described for Progress products remains at the sole discretion of Progress. The roadmap does not represent a commitment, obligation or promise to deliver any products to the customer at any time."
I understand that waiting for some component, feature or enhancement, longer than expected might be frustrating, and I am sorry about the seemingly misleading (from present point of view) information, provided by one of our former colleagues a year ago, but we decided to go in another direction and focus our efforts in polishing the basic components and the Grid first, as well as introducing other new components such as the TreeView and the Window, before eventually getting to the Editor, TreeList and Scheduler.
We will be happy to share more details once we have a more specific timeline and a better estimate of when an initial version of the Scheduler component can be available. Thank you for the understanding.
I am afraid the most current information about the Kendo UI for Angular Scheduler component, is still the one available in my latest posts. We will do our best to start initial research and development work on the Scheduler this summer, but as it is a very complex component, I cannot commit to a timeline or estimate how long it will take us to release it.
We hope that we will be able to have an initial prototype by the end of this year or in the first months of 2019, but this is still just a speculation. Once the initial research phase is over, we will have a better estimate of when the Scheduler can be ready, and will update our roadmap accordingly.