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

Remove textArea border in MultiLineComboBoxEditor #7799

Merged
merged 1 commit into from
Sep 27, 2024

Conversation

DJ-Raven
Copy link
Contributor

This PR update the UI. by removed textArea border in MultiLineComboBoxEditor class
This MultiLineComboBoxEditor use in:

  • Find in Projects by pressed Ctrl+F
  • Replace in Projects by pressed Ctrl+H

2024-09-26_152246

After changed

Preview with flatlaf light laf

2024-09-26_152149

Preview with flatlaf light cupertino (multi line search)

2024-09-26_152528

Please review, Thank you

@troizet troizet added the UI User Interface label Sep 26, 2024
@mbien mbien added the ci:dev-build [ci] produce a dev-build zip artifact (7 days expiration, see link on workflow summary page) label Sep 26, 2024
@apache apache locked and limited conversation to collaborators Sep 26, 2024
@apache apache unlocked this conversation Sep 26, 2024
@mbien
Copy link
Member

mbien commented Sep 26, 2024

awesome, thanks for the fix!

@DJ-Raven could you update the commit author to your full name like in your last PR?
for comparison:

 git commit --amend --author="Author Name <email@address.com>" --no-edit

and simply force push

@mbien mbien added this to the NB24 milestone Sep 26, 2024
@DJ-Raven
Copy link
Contributor Author

@mbien already push

Copy link
Contributor

@eirikbakke eirikbakke left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this fix; looks good!

Perhaps quickly check that it also works on the Windows LAF as well (though any problems would be purely cosmetic).

Copy link
Member

@mbien mbien left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

checked some of the older LAFs and it looked good except on GTK. But GTK LAF is a lost cause i think, NB doesn't render well on it and nothing aligns (not only in this dialog toolbars etc look also bad).
image

Metal
image

Nimbus
image

@eirikbakke
Copy link
Contributor

Yeah, I don't think the alignment problems in older LAFs are due to this patch; I saw them when trying Nimbus without the patch, for instance. (In any case I don't think much effort needs to be spent on the older LAFs at this point; they just served as a useful "test case" for the patch.)

@eirikbakke eirikbakke merged commit 328931e into apache:master Sep 27, 2024
31 checks passed
@eirikbakke
Copy link
Contributor

Merged it--thanks again for the patch!

@DJ-Raven
Copy link
Contributor Author

Thank @mbien @eirikbakke for review.

@mbien
Copy link
Member

mbien commented Sep 27, 2024

I don't think the alignment problems in older LAFs are due to this patch;

yes, this is not what I meant. This dialog is somewhat special since it uses the old grid bag layout which doesn't implement text baseline alignment for neighboring components if i remember correctly. Two combo boxes are also multi line fields with dynamic height - so this is to be expected that it won't look nice on all LAFs. (I remember starring at the dialog a while while doing #3393)

What i meant was that the GTK laf specifically looks inconsistent everywhere else too. Toolbar icons have the wrong size and every combo box looks different. I set -J-Djdk.gtk.version=2 for VisualVM to make it somewhat useable (fixes the toolbars at least).

I am wondering if we should filter it out from the LAF list? I guess users could still use the flag to force it.

@eirikbakke
Copy link
Contributor

I am wondering if we should filter it out from the LAF list? I guess users could still use the flag to force it.

Perhaps? Or otherwise advertise that we really recommend FlatLAF over the other ones.

The main reason to keep the older LAFs around is that it's useful to have each of the basic Java LAFs available in the list for people who are developing Swing apps and would like to see what each one of them looks like in the context of the full IDE. It's also useful during NetBeans IDE development, to test Swing code changes with different LAFs to make sure the code does not make accidental assumptions about specific LAF implementation details.

I set -J-Djdk.gtk.version=2 for VisualVM to make it somewhat useable (fixes the toolbars at least).

I think we used to have that setting as default in NetBeans, until https://issues.apache.org/jira/browse/NETBEANS-5862 removed it. Maybe certain issues appeared to have been fixed in the JDK, but others were not.

@DJ-Raven DJ-Raven deleted the update-search-form branch September 29, 2024 16:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci:dev-build [ci] produce a dev-build zip artifact (7 days expiration, see link on workflow summary page) UI User Interface
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants