http://karoshiethos.com/2008/12/22/as3-class-to-asset-linkage-something-different/ Navigating the treacherous waters of interactive technology Wed, 4 Aug 2010 08:56:23 -0400 http://wordpress.org/?v=2.9.2 hourly 1 http://karoshiethos.com/2008/12/22/as3-class-to-asset-linkage-something-different/comment-page-1/#comment-330 jon williams Tue, 11 May 2010 15:32:20 +0000 http://karoshiethos.com/?p=157#comment-330 Not as much. I've recently become more comfortable leaving the assets inside a "skin" container (layout in the above example). Effectively, I suppose that means I'm embracing the composition pattern. It depends on what the goals of your architecture are though. Does it make sense to define an interface if you'll have more than one skin implementation? "Is-A vs Has-A" should become a mantra that you don't have a pat answer for. I'm a big fan of having a LOT of different approaches in my toolbox. I'm sure I'll reach for this one again eventually. Not as much. I’ve recently become more comfortable leaving the assets inside a “skin” container (layout in the above example). Effectively, I suppose that means I’m embracing the composition pattern.
It depends on what the goals of your architecture are though. Does it make sense to define an interface if you’ll have more than one skin implementation? “Is-A vs Has-A” should become a mantra that you don’t have a pat answer for. I’m a big fan of having a LOT of different approaches in my toolbox. I’m sure I’ll reach for this one again eventually.

]]> http://karoshiethos.com/2008/12/22/as3-class-to-asset-linkage-something-different/comment-page-1/#comment-324 Pavel fljot Sat, 01 May 2010 08:50:00 +0000 http://karoshiethos.com/?p=157#comment-324 Are you still doing it this way?? Are you still doing it this way??

]]>