Re: Re: Separate PHP Code From HTML || Pros & Cons?

On Sat, October 7, 2006 4:24 pm, sit1way wrote: > I would dearly love to have a base CMS repository that all sites would > draw > on, extending the base CMS in the event that a particular client has > need of > customization. Some combo of Linux and Apache would do the trick; > e.g. PHP > requests for any of my sites would point to say, "/home/cms/includes/" You might want to consider just installing subversion and using svn to control your own source code. > Now, the other issue I'd like to address is separating PHP code logic > from > site HTML. This has been beaten to death here so often... > I've often heard the mantra, "separate code from HTML", but it seems > ridiculous at times to include tiny HTML snippets that can easily be > echoed > out, or stored in a variable. Smarty goes to the extreme in > separating code > from HTML, but looking at their templating system, I wonder what's the > point? Is it the end of the world if you've got a few choice if, > then, else > statements in your HTML templates? I personally think you're doing a fine thing. Going whole-hog template with no PHP allowed might be more useful for larger teams where some HTML designer is supposed to know NOTHING about PHP -- Though, honestly, teaching an HTML designed just enough PHP to deal with your not-quite-templates is probably easier and better in the long run, imho. Just use whatever works for you. -- Some people have a "gift" link here. Know what I want? I want you to buy a CD from some starving artist. http://cdbaby.com/browse/from/lynch Yeah, I get a buck. So?