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

Original Maya-style icon set: wire into the shell and retire tool_icons.rs

Open
  • Is something wrong?
#70 7 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
12/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
rust
Domain
desktop

Research direction

Start in src/tool_icons.rs (current Cube, Plane, Undo, Redo and Frame symbols) and the provenance file .project-docs/icon-provenance.md, but note that src/ui_icons.rs is still being built by another session and its wiring is blocked on the Move slice. The issue spans icon drawing, accesskit labels, MCP tool schemas, Editor protocol tests and a native screenshot check, so it is not a first task. Done means every criterion in the checklist holds, with the MCP docs in .project-docs/mcp.md updated in the same change.

Written by the indexing model from the issue text.

Description

area/icons area/ui-parity type/feature

Problem

The UI uses ad hoc vector symbols in src/tool_icons.rs. An original code-drawn icon set (src/ui_icons.rs, gallery example, provenance table) is in progress by another session (slices B1/B2 in progress, B4 wiring blocked on Move landing).

Current behavior

src/tool_icons.rs draws Cube, Plane, Undo, Redo and Frame today.

Expected behavior

Icons mimic Maya's icon language (silhouette, metaphor, colour coding) but are original, with a provenance row per icon in .project-docs/icon-provenance.md. The project license is being applied as MIT OR Apache-2.0, so provenance wording can proceed. Status Line and Poly Modeling shelf icons are deferred to the Status Line and Shelf slices.

Acceptance criteria

  • Every icon button keeps a text label or hover text plus accesskit widget_info.
  • Gallery checked at 1x and 2x in both tones.
  • Nothing copied, traced or sampled from Maya assets.
  • Unimplemented controls stay visibly disabled with a reason; no dummy tools or controls.
  • MCP coverage in the same change: implemented operations and relevant state exposed with synchronized tool schemas, real Editor protocol tests (scene token, draft, modal, close and busy guards) and updates to .project-docs/mcp.md and its coverage inventory.
  • Native visual check of the real window (screenshot reviewed), not only headless tests.
  • Tests cover malformed, empty, boundary and failure cases; failed operations preserve the baseline.
  • No parity claim without comparison against the pinned Maya reference (#5); unverified constants are documented as provisional.
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.