Overhaul load state machine

ndubois-legion commented 2 years ago

Summary

Leaner API & make loading steps more configurable per type

Current State

Currently, loading is klunkly. APIs should probably have a single entry point for accessing resources, in both offline & runtime. We should also have a way for defining the loading graph per resource type, or just per resource. Use Reference in the APIs, and avoid the mix of Handle, HandleUntyped, ReferenceUntype. Are those really useful?

Tasks

[x] Remove all the AssetRegistry::loadXXX() APIs and keep a single async one.
[x] Remove the loading thread
[x] Implement entity
[x] Implement an example, like shader and texture
[ ] Review API with Rendering team ...

ndubois-legion commented 2 years ago

@smartel-legion Can you update the description of this issue before our planning exercise please? @aganea says it's larger than initially.

ndubois-legion commented 2 years ago

Going well, looking at physics playground. Most tests are passing, some still deactivated.

Merge with no_metadata branch (1d)
Look at deactivated tests (3d)
Will be missing the Rendering refactor, implement the installers (3w)

aganea commented 2 years ago

Update: mainly done in 'maverick' branch. Lacking integration with graphics. Stabilization will come after in the last sprint of M3.

legion-labs / legion