Use Enso font

[somebody1234]

Pull Request Description

• Closes Use Enso Font in new GUI #8485

Important Notes

None

Screenshots

Before:


After:

Checklist

Please ensure that the following checklist has been satisfied before submitting the PR:

• The documentation has been updated, if necessary.
• Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
• All code follows the
  Scala,
  Java,
  and
  Rust
  style guides. In case you are using a language not listed above, follow the Rust style guide.
• All code has been tested:
  • Unit tests have been written where possible.
  • If GUI codebase was changed, the GUI was tested when built using ./run ide build.

[somebody1234]

adding @kazcw as reviewer as he implemented the corresponding PR for GUI1.
(is there anywhere else that needs this font? most places should have it due to CSS cascading, but it may be conceptually clearer to explicitly add it in more places. alternatively, maybe it's currently being added in too many places - e.g. both main.css and App.vue)

[kazcw]

One thing to watch out for is that the Enso Font is not intended to be used for non-code text without performing some glyph substitutions first (affecting period/space/hyphen): https://github.com/enso-org/font#using-enso-font-in-regular-sentences

Also, some visualizations will break if a non-monospaced font (like Enso Font) is used.

[somebody1234]

hm... should we even be using Enso Font instead of M PLUS 1 in those cases then?

[somebody1234]

@kazcw also, which visualizations will break btw?

[kazcw]

hm... should we even be using Enso Font instead of M PLUS 1 in those cases then?

Indeed--in GUI1 we were using three fonts:

• Enso Font for code
• M PLUS 1 for most non-code
• Some monospace font (DejaVu Sans Mono?) for the text grid visualization (it looks like that isn't changed here)

It's a little inefficient since Enso Font and M PLUS 1 are mostly the same. Some day as an optimization (rather than glyph substitutions) we could reduce the Enso Font to only include a few glyphs, and specify the glyph fallbacks in CSS so that our code font is Enso Font overlayed on the base M PLUS 1 font.

[somebody1234]

hmm... i think i'll switch back to M PLUS 1 for regular text, i can't imagine it being very performant to do text replacement on every single text span in Vue

[enso-bot]

E-Hern Lee reports a new STANDUP for yesterday (2023-12-08):

Progress: - implement

other issues -

• (8228, PR 8501) partially refactor util folder
• (8420, PR 8461) alternate implementation for bringing back missing edges It should be finished by 2023-12-12.