"> Also, the display portion of my intranet will be so custom, that it > wouldn't make sense to spend the time to make it very reusable.
I think this is one of the key insights here: display "logic" is typically much less generic and much less reusable than business logic. A Person CFC can, if well-designed, be applicable in several situations (perhaps with some additional work, or even through extension) but how to display a Person is likely to be very specific to the current application." I agree. "If you look at MVC, the elements of the model tend to be more abstract and reusable - and much less tainted by their environment - than the elements of the view. The same model can be reused for a Flash view, an HTML view and a WAP view." My first deadline is to get the site usable with mainstream browser use. Once I'm done with that, I'm going to retrofit it for handheld browser use such as Palm OS or Win CE. Would the same custom tag generate HTML for desktop browser AND handheld browsers? Would you split the different "views" into separate custom tags? "In my opinion, it's OK for the views to be 'environment aware' but it's important for the model to be as 'environment neutral' as possible." I agree. ">> Example 2 >> <cf_myTag firstName="#Session.firstName#"> >> <cfoutput>#Attributes.firstName#</cfoutput></cf_myTag> To me, this adds unnecessary complication / redundancy. It seems less readable and less maintainable to me." I totally agree. Thanks M!ke
<<winmail.dat>>
