bgstaal/multipleWindow3dScene
A quick example of how one can "synchronize" a 3d scene across multiple windows using three.js and localStorage observed · 2026-08-28
Health v2 · maintenance only
27/100
- Activity 0
- Release rhythm 35
- Longevity 72
Flags: no_releases
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 1014
- days_rel: n/a
- days_push: 1008
- n_releases_24m: 0
Adoption not part of the score
18926 stars · 2914 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded
A demo application showing how to synchronize a Three.js 3D scene across multiple browser windows using localStorage for shared state. It includes a WindowManager class handling window lifecycle and synchronization.
Use cases
- render a 3d scene across multiple browser windows
- sync state between browser windows
- learn multi-window web graphics techniques
- build a 3d scene spanning several monitors
- manage window lifecycle with localStorage
When to choose
- you want a reference example of cross-window 3D rendering with Three.js
- you need a simple localStorage-based window synchronization pattern
When to avoid
- you need production-grade synchronization with robust conflict handling
- you require a maintained library with releases and tests
- you need cross-browser support beyond localStorage-based approaches
Facets
application · maturity experimental
graphics state-management web-framework web-development graphics frontend browser threejs localstorage multi-window 3d-graphics demo window-management javascript
1 source
- readme: https://github.com/bgstaal/multipleWindow3dScene · fetched 2026-08-28 · 2d9b88950069
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| bgstaal/multipleWindow3dScene | main | 27 |
For agents
markdown · JSON · MCP: product_card(name="bgstaal/multipleWindow3dScene")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem