[UI/UX] Improve the debug log

[btarg]

Describe the project you are working on

A turn-based RPG

Describe the problem or limitation you are having in your project

The current debug log is difficult to read and parse, especially when compared to Unity's. It also does not have any debug functionality besides simply outputting text.

Describe the feature / enhancement and how it helps to overcome the problem or limitation

Readability

• Each line of the debug log should have an alternating background colour shade, like in Unity. This helps distinguish where new lines start. Icons for the log severity level at the start of every statement could also help.
• The log's font size should be easy to quickly change, e.g. with a slider.

  Functionality

• When a node's name/ID is printed via print(node) the output should become a hyperlink. Clicking it should highlight the node in the remote debug's scene tree if applicable.
• Within a stack trace, references to files and line numbers are printed. These should also become like hyperlinks that the user can click to find exactly where in their editor these errors come from. This cannot currently be done in VS Code with the Godot extension as res:// file paths are not supported in VS Code - but the functionality is part of that editor.
• When a regular string, error or stack trace are printed, the user should be able to double-click a non-hyperlinked part of the line to open the associated print function in their editor.

Describe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams

n/a

If this enhancement will not be used often, can it be worked around with a few lines of script?

No

Is there a reason why this should be core and not an add-on in the asset library?

It is a core part of the editor

[AThousandShips]

Within a stack trace, references to files and line numbers are printed. These should also become like hyperlinks that the user can click to find exactly where in their editor these errors come from. This cannot currently be done in VS Code with the Godot extension as res:// file paths are not supported in VS Code - but the functionality is part of that editor.

Already tracked in:

• https://github.com/godotengine/godot-proposals/issues/1628

[passivestar]

Already tracked in:

• Make script paths in Editor Output error messages clickable #1628

Also in https://github.com/godotengine/godot-proposals/issues/10000

[btarg]

Already tracked in:

• Make script paths in Editor Output error messages clickable #1628

Also in #10000 Thank you for showing me both of these! Are there any issues pertaining to the other ideas I mentioned already? Also would implementing #10000 using rich text tags make the output logs look weird outside of the Godot Editor? (e.g. vscode or saved to a text file)

[Calinou]

When a regular string, error or stack trace are printed, the user should be able to double-click a non-hyperlinked part of the line to open the associated print function in their editor.

This is already being tracked in https://github.com/godotengine/godot-proposals/issues/9367. I don't recommend using double-clicking for that though, as double-clicking is already used to select the word under the cursor.