Mark/Kimi_Agent_Brother_10_Digitizing_App
1
0
Fork 0
Code Issues 14 Pull requests Projects Releases Packages Wiki Activity Actions

Implement real PES file export #2

New issue
Closed
opened 2026-06-22 14:58:57 +00:00 by Mark · 4 comments
Mark commented 2026-06-22 14:58:57 +00:00
Owner
Copy link

⚠️ Re-scoped — blocked on #11

This work was originally framed as "implement from scratch." After auditing the
existing ~/Projects/easystitch/ project (a complete Python embroidery CAM with
5-stage pipeline, satin/fill/running generation, ΔE color matching, and PES/DST/
EXP/JEF output), the right shape is call the EasyStitch service rather than
re-implement the algorithms.

Blocked on #11 ("Stand up EasyStitch as an HTTP service for ThreadCraft").
Until that service exists, this work has no backend to call.

Donor code in EasyStitch (do not port — call it):

  • ~/Projects/easystitch/src/output_generators/pes_generator.py
  • ~/Projects/easystitch/src/post_processing/pull_compensation.py

New scope (post #11)

Replace the in-app PES export with a thin client of the EasyStitch
service. Specifically:

  1. Add a src/lib/easystitch-client.ts typed wrapper (or use the one
    introduced in #11) with a exportPES(stitchObjects, opts) => Blob
    function that calls POST /v1/export and returns the binary.
  2. Update src/components/workspace/ExportDialog.tsx to call this
    client when the user picks PES, and trigger a file download with
    the returned bytes.
  3. Show a progress state during the round-trip (typical: 200-600ms).
  4. Surface the service's X-Stitch-Count and X-Color-Count headers
    in the export confirmation toast.
  5. Error handling: if the service is unreachable, show a toast with
    the failure and offer a "retry". Do not crash the React tree.

Acceptance: a real PES file downloads from the Workspace export
flow and opens in an embroidery viewer (e.g. Ink/Stitch or
embroiderviewer.com) with the design rendered correctly.

## ⚠️ Re-scoped — blocked on #11 > This work was originally framed as "implement from scratch." After auditing the > existing `~/Projects/easystitch/` project (a complete Python embroidery CAM with > 5-stage pipeline, satin/fill/running generation, ΔE color matching, and PES/DST/ > EXP/JEF output), the right shape is **call the EasyStitch service** rather than > re-implement the algorithms. > > **Blocked on #11** ("Stand up EasyStitch as an HTTP service for ThreadCraft"). > Until that service exists, this work has no backend to call. > > Donor code in EasyStitch (do not port — call it): - `~/Projects/easystitch/src/output_generators/pes_generator.py` - `~/Projects/easystitch/src/post_processing/pull_compensation.py` ## New scope (post #11) Replace the in-app PES export with a thin client of the EasyStitch service. Specifically: 1. Add a `src/lib/easystitch-client.ts` typed wrapper (or use the one introduced in #11) with a `exportPES(stitchObjects, opts) => Blob` function that calls `POST /v1/export` and returns the binary. 2. Update `src/components/workspace/ExportDialog.tsx` to call this client when the user picks PES, and trigger a file download with the returned bytes. 3. Show a progress state during the round-trip (typical: 200-600ms). 4. Surface the service's `X-Stitch-Count` and `X-Color-Count` headers in the export confirmation toast. 5. Error handling: if the service is unreachable, show a toast with the failure and offer a "retry". Do not crash the React tree. Acceptance: a real PES file downloads from the Workspace export flow and opens in an embroidery viewer (e.g. Ink/Stitch or embroiderviewer.com) with the design rendered correctly.
Mark commented 2026-06-22 15:01:53 +00:00
Author
Owner
Copy link

Auto-triage: needs decompose

Marked triage-approved + needs-decompose. decompose-executor will pick this up and break it into implementable sub-issues.

## Auto-triage: needs decompose Marked `triage-approved` + `needs-decompose`. decompose-executor will pick this up and break it into implementable sub-issues.
Mark commented 2026-06-22 16:02:40 +00:00
Author
Owner
Copy link

Blocked on #11 (Stand up EasyStitch as an HTTP service for ThreadCraft).

This work has been re-scoped — see the updated body. The reframe replaces
"implement from scratch" with "call the EasyStitch service and render the
result." #11 must complete first; once the service exposes /v1/digitize and
/v1/export, this work becomes a thin client + canvas rendering job.

cc: #11

**Blocked on #11** (Stand up EasyStitch as an HTTP service for ThreadCraft). This work has been re-scoped — see the updated body. The reframe replaces "implement from scratch" with "call the EasyStitch service and render the result." #11 must complete first; once the service exposes `/v1/digitize` and `/v1/export`, this work becomes a thin client + canvas rendering job. cc: #11
Mark commented 2026-06-23 22:05:23 +00:00
Author
Owner
Copy link

Blocked-on update

This issue is blocked on easystitch-service#2 ("Dockerfile + node_hub deployment configuration").

Why: needs the FastAPI wrapper (#1) deployed before /v1/export can be called from the browser.

The parent ticket [Kimi_Agent_Brother_10_Digitizing_App#11] is the integration contract. The actual implementation lives in Mark/easystitch-service. When easystitch-service#2 closes, this issue can move forward.

There is also a frontend-side wiring issue: [Mark/easystitch-service#3] ("TypeScript client wrapper + vite dev proxy") — that one will be mirrored into the ThreadCraft repo as a frontend sub-issue when it's ready to dispatch.

## Blocked-on update This issue is blocked on **easystitch-service#2** ("Dockerfile + node_hub deployment configuration"). **Why:** needs the FastAPI wrapper (#1) deployed before /v1/export can be called from the browser. The parent ticket [Kimi_Agent_Brother_10_Digitizing_App#11] is the integration contract. The actual implementation lives in [Mark/easystitch-service](https://forgejo.tail018ac4.ts.net/Mark/easystitch-service). When easystitch-service#2 closes, this issue can move forward. There is also a frontend-side wiring issue: [Mark/easystitch-service#3] ("TypeScript client wrapper + vite dev proxy") — that one will be mirrored into the ThreadCraft repo as a frontend sub-issue when it's ready to dispatch.
Mark commented 2026-06-27 03:43:38 +00:00
Author
Owner
Copy link

Auto-triage: needs decompose

Marked triage-approved + needs-decompose. decompose-executor will pick this up and break it into implementable sub-issues.

## Auto-triage: needs decompose Marked `triage-approved` + `needs-decompose`. decompose-executor will pick this up and break it into implementable sub-issues.
Mark 2026-06-27 03:51:32 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels   
blocked:commit-ready-failed

   
blocked:gate-fetch

   
blocked:gate-lint

   
blocked:gate-plan

   
blocked:gate-research

   
blocked:needs-attention

Worker halted; needs human/janitor inspection

  
blocked:needs-decision

   
blocked:needs-human

   
blocked:no-changes

   
blocked:verify-failed

   
bug

   
deferred

   
feature-request

   
in-progress

   
needs-decompose

   
needs-triage

   
quickfix

   
security/medium

   
triage-approved
No labels
blocked:commit-ready-failed
blocked:gate-fetch
blocked:gate-lint
blocked:gate-plan
blocked:gate-research
blocked:needs-attention
blocked:needs-decision
blocked:needs-human
blocked:no-changes
blocked:verify-failed
bug
deferred
feature-request
in-progress
needs-decompose
needs-triage
quickfix
security/medium
triage-approved
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Mark/Kimi_Agent_Brother_10_Digitizing_App#2
No description provided.