Phase 4: WebARKit integration
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- three.js, typescript
- Domain
- ar-vr-xr, full-stack
Research direction
Start by locating the existing jsartoolkitNFT tracker nodes and the tracker-agnostic trackingResult consumers, then compare their interfaces with webarkit/webarkit. The issue also calls for .wnft target loading, editor image upload tools, pose conversion, and a pinball demo integration. Done means the demo works with webarkit.nftTracker by changing only the tracker nodes; the payload names no files or tests.
Written by the indexing model from the issue text.
Description
Add the trackers of webarkit/webarkit as webarkit.* nodes. The webarkit.* namespace is already reserved for this. Select Marker, Anchor, filters and events already read a tracker-agnostic trackingResult, so they should work unchanged.
Nodes
-
webarkit.cvBackend: chooses a@webarkit/cv-backend-specimplementation (jsfeatNext today, PureCV / WebARKitLib-rs later), and shows itscapabilitiesin the node -
webarkit.target: loads a.wnfttarget -
webarkit.nftTracker: video, cvBackend, target, filter? → markers (trackingResult), onFound, onLost, projection, stats - Conversion of the pose from
Pose { R, t }(OpenCV camera frame) to the column-major GL matrix the renderers use. Share it with jsartoolkitNFT if a shared tracking result is agreed (jsartoolkitNFT#720).
Tools
- Build a
.wnfttarget in the editor from an uploaded image (buildTargetFromImage) - NFT dataset generation for JsartoolkitNFT from an uploaded image
Acceptance
- The pinball demo runs with
webarkit.nftTrackerinstead of the jsartoolkitNFT controller, changing only the tracker nodes.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 4m
- Merged PRs (30d)
- 1
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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 webarkit/webarkit-studio
-
Plugin API: load node packages from outside the studio (jsartoolkitNFT first, then artoolkit5-ts)Openeditor enhancement runtime tracking
Difficulty 5/5 Over a week Newbie friendliness 20/100
webarkit/webarkit-studio#12 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
webarkit/webarkit-studio#10 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Agent instructions for AI coding tools (Claude Code, Copilot, Gemini, Antigravity, Codex, Cursor)Possibly taken @kalwalt claimed this 6 days ago. OpenAI - agents documentation enhancement
webarkit/webarkit-studio#7 · 1 comment · 1 assignee ·
All issues in webarkit/webarkit-studio
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
maniator/verticopolis#1303 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
components-web-app/docs#297 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
appwrite/mcp-for-docs#23 · 1 comment ·
-
`@vanilla-extract/turbopack-plugin`: "getImageSize is not a function" with Next.js 16.4.x when a `.css.ts` file imports an imagePossibly taken @aevarOrigo claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
vanilla-extract-css/vanilla-extract#1799 · 1 comment ·
-
native
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
prime-radiant-inc/evener#4839 ·
Maintainers usually reply within 1 day