3,035
edits
(→Templating Engines for Consideration: Make these link to the Site for the Template engine in question) |
|||
Line 110: | Line 110: | ||
: mvl's comments: A template engine is definitly worth it. It is not about CSS. It is about readable code. html all over the php code makes the php unreadable. php all over the html code makes the html unreadable. You really want to split it. (and having it split up reduces the risk of cvs conflicts) --[[User:Mvl|Mvl]] 10:51, 22 Jan 2005 (PST) | : mvl's comments: A template engine is definitly worth it. It is not about CSS. It is about readable code. html all over the php code makes the php unreadable. php all over the html code makes the html unreadable. You really want to split it. (and having it split up reduces the risk of cvs conflicts) --[[User:Mvl|Mvl]] 10:51, 22 Jan 2005 (PST) | ||
: morgamic's comments: I think I may have not been thinking enough about the people responsible for UMO's design. The need for a good engine that can accomodate them and allow them the ability to change look and feel without mucking with CVS would be a great feature -- mconner helped explain that to me. UMO will be very different from Bouncer in that respect, so maybe I have to read up more on templating engines. :) | |||
=== alanjstr's take === | === alanjstr's take === |
edits