Timeline for Child to Parent linking - bad idea?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 22, 2012 at 17:29 | vote | accept | Thraka | ||
| Nov 22, 2012 at 17:28 | comment | added | Thraka | Your edit makes me think about the VisualTreeHelper in WPF\Silverlight. This allowed you to query about the relationship of the current control was to the rest of the UI systems controls. I guess I could implement something like this because I also have a root control that will host everything else. Thanks!! | |
| Nov 22, 2012 at 14:20 | history | edited | Telastyn | CC BY-SA 3.0 | elaboration due to question edit. |
| Nov 22, 2012 at 14:14 | comment | added | Telastyn | @ManojR - object oriented programming was never related to real life objects. | |
| Nov 22, 2012 at 6:05 | comment | added | Thraka | Thanks for this answer so far. I've added more context in my original question. | |
| Nov 22, 2012 at 5:41 | comment | added | Manoj R | The answer is right. But if child to parent linking is a bad idea, then object oriented programming is no longer related to real life objects. Isn't there any way to make this a good thing? | |
| Nov 22, 2012 at 3:36 | comment | added | rperetti | This is a good answer and you should probably consider all the points raised by it and see if they apply to your problem. Having said that though I don't think it is the end of the world if you start with the reference as a simple implementation and refactor it out when/if things get out of hand. | |
| Nov 22, 2012 at 3:17 | history | edited | Telastyn | CC BY-SA 3.0 | added 5 characters in body |
| Nov 22, 2012 at 3:10 | history | answered | Telastyn | CC BY-SA 3.0 |