[Suggestion] Expose internal command buffer?
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 4.3k
- Forks
- 300
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 61
Description
I don't know how much of that is possible. But if you would expose command buffer - it would be possible to use vello more-or-less directly for rendering into svg/pdf/postscript/etc...
I didn't research in what form you exactly store commands - but if they're in somewhat digestible format, like move_to, line_to, or more high-level - that should work...
The idea is having something like `skia-pdf` WITHOUT making all interface functions - function-pointer redirections to specific implementations.
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
The issue does not name files, tests, or an existing entry point. Start by locating how Vello stores its internal command buffer and determine whether its representation is suitable for public consumption. Done would require an agreed API and design for exposing commands to alternate SVG, PDF, or PostScript renderers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- computer-graphics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100