Implement new text API for piet-web
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.4k
- Forks
- 98
- PR merge metrics
- No merged PRs in 30d
Description
The changes to the text API were not implemented for piet-web for the simple reason that I don't know that code very well and it isn't a "tier one" backend, e.g. it is entirely developed and maintained by other contributors.
It would be lovely to get this API working, though! Most of it should be fairly straight forward, but there are a few tricky parts; in particular custom fonts may pose a challenge. It is entirely acceptable if not all features work perfectly, though, so I wouldn't stress too much about this.
Contributor guide
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
No files or tests are named. Start by comparing the existing piet-web text implementation with the new text API, then investigate custom-font handling and the other incomplete features. Done means piet-web supports the API to the extent practical, with limitations for unsupported features documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- computer-graphics
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100