Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rewrite assets and loading to use atelier-assets #159

Open
1 task done
azriel91 opened this issue Mar 12, 2020 · 2 comments
Open
1 task done

Rewrite assets and loading to use atelier-assets #159

azriel91 opened this issue Mar 12, 2020 · 2 comments
Labels
F: core Core application functionality - managing resources, state, etcetera. W: third party Waiting on a third party's action.
Milestone

Comments

@azriel91
Copy link
Owner

In GitLab by @azriel91 on Aug 27, 2019, 13:23

  • Each asset type needs its own type uuid.
  • Each asset needs its own asset uuid.

Generating UUIDs for each component sequence:

From @Kae:

I think there are two features that would help you in addition to SerdeImportable:

  • Handle references that are registered by path instead of UUID (resolved transparently by the framework): Handling assets with path references in the build process amethyst/distill#2
  • Custom build pipelines - a way to run code after import, but before loading i.e. "offline", to transform an asset from one asset type to another asset type. This can be used to transform from AOS to SOA for example.

Notes:

  • Set up CI to have capnp on PATH.
@azriel91 azriel91 added F: core Core application functionality - managing resources, state, etcetera. W: third party Waiting on a third party's action. labels Mar 12, 2020
@azriel91 azriel91 added this to the Asset Loading Pipeline milestone Mar 12, 2020
@azriel91
Copy link
Owner Author

In GitLab by @azriel91 on Aug 29, 2019, 09:11

unassigned @azriel91

@azriel91
Copy link
Owner Author

In GitLab by @azriel91 on Sep 3, 2019, 11:13

Maybe use warmy instead, as it is looks ready for our use case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
F: core Core application functionality - managing resources, state, etcetera. W: third party Waiting on a third party's action.
Projects
None yet
Development

No branches or pull requests

1 participant