Timeline for A more data oriented design approach to Entity Component System game engine
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 11, 2017 at 11:45 | comment | added | Quentin | @Jason there's no real way to put a limit on that -- how would it look like? No more than X components for a system? This is the same self-discipline as always: don't put a ton of unrelated data into a single object, don't make huge functions that do too much. Also, if you want to actually have that explicit function signature inside your systems, C++ can do this, too! I have made something similar here. That one does more than what you need, but the part that detects the function's parameters and provides suitable arguments should be useful. | |
| Mar 10, 2017 at 23:47 | comment | added | Jason | Perfect. This gets me to think about encapsulation in a whole different way. Let me ask you though, in your example you're passing the data needed by a specific system through parameters of the function which helps to limit the number of components each system can use. In my implementation currently, all systems have access to all components which means there could be systems that change the state of many different components. While I would try and avoid this, nothing yet is really inhibiting me from doing so. Do you think this is enough of a concern to merit changing my ECS implementation? | |
| Mar 10, 2017 at 21:44 | vote | accept | Jason | ||
| Mar 10, 2017 at 19:34 | history | edited | James | CC BY-SA 3.0 |
Just restating the meaning of the acronym as was done in the OOP section.
|
| Mar 10, 2017 at 9:40 | history | answered | Quentin | CC BY-SA 3.0 |