Add an edge border/frame tool for generated models
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, threejs, typescript
- Domain
- computer-graphics, frontend
Research direction
Start by tracing the 2D/3D preview toolbar and the STL/3MF export entry points to determine where model-edge geometry and display options belong. Define a small first version with one border style, color, width, and height behavior, then verify that irregular and smooth/blended edges remain connected in preview and export.
Written by the indexing model from the issue text.
Description
Kromacut could add a border/frame tool that follows the outer edge of the generated model and uses a chosen color or filament.
The goal is to let users add a clean physical outline around a print without needing to edit the source image manually. This could help prints feel more finished, make edges easier to see, or create a consistent frame around irregular shapes.
Useful options could include:
- Toggle border/frame on or off.
- Choose the border color or filament.
- Choose border thickness/width.
- Choose whether the border reaches the highest layer, a fixed height, or only a few top/bottom layers.
- Preview the border in the 2D/3D views before export.
- Export the border as part of the STL/3MF output.
The border should follow the actual model edge, including irregular shapes. It should also behave predictably when smooth/blended edges are enabled, so the result does not look jagged, detached, or inconsistent around softened areas.
This could potentially live as a tool near the 2D preview toolbar, similar to crop and other image-prep tools, or as a 3D/export option if that ends up feeling more natural.
A simple first version could support one border style with color, width, and height options, then expand later if needed.
- 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 79 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
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
apache/rocketmq-dashboard#6610 ·
Maintainers usually reply within 3 days
-
nextjs-tracking
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
cloudflare/vinext#3920 ·
Maintainers usually reply within 1 day
-
Team:Dashboards
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
elastic/kibana#297299 · 1 comment ·
Maintainers usually reply within 1 day
-
analytics beginner friendly community contributions-welcome good first issue hacktoberfest help wanted up-for-grabs
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
affected/v17 affected/v18 area/frontend type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
umbraco/Umbraco-CMS#24186 ·
Maintainers usually reply within 2 days