purge manual font rendering
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 14.4k
- Forks
- 1.3k
- PR merge metrics
- No merged PRs in 30d
Description
Right now, we are using fontconfig, freetype and harfbuzz for rendering fonts in some places, while Qt5 is used in the newer GUI code. We should get rid of the low-level libraries.
- find code that uses our own font renderer (
libopenage/renderer/font) - use Qt5 instead
- remove the font renderer
- update buildsystem and docs
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by searching for uses of the custom renderer in libopenage/renderer/font and identify the code paths that still use fontconfig, freetype, or harfbuzz. Review the newer Qt5 GUI code as the intended replacement, then determine the affected buildsystem and documentation. Done means the listed usages are migrated, the custom renderer is removed, and buildsystem and docs are updated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, cpp
- Domain
- build-system, computer-graphics, documentation
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100