Adding text formatting for hits

[vigneshdurairaj]

Compulsory checks

Preview Give feedback

1. Change in CHANGELOG.md described in a way that is understandable for the average user (if applicable)
2. Tests created for changes (if applicable)
3. Manually tested changed features in running JabRef (always required)
4. Screenshots added in PR description (for UI changes)
5. Checked developer's documentation: Is the information available and up to date? If not, I outlined it in this pull request.
6. Checked documentation: Is the information available and up to date? If not, I created an issue at https://github.com/JabRef/user-documentation/issues or, even better, I submitted a pull request to the documentation repository.

Fixes #8797

As first-time contributors, we would like to ensure that our submission adheres to the community guidelines. Consequently, we have submitted this Pull Request as part of our university project. Our team member, @sambhav97, has been assigned to the issue.

We believe that displaying numbers such as 1000 as 1k is a design choice. To provide a visual representation, we have included a screenshot displaying how the entries appear with this change. If there are any oversights or areas for improvement, please do not hesitate to inform us.

When the entries are 1000

When the entries are 1500

When the entries are 100,000

[Siedlerchr]

I like the idea, just a question for the last screenshot? Does that mean 100,000 entries? or just 1000?
I would assume 100k= 100,000

[calixtus]

looks just like a typo to me, since he had 1000 entries = 1k in his first screenshot...

[calixtus]

[vigneshdurairaj]

I like the idea, just a question for the last screenshot? Does that mean 100,000 entries? or just 1000?
I would assume 100k= 100,000

Yes it is 100,000. Changed the description now accordingly.

[Siedlerchr]

I tested it, it's a nice idea. However, it does not resolve the original issue:
Set font size to 14 in Appearance.

There is still something not right with the padding regarding the font size. You might need to check with https://github.com/JonathanGiles/scenic-view to see what's going on.

[calixtus]

About the size of the controls, labels and stuff: Controls should be sized in relation to the base font size of the main application window. See the documentation on jfx css measure units: docs.oracle.com/javafx/2/api/javafx/scene/doc-files/cssref.html#typelength

[vigneshdurairaj]

We have analyzed and improved the padding and font scaling in the UI.
Our changes include:
Examining the CSS padding, which accommodates the arrow and icon elements.
Identifying UI breakpoints by applying text formatting to observe where the UI breaks.
Adjusting font scaling by changing the font size units from percentage to em.
Implementing a logic in Java that reduces the font size by 0.20 em for every 4 steps after the font size reaches 17.
These changes improve the UI's responsiveness and ensure a consistent appearance across different font sizes.

With font size default

With font size 14

With font size 18

With font size 22

With font size > 26

[Siedlerchr]

Yeah! Really great work, tested it, works fine! Thanks for digging into this :)
Codewise looks also good to me.
Please add a changelog entry, then you can set it to ready for review.

[calixtus]

😍
Took the liberty tho shorten the changelog a bit.

[Siedlerchr]

@vigneshdurairaj Unfortunately, there was an issue with the update of the item count. However, I was able to adapt your code a bit. FYI: #9709