Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for the Vaadin UI Framework #24794

Open
1 of 7 tasks
josiahhaswell opened this issue Jan 9, 2024 · 6 comments
Open
1 of 7 tasks

Support for the Vaadin UI Framework #24794

josiahhaswell opened this issue Jan 9, 2024 · 6 comments
Labels
area: feature request 💡 resolution: should go to blueprint The solution will no be implemented in core, but rather be a blueprint theme: front

Comments

@josiahhaswell
Copy link

Overview of the feature request

As a Vaadin user, it would be nice if JHipster supported the Vaadin UI framework

Motivation for or Use Case
  1. Vaadin is a widely-used Java UI technology
  2. Support for Vaadin has the potential to increase breadth of both projects
Related issues or PR

I see an old issue related to this request (from 2018)

  • Checking this box is mandatory (this is just to show you read everything)

I'm happy to work on contributing this feature if it seems like there's agreement that it should be implemented.

Vaadin does have commercial features (components, support, etc.)--does that pose a problem? The core framework and many components are completely open-source.

Scope

  • Generator for a Vaadin Flow template
  • Generator for a Vaadin Hilla template
  • Integrate with Spring Security
  • Spring framework support
  • Micronaut support
  • Quarkus support

Before I embark on submitting a PR, are there any comments or considerations I may be missing?

@mraible
Copy link
Contributor

mraible commented Jan 9, 2024

This would be best implemented as a JHipster Blueprint. Having it separate from the core should make it easier to maintain.

Would you just be using Vaadin for the frontend or for the backend, too?

Also, please keep in mind that creating it is the easy part. Maintaining it for years to come is a lot harder.

@mshima
Copy link
Member

mshima commented Jan 10, 2024

@josiahhaswell are you willing to contribute?

@mshima mshima added area: feature request 💡 theme: front resolution: should go to blueprint The solution will no be implemented in core, but rather be a blueprint and removed area: triage theme: undefined labels Jan 10, 2024
@josiahhaswell
Copy link
Author

Hi folks,

Thanks for the responses. @mraible -- yes, I'm working with the Vaadin team to ensure long-term maintenance. I may not proceed if I can't secure that.

@mshima Yes, I'd be happy to perform at least the initial work, and contribute towards maintenance long-term

@atomfrede
Copy link
Member

Thats big news to have the Vaadin team on board. Looking forward to the first result. Do you want us to create a repo under the jhipster org or do you want to start elsewhere?

@mshima
Copy link
Member

mshima commented Jan 15, 2024

The first step is to generate a working sample project.

@josiahhaswell
Copy link
Author

Thats big news to have the Vaadin team on board. Looking forward to the first result. Do you want us to create a repo under the jhipster org or do you want to start elsewhere?

Hi @atomfrede -- we'd love to have a repo under the JHipster org. I can try to get an initial sample project here shortly. I'm currently traveling so I wouldn't expect much progress on this before February

@mshima mshima mentioned this issue Feb 2, 2024
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: feature request 💡 resolution: should go to blueprint The solution will no be implemented in core, but rather be a blueprint theme: front
Projects
None yet
Development

No branches or pull requests

4 participants