Skip to content
This repository has been archived by the owner on Jun 6, 2020. It is now read-only.

Plans for the scene graph #1

Open
5 tasks
zpl-zak opened this issue Feb 2, 2018 · 0 comments
Open
5 tasks

Plans for the scene graph #1

zpl-zak opened this issue Feb 2, 2018 · 0 comments
Assignees

Comments

@zpl-zak
Copy link
Contributor

zpl-zak commented Feb 2, 2018

I'd like to address some thoughts and ideas I'd like to apply this month (February as of writing), that should improve QoL and also introduce new features:

  • rebrand the module to Scene graph as it's closer to what the module is intended to do
  • work out mesh flattening to avoid memory leaks in heavily modified space
  • introduce hierarchical structure to the nodes (e.g. nodes can have parent and therefore their transformation is relative from parent's origin)
  • add rotation and scale as a field for node's transformation (and introduce transformation structure as well)
  • possibly introduce different types of spaces (binary space, sparse octree space, ...)

Note, these tasks are all work in progress and may or may not be completed.

Considering the fact that this version extends the purpose of this module and possibly introduces collisions with the original ideals, I will keep version-v3 updated if there would be any issues found. (Mesh flattening will make it into v3 as well.)

EDIT: After further thinking, these ideas should be introduced in a new repository. I will keep the issue opened for convenience.

@zpl-zak zpl-zak self-assigned this Feb 2, 2018
@zpl-zak zpl-zak changed the title Plans for the v4 Plans for the ~~v4~~ scene graph Feb 2, 2018
@zpl-zak zpl-zak changed the title Plans for the ~~v4~~ scene graph Plans for the scene graph Feb 2, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant