> I don't think it's off track ... I have seen that i have to be very careful > how i think about my model tho' > > For instance, if we bring in a concept of a Page here, a Page can have > either a Text blog post, a Photo blog post, or comments. Now what? > > Then of course, you might want to add a few more pods to your page, of > course, for things like google ads or teasers. Now we have Pods on a Page. > Now what?
That's a great point. I think the approach then becomes a Page object that has a data structure (perhaps a tree) of UIObjects. UIObject can simply be a class that TextArticle, PhotoArticle, Pod, etc. extends. It's kind of the way the Flex object model works. Note that Comment might not extend UIObject, since you can't really have a Comment living on its own (a comment regarding what?!). Again, this seems like a great use of polymorphism... plug in whatever kind of UIObject you want, the Page doesn't care, as long as the UIObject services are available. If you come up with other, specialized page elements in the future, just extend the UIObject class and you're all set. ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com). An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
