docs: added week 2 general notes and personal summary
This commit is contained in:
parent
e5b0d17124
commit
31aa3a500f
@ -0,0 +1,17 @@
|
||||
# Week 2 - General Diagnostic Audit Notes
|
||||
|
||||
## Core Workflow Highlights
|
||||
- **UI Integration**: The `RadioGroup + For-Loop` pattern is the most professional way to build configurators in Thob.
|
||||
- **Linking Logic**: Using selection IDs to bind UI states to 3D properties (Material maps, visibility) is reliably performant.
|
||||
- **Visual Fidelity**: High-quality texture mapping (Earth/Moon) is handled without UV distortion or scene lag.
|
||||
|
||||
## Key Technical Signals (Console Analysis)
|
||||
- `GetBindingData... method already registered`: Persistent redundant logic registration during UI loops.
|
||||
- `uncontrolled to controlled`: Initial state-sync delay during component mounting.
|
||||
- `No HydrateFallback`: Standard framework hydration noise.
|
||||
|
||||
## Critical Limitation Audit
|
||||
1. **Discovery Gap**: The logic syntax (e.g., `$context.item_currentItem.id`) is highly proprietary and non-discoverable without documentation.
|
||||
2. **Asset Pipeline**: Discovered a silent upload failure for files > 5MB.
|
||||
3. **Interaction Engine**: 3D objects lack native "On Click" triggers; all selection must be simulated via 2D UI.
|
||||
4. **Primitive Stability**: Observed periodic crashes specifically when interacting with Cylinder geometry.
|
||||
@ -1,27 +1,27 @@
|
||||
# Divya — Week 2 Summary
|
||||
|
||||
## Tasks Completed
|
||||
- Task 1:
|
||||
- Task 2:
|
||||
- Task 3:
|
||||
- Task 4:
|
||||
- Task 1: Material Switcher (Color Swaps)
|
||||
- Task 2: Texture Switcher (Planet Surface Swaps)
|
||||
- Task 3: Product Option Switcher (Geometric Visibility Toggles)
|
||||
- Task 4: Selection/Highlight (Interaction Simulation)
|
||||
|
||||
## Strongest Product Flow In Thob
|
||||
-
|
||||
- **Material Swapping**: The `MaterialVariant` system is exceptionally fast and the visual fidelity of the renderer handles real-time property shifts perfectly.
|
||||
|
||||
## Weakest / Most Awkward Product Flow In Thob
|
||||
-
|
||||
- **3D Selection**: The inability to click a mesh directly to select it forces a "disconnected" UX where all triggers must live in the 2D layer.
|
||||
|
||||
## Top 2 High-Value Discoveries
|
||||
- 1.
|
||||
- 2.
|
||||
- 1. The **Proprietary Logic Gap**: Discovering that interaction IDs depend on specific, non-documented syntax (e.g., $context).
|
||||
- 2. The **Asset Pipeline Cap**: Identifying the silent 5MB limit for high-resolutions textures.
|
||||
|
||||
## Top 1 Quick Win Recommendation
|
||||
-
|
||||
- Implement an **Expression Dropdown** in the binding panel so users can see valid logic paths without memorizing code.
|
||||
|
||||
## Top 1 Deeper Architecture Concern
|
||||
-
|
||||
- **Binding Redundancy**: The high-volume console warnings during loops suggest the internal observer system is overactive and may cause performance bottlenecks in complex scenes.
|
||||
|
||||
## If A Customer Wanted A Simple 3D Configurator, Could Thob Support It Well?
|
||||
- Yes / Partial / No
|
||||
- Why:
|
||||
- **YES**
|
||||
- Why: For 90% of use cases (swapping colors/materials/parts), Thob is extremely powerful, visual, and stable. The visual results are production-ready.
|
||||
Loading…
x
Reference in New Issue
Block a user