Font lists

[ickshonpe]

Objective

Add FontSource variants to support ordered lists of fonts.

Solution

The changes are mostly just boilerplate implementing the API. The lists are just handed off to Parley to resolve.

• New FontSource variants Css and List. bevy_text uses the first available font in the list.
  • FontSource::Css takes a string in CSS font family format.
  • FontSource::List takes a vector of family names and generic font families.
• New FontSource::Generic(GenericFontFamily) enum replaces the individual variants for each generic family. Included short form constructors such as FontSource::serif() to be used instead of FontSource::Generic(GenericFontFamily::Serif).
• Updated the font queries in update_editable_text_content_size. That function is a bit unpleasant now but I'm not sure if there's a nicer alternative to what it does.
• New FontFamilyEntry and GenericFontFamily enums, these just exist to be Bevy friendly types that are mapped internally to Parley's FontFamilyName and GenericFamily types.

Testing

New example font_lists:

cargo run --example font_lists

The first available font from the list (going downwards) is used to display each list. The Gabriola font isn't included with Bevy, so it's skipped.

With the "system_font_discovery" feature enabled, the Gabriola font (if present on your system) is used:

cargo run --example font_lists --features="system_font_discovery"

[github-actions]

Your PR caused a change in the graphical output of an example or rendering test. This might be intentional, but it could also mean that something broke!
You can review it at https://pixel-eagle.com/project/B04F67C0-C054-4A6F-92EC-F599FEC2FD1D?filter=PR-24378

If it's expected, please add the M-Deliberate-Rendering-Change label.

If this change seems unrelated to your PR, you can consider updating your PR to target the latest main branch, either by rebasing or merging main into it.

[github-actions]

Your PR caused a change in the graphical output of an example or rendering test. This might be intentional, but it could also mean that something broke!
You can review it at https://pixel-eagle.com/project/B04F67C0-C054-4A6F-92EC-F599FEC2FD1D?filter=PR-24378

If it's expected, please add the M-Deliberate-Rendering-Change label.

If this change seems unrelated to your PR, you can consider updating your PR to target the latest main branch, either by rebasing or merging main into it.

[github-actions]

Your PR caused a change in the graphical output of an example or rendering test. This might be intentional, but it could also mean that something broke!
You can review it at https://pixel-eagle.com/project/B04F67C0-C054-4A6F-92EC-F599FEC2FD1D?filter=PR-24378

If it's expected, please add the M-Deliberate-Rendering-Change label.

If this change seems unrelated to your PR, you can consider updating your PR to target the latest main branch, either by rebasing or merging main into it.

[github-actions]

Your PR caused a change in the graphical output of an example or rendering test. This might be intentional, but it could also mean that something broke!
You can review it at https://pixel-eagle.com/project/B04F67C0-C054-4A6F-92EC-F599FEC2FD1D?filter=PR-24378

If it's expected, please add the M-Deliberate-Rendering-Change label.

If this change seems unrelated to your PR, you can consider updating your PR to target the latest main branch, either by rebasing or merging main into it.

[github-actions]

Your PR caused a change in the graphical output of an example or rendering test. This might be intentional, but it could also mean that something broke!
You can review it at https://pixel-eagle.com/project/B04F67C0-C054-4A6F-92EC-F599FEC2FD1D?filter=PR-24378

If it's expected, please add the M-Deliberate-Rendering-Change label.

If this change seems unrelated to your PR, you can consider updating your PR to target the latest main branch, either by rebasing or merging main into it.