Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Add dedicated lithophane settings

Open
#52 0 comments 0 reactions 0 assignees View on GitHub

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, tauri, threejs, typescript

Research direction

No files or tests are named. Start by mapping Kromacut’s existing settings, light/dark mapping, 2D/3D preview, and STL/3MF export entry points, then define the lithophane workflow and its material assumptions. Done means a planned, dedicated path with agreed thickness controls, preview behavior, and export settings.

Written by the indexing model from the issue text.

Description

enhancement

Kromacut could add a dedicated lithophane workflow or settings group for prints intended to be viewed with light passing through them.

This needs more planning before implementation, but the goal would be to make lithophane-style output feel intentional rather than something users have to approximate through general print settings.

Potential areas to explore:

  • Lithophane-specific thickness controls.
  • Light/dark mapping behavior.
  • Preview behavior for backlit viewing.
  • Material/color assumptions for translucent or white filament.
  • Export settings that make sense for lithophane prints.

Desired outcome:
Users who want to create lithophanes have a clearer, dedicated path inside Kromacut, with settings and preview behavior designed around light-through-material prints.

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from vycdev/Kromacut

All issues in vycdev/Kromacut

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.