Template-specific text holes
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 49
- Forks
- 0
- Avg merge
- 13d 23h
- Merged PRs (30d)
- 1
Description
We've talked before about having a nice UI for dynamically picking text locations. A simpler approach (and easier to implement) would be to allow a template to designate its own regions of interest. The UI for creating macros can still be simple (just some text fields) and a go button, but instead of fixed top/bottom locations we could have those fields point to specific targets.
- Add data to the template record to record locations where text should go.
- When creating a macro, populate the text fields based on the template's locations.
- Include those locations in the text lines when creating the macro.
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 tracing the template record, the macro-creation UI, and the code that writes text lines. Implement the three requested steps: store template-specific text locations, use them to populate the fields, and include them when creating a macro; the work is done when macros target each template's declared regions instead of fixed top/bottom locations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100