|
@@ -9,6 +9,7 @@
|
|
|
* runner proposal: https://en.wikipedia.org/wiki/Fork%E2%80%93join_model https://slide-rs.github.io/specs/03_dispatcher.html
|
|
* runner proposal: https://en.wikipedia.org/wiki/Fork%E2%80%93join_model https://slide-rs.github.io/specs/03_dispatcher.html
|
|
|
* is it possible to iterate all the components assigned to an entity through a common base class?
|
|
* is it possible to iterate all the components assigned to an entity through a common base class?
|
|
|
* work stealing job system (see #100)
|
|
* work stealing job system (see #100)
|
|
|
|
|
+* can we do more for shared libraries? who knows... see #144
|
|
|
* meta: sort of meta view based on meta stuff to iterate entities, void * and meta info objects
|
|
* meta: sort of meta view based on meta stuff to iterate entities, void * and meta info objects
|
|
|
* meta: move-to-head optimization when searching by name on parts (data, func, etc)
|
|
* meta: move-to-head optimization when searching by name on parts (data, func, etc)
|
|
|
* hashed string: add implicit check on construction for uniqueness (optional)
|
|
* hashed string: add implicit check on construction for uniqueness (optional)
|
|
@@ -21,11 +22,7 @@
|
|
|
* events on replace, so that one can track updated components? indagate impact
|
|
* events on replace, so that one can track updated components? indagate impact
|
|
|
* tags revenge: if it's possible, reintroduce them but without a link to entities (see #169 for more details)
|
|
* tags revenge: if it's possible, reintroduce them but without a link to entities (see #169 for more details)
|
|
|
|
|
|
|
|
-Required test:
|
|
|
|
|
-* can we do more for shared libraries? who knows... see #144
|
|
|
|
|
-* type_info::hash_code can be used in place of family when it comes to working with dlls
|
|
|
|
|
-
|
|
|
|
|
Ready to go:
|
|
Ready to go:
|
|
|
* stealing archetype-like model on top of EnTT (design completed, wip dev)
|
|
* stealing archetype-like model on top of EnTT (design completed, wip dev)
|
|
|
* write/show how to create an archetype based model on top of EnTT
|
|
* write/show how to create an archetype based model on top of EnTT
|
|
|
-* do not include it in EnTT, it breaks the pay-for-what-you-use principle all the ways
|
|
|
|
|
|
|
+* note: do not include it in EnTT, it breaks the pay-for-what-you-use principle all the ways
|