Adopt the jsartoolkitNFT data-oriented tracker facade (jsartoolkitNFT#720)
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript, web-dev
- Domain
- frontend, testing-qa
Research direction
Read ArtkSession, the worker protocol, and the controller node’s letterbox/rescale code, then run the integration tests to understand the current behavior. Track the jsartoolkitNFT #720 facade proposal and compare its API and semantics with this integration. Done means replacing the custom tracking layer with the facade while preserving the e2e expectations and exposing the requested settings and dataset load errors.
Written by the indexing model from the issue text.
Description
webarkit/jsartoolkitNFT#720 proposes createNFTTracker() / createNFTTrackerWorker():
configure(patch)to change the settings live;process(frame, timestampMs)returning aFrameResultwith per-marker poses and found / lost transitions;- load results as values;
- a generic worker wrapper.
WebARKit Studio already implements most of this layer itself inArtkSessionand in its worker protocol. It is the proposal's reference implementation and test bed.
Until the facade lands
- Keep
ArtkSessionaligned with the proposal's semantics: found on the rising edge, lost after the grace period, filters reset on loss, lens rebuilt after load and on near / far changes - Report the gaps found here on #720 (for example: the init lens is still built with near 0.0001 in 1.14.0)
When the facade is released
- Replace
ArtkSessionand the custom worker protocol withcreateNFTTrackerWorker - Map Controller Settings to
configure(); exposelostTimeoutand the AR2 parameters if the facade offers them - Use
projectionFor(viewport)instead of the letterbox / rescale code in the controller node - Show load errors per dataset in the node, from
MarkerLoad - Keep the integration tests: they run against the facade with the same expectations
Acceptance
- Same behaviour in the e2e tests, with less tracking code in this repository.
- 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 5 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 70/100
logancyang/obsidian-copilot#3753 ·
Maintainers usually reply within 1 day
-
area: presentation severity: important
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
voithos-labs/aragonite#763 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
diegosouzapw/OmniRoute#17386 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 Half a day Newbie friendliness 72/100
super-productivity/super-productivity#10982 · 1 comment ·
Maintainers usually reply within 1 day