Timeline for How should one modularly implement related objects?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 16, 2020 at 10:01 | history | edited | CommunityBot |
Commonmark migration
|
|
| Jun 24, 2015 at 21:34 | vote | accept | Jordan | ||
| Jun 24, 2015 at 19:38 | comment | added | Steven A. Lowe | @Jordan: 'service' in this context is simply a helper/utility class or method that performs some calculations on behalf of other objects. Good luck! | |
| Jun 24, 2015 at 8:02 | comment | added | Jordan | I'm only familiar with services from client/server networking idioms, so I'm not sure that I entirely absorbed your answer, but I do think that you're right about how I need to stop thinking of those things as real objects in their own right and instead as add-ons for their host object. Specifically, I'm leaning toward my second original option (pointers) and having some way of letting the host object associate and disassociate freely with various e.g. graphical representations. Also, thanks for the Unreal source link -- it looks rather intimidating, but I will definitely give it a go. | |
| Jun 23, 2015 at 19:51 | history | answered | Steven A. Lowe | CC BY-SA 3.0 |