anshk/builder-research
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: update week2 task2 docs

Browse Source
This commit is contained in:
anshk 2026-04-21 17:17:16 +05:30
parent bf2f0f6cdd
commit e47831aaec
3 changed files with 9 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
Week-2/Task-2/ProductLens.md
View File

@ -5,7 +5,8 @@
- Feature comparison scenes with predefined arrangements. - Feature comparison scenes with predefined arrangements.
- Presentation flows where one click changes scene composition and framing. - Presentation flows where one click changes scene composition and framing.
- Does Thob feel strong enough for this use case? - Does Thob feel strong enough for this use case?
- Partial. The pattern is possible by combining object visibility states and Perspective Camera positions, but button-triggered updates are not reliably synchronized. - Partial. The pattern is possible by combining object visibility states and Perspective Camera positions, but my first instinct was button-based one-click switching and that did not work reliably end-to-end.
- A practical fallback is radio-button switching across preconfigured scene-state combinations.
- What would improve the experience? - What would improve the experience?
- One button should update all linked properties simultaneously, or fast enough that transitions feel instant. - One button should update all linked properties simultaneously, or fast enough that transitions feel instant.
- Better multi-target binding UX for visibility, transforms, and camera props. - Better multi-target binding UX for visibility, transforms, and camera props.

6
Week-2/Task-2/TaskNotes.md
View File

@ -32,8 +32,10 @@ Switch between predefined scene states where each state controls object visibili
-Possible: Partial -Possible: Partial
-Notes: -Notes:
- We can make things like this by creating combinations of object visibility and Perspective Camera position, but the button issue persists. - We can make things like this by creating combinations of object visibility and Perspective Camera position, but the button issue persists.
- My first intuition was to use buttons for one-click state switching, but I could not make that setup reliably work end-to-end.
- We should be able to click the button and it all should be simultaneously or fast enough to not notice. - We should be able to click the button and it all should be simultaneously or fast enough to not notice.
- Current button flow is not reliable enough for multi-property state switching. - Current button flow is not reliable enough for multi-property state switching.
- A practical fallback is using radio buttons to switch between preconfigured scene-state combinations.
-Builder steps: -Builder steps:
- Create scene objects and define visibility combinations. - Create scene objects and define visibility combinations.
- Set Perspective Camera positions for each target state. - Set Perspective Camera positions for each target state.
@ -66,8 +68,8 @@ Switch between predefined scene states where each state controls object visibili
-Is there a workaround? -Is there a workaround?
- Partial workaround. - Partial workaround.
-If yes, what is it? -If yes, what is it?
- Manually set visibility and camera values in sequence. - Use radio buttons to switch between preconfigured scene-state combinations (visibility + transform + camera presets).
- Use simpler, fewer state transitions to reduce button binding complexity. - Keep transitions simpler/fewer to reduce binding instability and improve repeatability.
## Suggested Improvement ## Suggested Improvement
-What should improve in Thob? -What should improve in Thob?

5
Week-2/Task-2/builder/BuilderNotes.md
View File

@ -3,7 +3,7 @@
## Thob Observations from Task Notes ## Thob Observations from Task Notes
- **Possible:** Partial - **Possible:** Partial
- **Implementation used:** Combinations of object visibility states and Perspective Camera positions, with button-based switching attempts. - **Implementation used:** Combinations of object visibility states and Perspective Camera positions; first intuition was button-based one-click switching, but it was not reliable end-to-end.
- **What worked as expected:** - **What worked as expected:**
- Visibility states can be configured for multiple objects. - Visibility states can be configured for multiple objects.
- Camera position presets can be prepared for different scene views. - Camera position presets can be prepared for different scene views.
@ -20,7 +20,7 @@
5. Validate whether transitions are synchronized and repeatable. 5. Validate whether transitions are synchronized and repeatable.
- **Complexity:** Hard - **Complexity:** Hard
- **Main limitation signals:** Editor UX + Event system + Runtime stability concerns. - **Main limitation signals:** Editor UX + Event system + Runtime stability concerns.
- **Workaround status:** Partial workaround only (manual or simplified transitions; full one-click synchronized switching is not dependable yet). - **Workaround status:** Partial workaround only (use radio buttons to switch preconfigured scene-state combinations, and keep transitions simpler while full one-click synchronized switching remains unstable).
## Console Warnings/Errors Seen (Deduplicated) and Probable Meaning ## Console Warnings/Errors Seen (Deduplicated) and Probable Meaning
@ -73,5 +73,6 @@
- Task 2 concept is achievable in thob at a basic level: visibility and camera state combinations can be authored. - Task 2 concept is achievable in thob at a basic level: visibility and camera state combinations can be authored.
- The key product gap is synchronized execution: one button should apply all linked updates simultaneously, but current binding behavior is not reliably atomic. - The key product gap is synchronized execution: one button should apply all linked updates simultaneously, but current binding behavior is not reliably atomic.
- A practical fallback is radio-button-driven switching between preconfigured state combinations.
- Recurring duplicate-registration warnings strongly match the interaction issues seen during multi-prop button setup. - Recurring duplicate-registration warnings strongly match the interaction issues seen during multi-prop button setup.
- Improving binding lifecycle stability and one-click bundled updates should be the highest priority for this task pattern. - Improving binding lifecycle stability and one-click bundled updates should be the highest priority for this task pattern.