Timeline for Relation between an object and its renderer
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 25 at 22:39 | answer | added | Antares | timeline score: 0 | |
| S Aug 22 at 11:42 | history | mod moved comments to chat | |||
| S Aug 22 at 11:42 | comment | added | DMGregory♦ | Let's continue this discussion in chat. We try to avoid extended back-and-forth conversations in comment threads here. 😉 | |
| Aug 21 at 0:10 | answer | added | agone | timeline score: 1 | |
| Aug 20 at 19:12 | comment | added | Gerry Schmitz | You can either "give" an object a particular ability; or have another class act as a "proxy" / adapter. The only example that might be familiar is the .NET "table adapter"; it's main purpose is to "fill" datatables; when one might say tables should "fill themselves". The "adapters" (IMO) allow you to isolate common functionality in the context of "acting on" versus "acting"; which in certain case, is just easier to get one's head around. A totally new behaviour doesn't mean having to go back and modify the object ... use an adapter / component / plug-in / extension instead. | |
| Aug 20 at 0:16 | comment | added | DMGregory♦ | This looks like it might be worth taking to the Code Review StackExchange instead. They handle cases where you have working code and want advice on how it can be improved. | |
| S Aug 20 at 0:11 | review | First questions | |||
| Aug 21 at 15:37 | |||||
| S Aug 20 at 0:11 | history | asked | X Y | CC BY-SA 4.0 |