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

Curves and surfaces: curve authoring, picking, CV editing, NURBS

Open
  • Is something wrong?
#47 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
8/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
rust
Domain
desktop

Research direction

This is a tracking epic, not a code task: read known-issues.md and .project-docs/parity.md for the current curve and surface gaps. Work can't start until the pinned reference (#5) and an audited inventory exist, and the checklist items must first be split into child issues with sourced workflows. Done means those child issues are filed, not that any curve code is written.

Written by the indexing model from the issue text.

Description

area/modeling area/viewport epic type/feature

Problem

Static ASCII curves can be displayed read-only; nothing can be authored or picked.

Current behavior

known-issues.md: viewport curve picking, CV/component editing and ASCII authoring are unsupported; binary NCRV refused; .project-docs/parity.md lists curves and surfaces as not implemented.

Expected behavior

Staged curve and surface support.

Checklist:

  • Viewport curve picking
  • CV and edit-point selection
  • Curve creation tools (CV, EP, pencil)
  • Curve editing (rebuild, attach, detach)
  • NURBS surfaces (display, then authoring)
  • Surface operations (loft, revolve, extrude)

Acceptance criteria

  • Each checklist item is split into its own issue before work starts, with a sourced workflow list.
  • Every child follows the feature gates: visibly unsupported until done, MCP coverage with schemas, Editor protocol tests and docs, native visual check.
  • No percentage or parity claim until the pinned reference (#5) and the audited inventory exist.
Dominant language
Rust
Stars
4
Forks
2
Avg merge
2h 28m
Merged PRs (30d)
76

Getting set up

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 cristim/AztecCraft

All issues in cristim/AztecCraft

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.