Apr 7 at 10:01pm, Robert Cummings wrote: > Smarty is a bit of a hack too... why do I need to declare my templates > within the PHP code? If I'm an HTML designer I'd like to create a new > page, include templates, use some data that's been made available and > have it all in the template. I sure as heck wouldn't want to have joe > programmer edit the main page, add support for importing my template.
I like Smarty because it solved many of the problems I was having trying to tackle the problems manifest when using no templating strategy. Actually, InterJinn has been on my radar screen for a while now, and thanks to your timely plug, I think I'll try it out and see how it compares. Incidentally, your posts on the Smarty list are what had me considering InterJinn in the first place.. how subversive of you! :) I'm not married to Smarty, I just think that it's got a lot more to offer than many PHP coders give it credit for after a mere cursory evaluation. Further, many of the people who shun templating systems aren't really working with web applications as much as simple PHP scripts, where templating solutions are much less necessary. I think we're on the same side. Perhaps I just haven't yet seen the light. I'll give InterJinn a go. I hope it's all you say it is. One thing we can both agree on is that templating is not inherently redundant with PHP. --Kelly -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
