-
Notifications
You must be signed in to change notification settings - Fork 51
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
fix: set proper borders / alignment in quarkus wizard #969
Conversation
For the Filter extension field (in last wizard page) I will grow up the field size to take the full horizontal size of the page. It is not linked to this issue but I have noticed that click on Next button is slow. I think it is because it collect Quarkus extension, but I think we should manage a progress monitor or something like this which explains that Quarkus extensions are collected. At first I though it didn't work and click on Next button several times. |
Signed-off-by: Fred Bricon <[email protected]>
12ed118
to
5064d08
Compare
Dimension maxSize = super.getMaximumSize(); | ||
return new Dimension(maxSize.width, JBUI.scale(30)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Signed-off-by: Andre Dietisheim <[email protected]>
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
Made first wizard page aka code endpoint chooser step only have left margin. Other than that +1
@adietish definitely too much space, I spent some time trying to fix it already, but IMHO this requires rewriting the QuarkusModuleBuilder so it doesn't extend JavaModuleBuilder, so we can control the layout of the SDK field. I chose to ignore that in this PR for now, it will need to be addressed separately. |
I was actually thinking more of the SDK left alignment, more than the space below |
@adietish thanks |
fixes #636
fixes #637