>>>>> "DB" == Dan Boger <[EMAIL PROTECTED]> writes:
DB> 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. DB> I've been trying to be good, and seperate content from presentation. DB> But since starting using Mason, I find that's much harder to do? Yes DB> Mason is hailed often as a Very Good Thing(tm), so am I missing DB> something? Most of the actual logic in my code sits in Class::DBI DB> modules, but there's quite a bit of code in the Mason files - to the DB> point that if I had a HTML Jocky working with me, they'd have to DB> understand Mason at least somewhat. in the templating world, there are two camps, code embedded in the text and code separated from the text. i have always been in the code outside the text camp and i have rolled my own tiny templaters in that way for years. i did use mason on one page on my site (i am friends with a key mason guy) and it is ok but as i said, the wrong camp for me. i am in a new project where templating is needed and we are going with template toolkit. it does allow code in text but that is disabled by default and discouraged. i like that attitude. anyhow, my reasons for separating code and text is just that they are very different jobs and that allows a code monkey to be different than the html monkey. this scales better to larger projects. it makes the text easier to read (less code noise). it makes the system more modular too. uri -- Uri Guttman ------ [EMAIL PROTECTED] -------- http://www.stemsystems.com --Perl Consulting, Stem Development, Systems Architecture, Design and Coding- Search or Offer Perl Jobs ---------------------------- http://jobs.perl.org _______________________________________________ Boston-pm mailing list [email protected] http://mail.pm.org/mailman/listinfo/boston-pm
