You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 21, 2024. It is now read-only.
Josh Field edited this page Mar 6, 2023
·
2 revisions
For re-use, composability and 2D/3D compatibility, we need to separate the concerns of the various aspects of a UI/XRUI implementation. There are three concerns:
ECS System
React Components
Flux State
For example, the XRUI Loading Screen is comprised of three files:
Ideally, the XRUILoadingSystem contains only the 3D specific logic, XRUILoadingDetailView contains only JSX, and LoadingState only contains the Hyperflux state/service/action/receptors. This is such that XRUILoadingDetailView can be used as a 2D asset without needing the 3d logic and renderer, such as for a 2d game or a minimalist page that doesnt need to run a 3d context.