Calendar component with Vaadin 8 / Java 8 style APIs

[heruan]

Seems like the Calendar component is missing in FW8 (just legacy compatibility from 7).

In my opinion a Calendar component shouldn't be missing/updated in FW8, considering the major improvement in data providing/binding API and Java 8 java.time classes.

[elmot]

Thanks for your feedback, we already found that is an important feature. Planned for future releases, under development right now.

[pleku]

For clarity: While we don't have any big plans on developing the Calendar component further, we agree that it would be worthwhile to convert it to have Java 8 style API's and replace Container part with DataProvider support.

This is now in the backlog, but I cannot give any guarantees when we'll get to this.

[pleku]

We have discussed about Calendar, the conclusion was that we want to spun this first as an add-on, to gather feedback and to allow us to improve and break the API when needed (instead of forcing some version with FW 8.1). This would make it then much faster to make a the first version of this and make it available for users via Directory.

[wgumar01]

Hi All, Is there a way to access the source code of the calendar component?

I have some feature enhancements that I would like to implement on the Calendar. Where can I download the complete source code for this component?

[RobertZenz]

@wgumar01 You can access it from the 7.7 branch.

[cyberoblivion]

Sad that this was left behind. This is an important component for many and it distinguishes Vaadin from many other frameworks that do not provide a calendar.

[blackbluegl]

AddOn: https://github.com/blackbluegl/calendar-component Same as in V7 with improvements and works in V8 without legacy packages

[stale[bot]]

Hello there!

It looks like this issue hasn't progressed lately. There are so many issues that we just can't deal them all within a reasonable timeframe.

There are a couple of things you could help to get things rolling on this issue (this is an automated message, so expect that some of these are already in use):

• Check if the issue is still valid for the latest version. There are dozens of duplicates in our issue tracker, so it is possible that the issue is already tackled. If it appears to be fixed, close the issue, otherwise report to the issue that it is still valid.
• Provide more details how to reproduce the issue.
• Explain why it is important to get this issue fixed and politely draw others attention to it e.g. via the forum or social media.
• Add a reduced test case about the issue, so it is easier for somebody to start working on a solution.
• Try fixing the issue yourself and create a pull request that contains the test case and/or a fix for it. Handling the pull requests is the top priority for the core team.
• If the issue is clearly a bug, use the Warranty in your Vaadin subscription to raise its priority.

Thanks again for your contributions! Even though we haven't been able to get this issue fixed, we hope you to report your findings and enhancement ideas in the future too!