How netzyn/webplayer works
This repository is a browser-side WebPlayer: the large JavaScript file is the sole indexed core module, while the tree shows separate launcher, page, timer, and TTG HTML experiences. The README points to external developer documentation but gives no workflow details. The JavaScript excerpt is heavily obfuscated and incomplete, so its internal responsibilities and connections cannot be confidently separated; the graph therefore preserves the visible entry point and HTML surfaces without inventing a runtime flow.
Main entry points: NzPlayerWebBrowser.js WebPlayer runtime · launcher.html Launcher view · page.html Player page · timer.html Timer view
Components 12
Browser client
- WebPlayer runtime
NzPlayerWebBrowser.js
HTML experiences
- Launcher view
launcher/launcher.html - Player page
page/page.html - Page JS enable
page/enablejs.html - Timer view
timer/timer.html - Timer JS enable
timer/enablejs.html - Play timeout
timer/playtimeout.html - Close notice
timer/pleaseclose.html - TTG view
ttg/ttg.html - TTG JS enable
ttg/enablejs.html
Other components
- Web user
- Developer docs
Connections 5
- Web user → Launcher view: opens
- Web user → Player page: opens
- Web user → Timer view: opens
- Web user → TTG view: opens
- WebPlayer runtime → Developer docs: guidance
README.md