Phase 2: Authoring
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- three.js, typescript
Research direction
Read the editor and asset code to identify how nodes, project assets, and exporter collection currently work; the issue does not name specific files or tests. Start with the pinball demo graph and the existing handling for params marked asset. Done means a user can build that demo from an empty graph without editing JSON, using their own model, and the graph runs without a camera.
Written by the indexing model from the issue text.
Description
Make the editor usable for real projects: adding nodes quickly, editing complex params, undoing mistakes, bringing in your own assets.
Editor
- Context menu and search to add nodes (by name, category, provider)
- Undo / redo (
rete-history-plugin) - Minimap and auto-arrange (
rete-minimap-plugin,rete-auto-arrange-plugin) - Inspector panel for complex params (vectors, colours, matrices), for example with Tweakpane
- Copy / paste and duplicate of node selections, keeping the internal connections
Assets
- Asset manager: upload images, NFT datasets (
.fset,.fset3,.iset) and models into the project -
scene.gltfnode (glTF / GLB), on both the Three.js and Babylon.js adapters - Assets saved with the project and collected by the exporter (it already collects params marked
asset)
Testing without a camera
-
source.imageandsource.videoFilenodes, producing the samevideovalue assource.camera - Use them in a demo graph that runs without a camera
Extensibility
- Plugin API: node packages loaded from outside the studio (jsartoolkitNFT as first plugin, then artoolkit5-ts): #12
Acceptance
- A user can build the pinball demo from an empty graph without editing JSON, using a model of their own.
Generated by Claude Code
- 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 2 days ago. OpenAI - agents documentation enhancement
webarkit/webarkit-studio#7 · 1 comment · 1 assignee ·
All issues in webarkit/webarkit-studio
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
521xueweihan/HelloGitHub#4025 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
voidzero-dev/void#478 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
Small-tailqwq/dsh-deep-whale#207 ·
Maintainers usually reply within 1 day
-
The inspector never shows the instances field, so scaling out is unreachablePossibly taken @Mrkewl claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
xevrion/breakscale#96 ·
Maintainers usually reply within 4 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Flux159/mcp-server-kubernetes#384 ·