Files
editor/packages/core
Wassim SAMADandClaude Opus 4.7 3c37ff009b Phase 5 Stage E: fence / slab / ceiling drop their legacy panels
Three flavors of Stage E in one PR:

- **Fence** — fully auto-derived. Adds `kind: 'boolean'` to ParamField
  (rendered as ToggleControl), wires `showInfill` through
  `def.parametrics`. Legacy `FencePanel` deleted; the auto-derived
  `<ParametricInspector>` now drives fence editing entirely.

- **Slab / Ceiling** — kind-owned via `parametrics.customPanel`. The
  legacy panels have shape-specific bits (elevation/height presets,
  area display, holes list with auto-vs-manual provenance) that don't
  fit the auto-derived field model yet. `<ParametricInspector>` learns
  to lazy-load and mount `parametrics.customPanel` when present;
  legacy `SlabPanel` + `CeilingPanel` files relocate to
  `nodes/src/<kind>/panel.tsx` and the legacy copies delete.

  When `list` / `computed` / `action` field kinds eventually graduate
  to auto-derived support, these custom panels collapse back into
  `parametrics.groups`. The plan calls this out under "Custom-behavior
  escape hatch" and Foot-gun 5 of the recipe.

Public-surface additions in `@pascal-app/editor`:
- `ActionButton`, `ActionGroup`, `PanelSection`, `SegmentedControl`,
  `ToggleControl`, `PanelWrapper` — needed by the kind-owned panels.

Per-kind progress table: fence/slab/ceiling all flip to E .

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-18 10:04:11 -04:00
..
2026-02-05 08:22:19 +09:00

@pascal-app/core

Core library for Pascal 3D building editor.

Installation

npm install @pascal-app/core

Peer Dependencies

npm install react three @react-three/fiber @react-three/drei

What's Included

  • Node Schemas - Zod schemas for all building primitives (walls, slabs, items, etc.)
  • Scene State - Zustand store with IndexedDB persistence and undo/redo
  • Systems - Geometry generation for walls, floors, ceilings, roofs
  • Scene Registry - Fast lookup from node IDs to Three.js objects
  • Spatial Grid - Collision detection and placement validation
  • Event Bus - Typed event emitter for inter-component communication
  • Asset Storage - IndexedDB-based file storage for user-uploaded assets

Usage

import { useScene, WallNode, ItemNode } from '@pascal-app/core'

// Create a wall
const wall = WallNode.parse({
  points: [[0, 0], [5, 0]],
  height: 3,
  thickness: 0.2,
})

useScene.getState().createNode(wall, parentLevelId)

// Subscribe to scene changes
function MyComponent() {
  const nodes = useScene((state) => state.nodes)
  const walls = Object.values(nodes).filter(n => n.type === 'wall')

  return <div>Total walls: {walls.length}</div>
}

Node Types

  • SiteNode - Root container
  • BuildingNode - Building within a site
  • LevelNode - Floor level
  • WallNode - Vertical wall with optional openings
  • SlabNode - Floor slab
  • CeilingNode - Ceiling surface
  • RoofNode - Roof geometry
  • ZoneNode - Spatial zone/room
  • ItemNode - Furniture, fixtures, appliances
  • ScanNode - 3D scan reference
  • GuideNode - 2D guide image reference

Systems

Systems process dirty nodes each frame to update geometry:

  • WallSystem - Wall geometry with mitering and CSG cutouts
  • SlabSystem - Floor polygon generation
  • CeilingSystem - Ceiling geometry
  • RoofSystem - Roof generation
  • ItemSystem - Item positioning on walls/ceilings/floors

License

MIT