Let people share prefabs with each other, and let the app find and install them.
The prefab system is built - definitions, master collections, Lua scripts with typed parameters, instances that stay linked, stamping for the static case. What does not exist is any way for one person's prefab to reach another person.
STRATEGY.md section 11 puts this at ~40-60 hrs and calls it the only item on its list that REDUCES future workload rather than adding to it: it turns community enthusiasm into product surface that did not have to be built. That argument holds independently of whether the rest of that document's thesis does.
Rough shape:
a portable prefab bundle (definition + script + master geometry + params), probably a subset of the existing .ana codec rather than a new format
somewhere to put them - the existing backend/ already does maps CRUD and share links, so this is closer to a new resource than a new service
in-app browse and install, landing the prefab in the current document
the trust question, which is the real one: prefab scripts are Lua that runs in the user's editor. Installing a stranger's prefab is running a stranger's code. lua_dardo_plus is sandboxed from the host by construction, but the exposed CanvasObject/Lines API is still a capability surface worth thinking about before this ships rather than after
Depends on nothing currently open. Related: the Lua scripting tracking issue.
Opened during the roadmap audit on 2026-09-05.
Let people share prefabs with each other, and let the app find and install them.
The prefab system is built - definitions, master collections, Lua scripts with typed parameters, instances that stay linked, stamping for the static case. What does not exist is any way for one person's prefab to reach another person.
STRATEGY.md section 11 puts this at ~40-60 hrs and calls it the only item on its list that REDUCES future workload rather than adding to it: it turns community enthusiasm into product surface that did not have to be built. That argument holds independently of whether the rest of that document's thesis does.
Rough shape:
- a portable prefab bundle (definition + script + master geometry + params), probably a subset of the existing `.ana` codec rather than a new format
- somewhere to put them - the existing `backend/` already does maps CRUD and share links, so this is closer to a new resource than a new service
- in-app browse and install, landing the prefab in the current document
- the trust question, which is the real one: prefab scripts are Lua that runs in the user's editor. Installing a stranger's prefab is running a stranger's code. `lua_dardo_plus` is sandboxed from the host by construction, but the exposed CanvasObject/Lines API is still a capability surface worth thinking about before this ships rather than after
Depends on nothing currently open. Related: the Lua scripting tracking issue.
Opened during the roadmap audit on 2026-09-05.
ImBenji
added this to the Arcs & Angles project 2026-09-05 15:11:46 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Let people share prefabs with each other, and let the app find and install them.
The prefab system is built - definitions, master collections, Lua scripts with typed parameters, instances that stay linked, stamping for the static case. What does not exist is any way for one person's prefab to reach another person.
STRATEGY.md section 11 puts this at ~40-60 hrs and calls it the only item on its list that REDUCES future workload rather than adding to it: it turns community enthusiasm into product surface that did not have to be built. That argument holds independently of whether the rest of that document's thesis does.
Rough shape:
.anacodec rather than a new formatbackend/already does maps CRUD and share links, so this is closer to a new resource than a new servicelua_dardo_plusis sandboxed from the host by construction, but the exposed CanvasObject/Lines API is still a capability surface worth thinking about before this ships rather than afterDepends on nothing currently open. Related: the Lua scripting tracking issue.
Opened during the roadmap audit on 2026-09-05.