Quote:
|
Originally Posted by funkydunk
I was of that opinion to start with, being a devout PHP junky as I could not get into (or didn't have the time to study) smarty at all.
|
I certainly don't mean to cause a ruckuss over Smarty. I think the biggest reason why I have such a problem with it is because I've been building my own php-based "templatized" websites for quite a while now.
Smarty makes a big deal that it "facilitates a managable way to separate application logic and content from its presentation". Yeah, so what? It's really easy to do that with just some basic PHP, and I don't have to learn a new language or syntax.
Here is what all my site pages look like:
<include global configuration file>
<define some page/section specific variables>
<include global header>
Page content goes here.
<include global footer>
What's so hard about that? The configuration file holds stuff like path information and some global functions, such as page title display. The page itself has variables such as $section, $subsection, $pagetitle, $printable, etc. and the headers and footers contain the "look" of the site, including all the logic code necessary to build navigation, etc.
Doing it my own way with just a few files and some common sense, I can totally change a site's look and architecture in a few minutes, no matter how big the site is. So that's why I just can't grasp why Smarty is necessary. I just think it complicates things unnecessarily.
Just my two cents.