Falling-Metal-Interactive/Blacksite
2
0
Fork 0
Code Issues 28 Pull Requests Actions Packages Projects Releases Wiki Activity

BS-JD-403 - Optional dylib extension exploration #29

New Issue
Open
opened 2026-06-06 01:48:36 -04:00 by Rbanh · 0 comments
Rbanh commented 2026-06-06 01:48:36 -04:00
Owner
Copy Link

Summary

Explore dynamic extension loading only after the static extension API is stable.

Why

Dynamic loading is useful for rapid iteration but has ABI, hot reload, safety, and platform complexity. It should be a spike, not a foundation.

Implementation notes

  • Document constraints and risks before implementation.
  • Prototype loading a narrow extension boundary only.
  • Do not make core editor behavior depend on dylib loading.
  • Compare with existing optional game hot reload path.

Acceptance criteria

  • Spike documents feasibility, risks, and recommended next step.
  • Prototype is isolated and removable.
  • Static API remains canonical.
  • No production workflow depends on dylib loading.

Tests/docs

Spike notes and minimal compile/runtime smoke if prototype is kept. Update ADR consequences if decision hardens.

## Summary Explore dynamic extension loading only after the static extension API is stable. ## Why Dynamic loading is useful for rapid iteration but has ABI, hot reload, safety, and platform complexity. It should be a spike, not a foundation. ## Implementation notes - Document constraints and risks before implementation. - Prototype loading a narrow extension boundary only. - Do not make core editor behavior depend on dylib loading. - Compare with existing optional game hot reload path. ## Acceptance criteria - [ ] Spike documents feasibility, risks, and recommended next step. - [ ] Prototype is isolated and removable. - [ ] Static API remains canonical. - [ ] No production workflow depends on dylib loading. ## Tests/docs Spike notes and minimal compile/runtime smoke if prototype is kept. Update ADR consequences if decision hardens.
Rbanh added this to the M4 - Extensibility and runtime integration milestone 2026-06-06 01:48:36 -04:00
Rbanh added the
roadmap:jackdaw
type:architecture
priority:P3
area:extensions
 labels 2026-06-06 01:48:36 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
area:assets

Asset browser, material browser, thumbnails, import, processing, and asset watcher.

  
area:brushes

Brush geometry, CSG, face editing, UVs, and brush diagnostics.

  
area:extensions

Static extension API, extension scaffolds, dylib exploration.

  
area:governance

Policy, attribution, planning, and production process.

  
area:inspector

Inspector, component metadata, component editing UX.

  
area:operators

Editor operator/action framework, undo, commit/cancel semantics.

  
area:physics

Physics placement, colliders, rigid bodies, diagnostics, and overlays.

  
area:project-ux

Project launcher, profiles, templates, or first-run project workflow.

  
area:quality

Regression packs, tests, performance budgets, profiler, first-hour UX.

  
area:runtime

BRP, remote inspector, PIE, game preview, runtime integration.

  
area:scene-io

Scene document, save/load, schema, migration, or reference repair.

  
area:terrain

Terrain authoring, terrain sculpting, heightmaps, and terrain materials.

  
area:viewport

Viewport interaction, selection, shortcuts, camera, overlays, and controls.

  
priority:P0

Must-have prerequisite or milestone-critical item.

  
priority:P1

Important production feature after P0 work is stable.

  
priority:P2

Useful follow-up or polish item.

  
priority:P3

Exploratory or later spike.

  
roadmap:jackdaw

Jackdaw-inspired Blacksite editor roadmap item.

  
type:architecture

Architecture, internal framework, or hard-to-reverse technical decision.

  
type:docs

Documentation, policy, samples, or issue-board structure.

  
type:epic

Tracking epic that groups related milestone work.

  
type:feature

User-visible feature or capability.

No Label
area:assets
area:brushes
area:extensions
area:governance
area:inspector
area:operators
area:physics
area:project-ux
area:quality
area:runtime
area:scene-io
area:terrain
area:viewport
priority:P0
priority:P1
priority:P2
priority:P3
roadmap:jackdaw
type:architecture
type:docs
type:epic
type:feature
Milestone
Clear milestone
No items
No Milestone
M4 - Extensibility and runtime integration
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
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: Falling-Metal-Interactive/Blacksite#29
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?