docs: added week 3 general notes and personal summary
This commit is contained in:
parent
31aa3a500f
commit
6ec84d0ea1
@ -0,0 +1,14 @@
|
|||||||
|
# Week 3 - Integrity Audit & Stress Test General Notes
|
||||||
|
|
||||||
|
## Audit Focus
|
||||||
|
This week focused on the **Integrity and Scaling** of Thob's interaction patterns. We tested consistency under rapid input and evaluated how logic scales for multi-object configurators.
|
||||||
|
|
||||||
|
## Key Integrity Findings
|
||||||
|
- **State Reliability**: [PASS] Material variant swaps remained 100% consistent during high-frequency (sub-200ms) clicking cycles.
|
||||||
|
- **Session Persistence**: [FAIL] Selection state (e.g., planet texture) **resets to default** on browser refresh. The editor does not currently persist the active variant in the local session.
|
||||||
|
- **Geometric Robustness**: [FAIL] Confirmed a **Reproducible Cylinder Crash** when toggling visibility. This indicates an internal failure in Thob's primitive-to-number conversion logic.
|
||||||
|
- **Selection Scaling**: [FAIL] Managing "Single-Select" lists relies on manual "Reset" triggers per button. For scenes with 10+ objects, this logic becomes unmanageable (**State Explosion**).
|
||||||
|
|
||||||
|
## Console Intelligence
|
||||||
|
- **Persistent Signal**: `GetBindingData... method already registered` scales with interaction speed.
|
||||||
|
- **Critical Signal**: `TypeError: Cannot convert a Symbol to a number` observed during cylinder property mutations.
|
||||||
@ -1 +1,27 @@
|
|||||||
# Week 3 Personal Summary
|
# Divya — Week 3 Summary
|
||||||
|
|
||||||
|
## Tasks Completed
|
||||||
|
- Task 1: Material Variant Stress Test (Red/Blue/Yellow)
|
||||||
|
- Task 2: Texture Persistence Audit (Sun/Moon/Earth/Jupiter)
|
||||||
|
- Task 3: Geometric Stability Audit (Sphere/Cube/Cylinder/Plane)
|
||||||
|
- Task 4: Multi-Object Logic Audit (Sphere/Cube/Torus)
|
||||||
|
|
||||||
|
## Strongest Product Flow In Thob
|
||||||
|
- **State Determinism**: Even under high-frequency interaction, Thob never "loses" the state of a material. The 3D viewport is perfectly in sync with the logic layer during configuration.
|
||||||
|
|
||||||
|
## Weakest / Most Awkward Product Flow In Thob
|
||||||
|
- **Scaling Logic**: Managing multi-object mutual exclusivity (Single-select) is currently a manual nightmare. The lack of a "Selection Group" primitive is a major friction point.
|
||||||
|
|
||||||
|
## Top 2 High-Value Discoveries
|
||||||
|
- 1. The **Cylinder Crash**: A reproducible hard-crash specifically for cylinder hiding/visibility.
|
||||||
|
- 2. The **Refresh Reset**: Discovering that selecting variants does not yet persist across browser refreshes in the editor.
|
||||||
|
|
||||||
|
## Top 1 Quick Win Recommendation
|
||||||
|
- Introduce a **"Selection Group"** logic node that handles "Single Select" behavior automagically for any mesh attached to it.
|
||||||
|
|
||||||
|
## Top 1 Deeper Architecture Concern
|
||||||
|
- **Session Persistence**: The reset-on-refresh behavior indicates that active variant states are lost from the editor's memory pool during navigation or refreshes.
|
||||||
|
|
||||||
|
## If A Customer Wanted A Complex 3D Configurator, Could Thob Support It Well?
|
||||||
|
- **PARTIAL**
|
||||||
|
- Why: While Thob is 100% reliable for simple 3-4 option configurators, the manual logic-linking for complex, multi-part selection (50+ parts) is too fragile and prone to "State Explosion" in its current form.
|
||||||
|
|||||||
Loading…
x
Reference in New Issue
Block a user