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.

Sign up for GitHub

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

Jump to bottom

Decouple asset loading processes from the graphics submodule. #67

Open
ImmutableOctet opened this issue Jul 20, 2023 · 1 comment
Open

Decouple asset loading processes from the graphics submodule. #67

ImmutableOctet opened this issue Jul 20, 2023 · 1 comment
Assignees
@ImmutableOctet
Labels
Good practice Indicates a proposed change that would be seen as good practice module: engine For features that involve the `engine` module. (optional) module: graphics For features that involve the `graphics` module. (optional) Refactor Used to flag significant codebase refactors

Comments

@ImmutableOctet
Copy link
Owner

We currently integrate many of the lower-level asset processing routines in the graphics submodule, rather than separating this into its own portion of the codebase (e.g. the engine module).
@ImmutableOctet ImmutableOctet self-assigned this Jul 20, 2023
@ImmutableOctet ImmutableOctet added Good practice Indicates a proposed change that would be seen as good practice module: engine For features that involve the `engine` module. (optional) module: graphics For features that involve the `graphics` module. (optional) Refactor Used to flag significant codebase refactors labels Jul 20, 2023
@ImmutableOctet
Copy link
Owner Author

To add to the description; we currently handle asset loading via assimp, which ideally wouldn't have any required linkage with the graphics submodule. Longer term, this would make for separating of graphics into a runtime module much easier.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ImmutableOctet ImmutableOctet

Labels
Good practice Indicates a proposed change that would be seen as good practice module: engine For features that involve the `engine` module. (optional) module: graphics For features that involve the `graphics` module. (optional) Refactor Used to flag significant codebase refactors
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ImmutableOctet