Skip to content

Customizable Text Engine Support #491

@CryZe

Description

@CryZe

Currently we bring our own text engine that always turns the glyphs into paths. This isn't ideal when using a rendering backend that itself supports rendering text. In the browser it's much better to let the canvas render out the text as that results in fewer draw calls and also allows using any fonts other than our default fonts in the first place as the browser does not allow getting access to the font data of the fonts installed on the user's system. Additionally our current text engine does not support any font fallback, so using the underlying renderer's or even the system's default text engine provides much better font fallback support. So for all of these reasons and more it would be ideal to be able to swap out the text engine.

This actually is already mostly implemented.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementAn improvement for livesplit-core.featureA new user visible feature for livesplit-core.priority: highThis is a high priority issue.renderingThe issue or pull request is affecting the rendering.text engineThis is about the text engine implementation.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions