Timeline for A more data oriented design approach to Entity Component System
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 18, 2017 at 19:35 | comment | added | Jason | Okay sounds good, I'll check it out. | |
| Mar 18, 2017 at 19:27 | comment | added | Christophe | @Jason it's a very nice answer and exactly in the same direction than mine (although with more explanations and details). In fact his Ball example illustrates in more details the OOP approach I suggested when i wrote about making "more comprehensive entities". And the ECS approach is one of the core elements of McShaffry's book, in which Entity/component is recommended in preference to a static inheritance. The book goes by the way in more details about how this interacts with physics, audio, video or scripting subsystems. | |
| Mar 18, 2017 at 19:09 | comment | added | Jason | Thank you for the insight. I asked this same question on another thread and got this response gamedev.stackexchange.com/questions/138438/…. Basically, he states that encapsulation is still present, you just have to think about it in a different way, with subsystem functions still acting like member functions. Though he seems to implement things slightly differently from my current implementation. Wondered if you had any specific thoughts on his response? | |
| Mar 18, 2017 at 18:46 | history | answered | Christophe | CC BY-SA 3.0 |