anshk/builder-research
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
builder-research/Week-2/Task-4/builder/BuilderNotes.md
anshk 9c381ac314 add: Week-2 Project setup
2026-03-31 15:56:38 +05:30

4.3 KiB
Raw Blame History

Builder Notes (Thob) — Task 4: Basic Rotation / Motion

Thob Observations from Task Notes

  • Possible: Partial
  • Implementation used: Applied available built-in animation presets on a cube/object inside thob builder.
  • What worked as expected:
    • Preset animation can be applied quickly.
    • Basic motion effects are visible without writing code.
  • Main limitation observed:
    • Custom animation is not possible; only pre-provided animation can be applied.
    • Exact motion parity with Vanilla/R3F frame-loop logic is not achievable from the builder controls.
  • Builder flow used:
    1. Create/Add cube object in scene.
    2. Open animation controls.
    3. Apply available preset animation.
    4. Tune exposed preset options (for example speed/intensity where available).
  • Complexity: Easy for preset motion, hard for custom motion requirements.
  • Main limitation signals: Editor UX + Runtime + Component concerns.
  • Workaround status: Partial workaround only (use nearest preset); no true custom per-frame animation authoring.

Console Warnings/Errors Seen (Deduplicated) and Probable Meaning

warn: Permissions-Policy header unrecognized feature ('browsing-topics')

  • Type: Browser/header compatibility warning.
  • Probable meaning: Response header includes a policy directive not recognized by the current browser engine.
  • Impact: Usually low for scene editing itself; mostly platform/header noise.

error: GET https://builder.thob.studio/builder/<id> 404 (Not Found)

  • Type: Network/resource error.
  • Probable meaning: Builder page/resource ID is stale, deleted, or inaccessible for current session.
  • Impact: High for workflow continuity; can block loading expected builder state.

warn: Unchecked runtime.lastError: The message port closed before a response was received

  • Type: Browser extension/runtime messaging warning.
  • Probable meaning: A background messaging channel closed before callback response (often extension-related).
  • Impact: Usually low for core scene logic; can add debugging noise.

warn: No HydrateFallback element provided to render during initial hydration

  • Type: Hydration/lifecycle warning.
  • Probable meaning: Initial hydration path expected a fallback UI element but none was configured.
  • Impact: Can produce unstable initial editor/preview rendering behavior.

warn: ... changing from uncontrolled to controlled and RadioGroup is changing from uncontrolled to controlled

  • Type: React state-management warning.
  • Probable meaning: Form/editor controls switch value ownership mode across renders.
  • Impact: Property panel behavior may become inconsistent or glitchy.

warn: GetBindingData<id> method already registered (repeated)

  • Type: Duplicate registration warning.
  • Probable meaning: Binding method handlers are attached multiple times during rerender/remount cycles.
  • Impact: High log noise, risk of duplicated side effects, and potential performance degradation.

warn: resetPOI method already registered

  • Type: Duplicate command registration warning.
  • Probable meaning: Command/event handler is registered more than once without cleanup.
  • Impact: Risk of repeated command execution and state drift.

warn: camera-controls: verticalDragToForward was removed...

  • Type: API deprecation/removed option warning.
  • Probable meaning: Legacy camera-controls prop is still being used by some path in the runtime/editor.
  • Impact: Non-fatal now, but indicates outdated control configuration and future fragility.

error: THREE.GLTFLoader: Invalid plugin found: missing name

  • Type: Asset loader/plugin configuration error.
  • Probable meaning: GLTF loader plugin object does not satisfy required shape/metadata.
  • Impact: Asset loading behavior may be incomplete or fail for some models.

Overall Read

  • For Task 4, thob supports only preset motion and does not support custom animation logic, which is the core functional gap compared with Vanilla and R3F.
  • Console output shows repeated registration and controlled/uncontrolled warnings, which aligns with editor/runtime stability concerns when iterating quickly in builder.
  • The 404 page load and loader/control warnings suggest platform-level reliability and compatibility issues that can interfere with smooth motion-authoring workflows.