Add basic 2D touch-up tools above the preview
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- react, typescript
- Domain
- frontend
Research direction
Start by inspecting the existing tool area above the 2D preview, including the crop action, and trace how image-preparation changes feed the 3D workflow. Define a focused first tool set from the requested options and establish what edit history and completion behavior are required. Done means users can make small touch-ups inside Kromacut before generating the layered model.
Written by the indexing model from the issue text.
Description
Kromacut could benefit from a small set of 2D editing tools for quick image touch-ups before moving into the 3D workflow.
The goal is not to become a full image editor, but to let users fix small details without leaving the app. For example, they may want to clean up stray pixels, fill gaps, remove tiny artifacts, draw simple corrections, or add text before generating the layered model.
The tools should live in the existing tool area above the 2D preview, alongside actions like crop, so they feel like part of the image-prep workflow rather than a separate mode.
Useful initial tools could include:
- Pencil/brush for simple drawing.
- Eraser or remove tool for small cleanup.
- Fill/bucket tool for replacing small areas.
- Text tool for adding labels or simple lettering.
- Color picker or palette-aware color selection.
- Undo/redo for edits.
A simple first version could start with only brush/eraser/text and expand later.
Desired outcome:
Users can make small visual edits inside Kromacut before generating the 3D model, especially when the original image has artifacts, missing details, or needs simple text/markings added.
- Dominant language
- TypeScript
- Stars
- 290
- Forks
- 32
- Avg merge
- 6h 2m
- Merged PRs (30d)
- 7
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from vycdev/Kromacut
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Experimental WebAssembly acceleration for compute-heavy algorithmsMay be free again @vycdev claimed this 80 days ago, and no pull request is open. Openenhancement
-
enhancement good first issue help wanted
Difficulty 5/5 Over a week Newbie friendliness 55/100
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 42/100
Similar issues
-
Contrib indemnité de départ à la retraite : faire le pont avec le simulateur sur la page génériqueOpenP1
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
SocialGouv/code-du-travail-numerique#7561 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
kubernetes-sigs/headlamp#7950 ·
Maintainers usually reply within 3 days
-
README for cliPossibly taken @Janvi-kapoor claimed this today. OpenOSCI'26
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
GauravKarakoti/SecureFlow#1308 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
vitest-dev/vitest#11577 ·
Maintainers usually reply within 1 day