What is the purpose of your templating system? And what does it solve? These questions are the ones I'd ask myself if I was creating one. However, there are a lot of them out there so does your templating system solve a problem and is a solution? or just "yet another templating class"? As its well known templates are made for several reasons such as separating server-side and client-code, separating designers and developers work in team environment, theme able and multy layout and language systems... and a lot more that could me mentioned. I've personally used the HTML_Template_IT package from pear along with Smarty. And now I'm back to normal HTML including for small projects that have a short life cycle, for longer life cycle projects I'd use the IT package. Will never use smarty again; it just makes another layer in the programming not in the system in other words, it becomes another language to add to your programming instead of being a component/tier though it provides much more flexibility than the any other package available. There are a number of articles on Templating I've selected a very criticizing article to share that lives at www.phppatterns.com<http://www.phppatterns.com>. I so much agree with him. At the same time I see a big need for templating. Here is the link to the article. http://phppatterns.com/index.php/article/articleview/4/1/1/ Hope that helps. Regards, M.Saleh.EG <http://M.Saleh.EG> +971-50-4779817
