Calendar component with Vaadin 8 / Java 8 style APIs #8217

Open
heruan opened this Issue Jan 11, 2017 · 8 comments

Comments

Projects
None yet
7 participants
@heruan
Contributor

heruan commented Jan 11, 2017

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

This comment has been minimized.

Show comment
Hide comment
@elmot

elmot Jan 12, 2017

Contributor

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

Contributor

elmot commented Jan 12, 2017

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

@pleku

This comment has been minimized.

Show comment
Hide comment
@pleku

pleku Feb 27, 2017

Contributor

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.

Contributor

pleku commented Feb 27, 2017

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 pleku changed the title from Calendar component in FW8 to Calendar component with Vaadin 8 / Java 8 style APIs Mar 13, 2017

@pleku pleku removed the candidate label Mar 22, 2017

@pleku

This comment has been minimized.

Show comment
Hide comment
@pleku

pleku Mar 22, 2017

Contributor

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.

Contributor

pleku commented Mar 22, 2017

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

This comment has been minimized.

Show comment
Hide comment
@wgumar01

wgumar01 Mar 24, 2017

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?

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

This comment has been minimized.

Show comment
Hide comment

@wgumar01 You can access it from the 7.7 branch.

@cyberoblivion

This comment has been minimized.

Show comment
Hide comment
@cyberoblivion

cyberoblivion Feb 1, 2018

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.

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

This comment has been minimized.

Show comment
Hide comment
@blackbluegl

blackbluegl Feb 2, 2018

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

blackbluegl commented Feb 2, 2018

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

@stale

This comment has been minimized.

Show comment
Hide comment
@stale

stale bot Jul 2, 2018

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!

stale bot commented Jul 2, 2018

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!

@stale stale bot added the Stale label Jul 2, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment