On Fri, Jan 14, 2005 at 08:00:17PM -0500, Grant M. wrote: > My biggest objection to PHP is that most developers write pages with > the code entirely or mostly within the page, leading to an inherent > inability to modify the layout without having at least a cursory > understanding of the language. This means that everytime a > modification is made to the design of the page, it typically involves > two groups of people as opposed to one; the HTML jockies, and the code > jockies, leading to a much more expensive maintenance cycle. Now don't > flame me, I am SURE that all of you separate your code from your > layout <snicker>, but I have encountered this on most every single > incarnation of PHP web design that I have seen, and I am just making > the observation.
I've been trying to be good, and seperate content from presentation. But since starting using Mason, I find that's much harder to do? Yes Mason is hailed often as a Very Good Thing(tm), so am I missing something? Most of the actual logic in my code sits in Class::DBI modules, but there's quite a bit of code in the Mason files - to the point that if I had a HTML Jocky working with me, they'd have to understand Mason at least somewhat. Am I missing something? -- Dan Boger [EMAIL PROTECTED] _______________________________________________ Boston-pm mailing list [email protected] http://mail.pm.org/mailman/listinfo/boston-pm
