feat(gui): Better looking error console

[Yubo-Cao]

Closes https://github.com/JabRef/jabref-issue-melting-pot/issues/782

Steps to test

Open Help > View Event Log

Mandatory checks

• I own the copyright of the code submitted and I license it under the MIT license
• I manually tested my changes in running JabRef (always required)
• [/] I added JUnit tests for changes (if applicable)
• I added screenshots in the PR description (if change is visible to the user)
• [/] I described the change in CHANGELOG.md in a way that is understandable for the average user (if change is visible to the user)
• [/] I checked the user 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 updating file(s) in https://github.com/JabRef/user-documentation/tree/main/en.

[subhramit]

Can you link the specific sub-task @Yubo-Cao
Currently, the entire meta-issue is linked that will be closed on merging this otherwise

[subhramit]

Thoughts: This will definitely help in debugging
However, should a user be able to see these details is something that we should discuss.
E.g. Unsupported JavaFX configuration
@JabRef/developers

[InAnYan]

So in previous versions users could not see "Unsupported JavaFX configuration"?

I would leave everything.

Though.. maybe we can add a combobox for filtering (>=) log levels?

[Yubo-Cao]

Thoughts: This will definitely help in debugging However, should a user be able to see these details is something that we should discuss. E.g. Unsupported JavaFX configuration @JabRef/developers

I didn't change the error console logic at all. I figured perhaps ... I messed up my JavaFX environment? I probably should have linked this issue instead: https://github.com/JabRef/jabref-issue-melting-pot/issues/782

[subhramit]

I didn't change the error console logic at all.

Ah, my confusion stemmed from not opening the event log since a long time, sorry

[subhramit]

Just check once if the javafx configuration thing appears on main as well

[Siedlerchr]

The unsupported javafx config comes from merging modules together. This is a known issue.

[jabref-machine]

Hey, we noticed that you force-pushed your changes. Force pushing is a bad practice when working together on a project (mainly because it is not supported well by GitHub itself). Commits are lost and comments on commits lose their context, thus making it harder to review changes.

When the pull request is getting integrated into main, all commits will be squashed anyway. Thus, your individual commit history will not be visible in main.

In future, please avoid that. For now, you can continue working.

[calixtus]

You could add a link to the issue tracker, if you say that an issue could be reported in the intro text. But how ever, I think the info text belongs into the documentation and not into the ui.

[trag-bot]

@trag-bot didn't find any issues in the code! ✅✨

[subhramit]

We forgot to add a changelog entry for this

[Yubo-Cao]

We forgot to add a changelog entry for this

I conveniently updated the CHANEGLOG at another open PR that would get this fixed after merged... #13791