> Point well-made. I suppose doing it the mixed way might have repercussions > later on if/when the site grows. Perhaps while the code is still fresh in my > mid, it might be worth the effort to separate it. > > However, for a good part of the site, I've used CSS for appearance details, > and controlling a lot of stuff that changes from page-to-page. It's very easy > to change all or some of the pages from the CSS scripts. But, for the most > part, not much of the actual php scripts COULD change, so that's why I've > never bothered to separate html from php. Perhaps I wrong, but . . .
I think it is a case of horses for courses - you are working on what sounds like a fairly small project, and "templatizing" your code may be more trouble than it is worth, so whatever feels best for you... -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
