Comments on: Why doesn’t Panel extend LayoutContainer? http://dougmccune.com/blog/2008/01/12/why-doesnt-panel-extend-layoutcontainer/ A blog about Adobe Flex Mon, 13 Oct 2008 04:36:57 +0000 http://wordpress.org/?v=2.0.7 by: Rick Winscot http://dougmccune.com/blog/2008/01/12/why-doesnt-panel-extend-layoutcontainer/#comment-57825 Wed, 20 Feb 2008 21:30:19 +0000 http://dougmccune.com/blog/2008/01/12/why-doesnt-panel-extend-layoutcontainer/#comment-57825 Inheritance would be easy... but in the end your subclasses would become heavily dependent on the parent implementation. This shouldn't be a problem as long as you understand the implications and you are fine with it. Deep object hierarchies can and usually do become a problem. Before you say yes to inheritance you should consider composition (which is what they are doing). The duplication buys you improved encapsulation/compartmentalization and can insulate your application from or ease the pains of refactoring when parent implementations change. Just a thought. Peace. Inheritance would be easy… but in the end your subclasses would become heavily dependent on the parent implementation. This shouldn’t be a problem as long as you understand the implications and you are fine with it. Deep object hierarchies can and usually do become a problem. Before you say yes to inheritance you should consider composition (which is what they are doing). The duplication buys you improved encapsulation/compartmentalization and can insulate your application from or ease the pains of refactoring when parent implementations change. Just a thought. Peace.

]]> by: Boubalou http://dougmccune.com/blog/2008/01/12/why-doesnt-panel-extend-layoutcontainer/#comment-44817 Mon, 14 Jan 2008 15:41:52 +0000 http://dougmccune.com/blog/2008/01/12/why-doesnt-panel-extend-layoutcontainer/#comment-44817 The response from Flex should be: "Because we can." ;) The response from Flex should be:

“Because we can.”

;)

]]>