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

Library API #27

Open
3 tasks
juliusikkala opened this issue Mar 27, 2023 · 0 comments
Open
3 tasks

Library API #27

juliusikkala opened this issue Mar 27, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@juliusikkala
Copy link
Member

It would be very useful to make the core of Tauray operate more like a library, where it could be integrated as a part of other projects.

One of the potential issues with this is that many parts of Tauray may currently assume that the number of objects or materials in the scene does not change while the program is running. Tauray also has this kind of odd architecture where it avoids re-recording command buffers like plague. This most likely won't work well if the scene composition constantly changes.

One thing I would link with this is that I really want to get rid of the object-oriented, inheritance-based node design and replace that stuff with an entity-component style approach. I've done this once in a non-public Vulkan renderer, and it seemed to make the scene handling much simpler in the end.

  • Move from scene class hierarchy to ECS
  • Ensure everything works when scene composition changes during runtime
  • Specify a public API
@juliusikkala juliusikkala added the enhancement New feature or request label Mar 27, 2023
This was referenced Mar 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant