Mercury: A Messaging Framework for Modular UI Components
summary
A messaging framework called Mercury uses relay nodes and responders to decouple UI logic, implemented as a Unity reference implementation that routes messages with an mmmInvoke call and supports a network responder for automatic state synchronization. Examples show teleportation across a distributed scene graph, remote-expert grab-and-replicate working without custom network code, and reusable visualization components; the system runs in real-time, aims to avoid extra programmer propagation code, and is on GitHub.
AI-written summary · about
chapters (12)
- 0:00Introduction to Mercury
- 1:08Problem with UI component coupling
- 2:33Observer pattern in Mercury
- 4:38Mercury framework overview
- 6:23Relay nodes and responders
- 8:48Teleportation use case
- 10:57Remote expert guidance system
- 12:20Rotation guidance visualization
- 13:27Future work and challenges
- 14:27Conclusion and GitHub link
- 14:50Q&A: Scalability concerns
- 16:17Q&A: Comparison with web patterns
related talks
53mMessaging: The fine line between awesome and awful
56mFluxing Up Your .NET Apps
37mMeteor - A Full Stack Framework For Building Pure JavaScript Apps
27mA Journey to Building a Server Driven UI Framework
43mMobius-Loopy UI Architecture
24mSolving the Puzzle of Real-Time Collaboration using the Fluid Framework
14mCross platform UI
34mFunctional UIs and Unidirectional Dataflow