Update:Archive/2.0/Developers/Templates: Difference between revisions

Line 107: Line 107:


But if we can use CSS properly, all HTML output will be exactly the same with the exception of DOM identifiers when appropriate, using templating or skinning the whole app should be reduced to a matter of switching stylesheets.  From there, it's just a matter of packaging your markup properly, which is not something I see us needing a separate tool for.
But if we can use CSS properly, all HTML output will be exactly the same with the exception of DOM identifiers when appropriate, using templating or skinning the whole app should be reduced to a matter of switching stylesheets.  From there, it's just a matter of packaging your markup properly, which is not something I see us needing a separate tool for.
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)


=== alanjstr's take ===
=== alanjstr's take ===
Confirmed users
503

edits