Skip to content

Add component carousel toolbox for creating optical elements - #2

Merged
veillette merged 1 commit into
mainfrom
claude/add-component-carousel-dfGC0
Mar 1, 2026
Merged

veillette merged 1 commit into
mainfrom
claude/add-component-carousel-dfGC0

Conversation

@veillette

Copy link
Copy Markdown
Collaborator

Replace hardcoded demo scene with an interactive carousel sidebar that lets users create any optical component by clicking its icon. The carousel (from SceneryStack's sun library) displays icons for all 16 component types organized by category: light sources, mirrors, lenses/glass, and blockers.

  • Add ComponentCarousel with miniature icons and factory functions for all element types (point source, beam, single ray, flat/arc/ parabolic/ideal mirrors, beam splitter, ideal lens, circle/spherical lens, prism, half-plane glass, line/circle blockers, aperture)
  • Add blocker view classes (LineBlockerView, CircleBlockerView, ApertureView) so blockers are now rendered and interactive
  • Update OpticalElementViewFactory to include blocker views
  • Update SimScreenView to host carousel and support dynamic element creation via callback
  • Simplify SimModel to start with empty scene; reset clears all

https://claude.ai/code/session_01QvNN5qX7o5FmGAtweEQyaZ

Replace hardcoded demo scene with an interactive carousel sidebar that
lets users create any optical component by clicking its icon. The
carousel (from SceneryStack's sun library) displays icons for all 16
component types organized by category: light sources, mirrors,
lenses/glass, and blockers.

- Add ComponentCarousel with miniature icons and factory functions
  for all element types (point source, beam, single ray, flat/arc/
  parabolic/ideal mirrors, beam splitter, ideal lens, circle/spherical
  lens, prism, half-plane glass, line/circle blockers, aperture)
- Add blocker view classes (LineBlockerView, CircleBlockerView,
  ApertureView) so blockers are now rendered and interactive
- Update OpticalElementViewFactory to include blocker views
- Update SimScreenView to host carousel and support dynamic element
  creation via callback
- Simplify SimModel to start with empty scene; reset clears all

https://claude.ai/code/session_01QvNN5qX7o5FmGAtweEQyaZ
@veillette
veillette merged commit 428a5b9 into main Mar 1, 2026
1 check passed
@veillette
veillette deleted the claude/add-component-carousel-dfGC0 branch March 1, 2026 22:16
veillette pushed a commit that referenced this pull request Apr 12, 2026
#1 – Centralize element labels in ElementRegistry
Add a `label: TReadOnlyProperty<string>` field to ElementDescriptor so the
registry is the single source of truth for element display names.  Export
`getElementLabel()`.  Remove the duplicate `buildTypeLabels()`/`TYPE_LABELS`
map from EditContainerNode and the now-unused StringManager import there.

#2 – Rename continuousSpectrumSource → ContinuousSpectrumSource
Fix the lone camelCase type key to match the PascalCase convention used by
all other element types.  Add a `case "continuousSpectrumSource":` fall-through
shim in elementSerialization.ts so scenes saved by older versions continue to
load without data loss.

#3 – Replace 4-arg buildEditControls signature with EditControlContext bag
Introduce `EditControlContext { signConvention, useCurvatureDisplay }` in
EditControlsResult.ts.  Update ElementDescriptor, the exported
buildEditControls() functions in ElementRegistry/EditControlFactory, and the
call site in EditContainerNode.  Registry entries that previously prefixed
unused params with `_` now destructure only what they need from the bag.
Adding a new display preference requires a single interface change, not
touching every builder signature.

#4 – Replace instanceof checks in OpticsScene.simulate() with interfaces
Add IAcquirable and ICompound to OpticsTypes.ts, with corresponding type
guards (isAcquirable, isCompound).  DetectorElement implements IAcquirable;
FiberOpticElement implements ICompound.  OpticsScene.simulate() uses the
guards instead of `instanceof DetectorElement` / `instanceof FiberOpticElement`,
removing its dependency on those concrete classes.

#5 – Make OpticsScene.getElement() O(1)
Add a `_elementById: Map<string, OpticalElement>` maintained by addElement /
removeElement / clearElements.  getElement() is now a single Map lookup
instead of a full array scan.

#6 – Fix SpatialIndex.getAllElements() O(n²) dedup
Replace the `all.includes(el)` linear scan inside a loop with a
`Set<OpticalElement>` accumulator, reducing the fast-path dedup from O(n²)
to O(n).

#7 – Extract syncBidirectional helper in SimScreenView
Replace three near-identical `let blockXSync = false` bidirectional-sync
patterns with a single generic `syncBidirectional(propA, propB)` helper.
The helper also writes propA's initial value to propB, removing the
separate initialization lines that preceded two of the three blocks.

https://claude.ai/code/session_01H65WqMzMK88Jkra4gAjhE7
veillette pushed a commit that referenced this pull request Jul 21, 2026
Finding #1: optical-element screen-reader names were generated from the
English class name via regex, bypassing i18n and never updating on locale
change. Add StringManager.getElementTypeNameProperty(type) mapping each
ELEMENT_TYPE_* to its localized component StringProperty; RayTracingCommonView
assigns that Property to accessibleName, falling back to the generated name
only for internal types (e.g. FiberCoreGlass).

Finding #2: the "∫I =" detector readout label was a hardcoded literal next to
a localized sibling. Add a detectorIntegratedIntensity key to en/fr/es, expose
it via getUIStrings(), and use it in DetectorChartPanel.

Mark both findings fixed in doc/scenerystack-review.md.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01US7abq5we9ZiLQ8j5YbUYK
veillette pushed a commit that referenced this pull request Jul 21, 2026
Finding #1: optical-element screen-reader names were generated from the
English class name via regex, bypassing i18n and never updating on locale
change. Add StringManager.getElementTypeNameProperty(type) mapping each
ELEMENT_TYPE_* to its localized component StringProperty; RayTracingCommonView
assigns that Property to accessibleName, falling back to the generated name
only for internal types (e.g. FiberCoreGlass).

Finding #2: the "∫I =" detector readout label was a hardcoded literal next to
a localized sibling. Add a detectorIntegratedIntensity key to en/fr/es, expose
it via getUIStrings(), and use it in DetectorChartPanel.

Mark both findings fixed in doc/scenerystack-review.md.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01US7abq5we9ZiLQ8j5YbUYK
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants