tag:blogger.com,1999:blog-4037079221500014725.post41187299892515011..comments2023-11-02T10:20:34.251-04:00Comments on Everyman Software: Dynamic Assets: Part I - DefinitionJosh Adellhttp://www.blogger.com/profile/13146384900735324084noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-4037079221500014725.post-17841610383347770332023-05-05T05:52:59.058-04:002023-05-05T05:52:59.058-04:00Thank you ffor thisThank you ffor thisPizza Cookbookshttps://www.pizzapins.com/cookbooks/noreply@blogger.comtag:blogger.com,1999:blog-4037079221500014725.post-23144305585919354552011-04-02T09:58:46.631-04:002011-04-02T09:58:46.631-04:00In a post coming soon, I'll show how we constr...In a post coming soon, I'll show how we construct these things. The short answer is that Assets don't really have behaviors; they just have properties that define their values and how they should be displayed.<br /><br />The longer answer is that we could have a specific class for an Asset type that needs special behaviors. The class would then be responsible for building itself correctly, and the factory that creates Assets for us would need to know to instantiate that class instead of the generic Asset class.Josh Adellhttps://www.blogger.com/profile/13146384900735324084noreply@blogger.comtag:blogger.com,1999:blog-4037079221500014725.post-19992329706041760262011-04-02T07:23:44.933-04:002011-04-02T07:23:44.933-04:00This looks pretty interesting! Sounds like this ap...This looks pretty interesting! Sounds like this approach will work fine, unless/until you start needing to define different behaviors for asset types. Then what?Michael Pelz-Shermanhttps://www.blogger.com/profile/16018206554765270841noreply@blogger.com