* Rory Browne <rory.browne@xxxxxxxxx>: > > This has all been done before, and in a number of ways. If you really > > *must* build your own templating class, go and thoroughly review the > > code of those that already exist: Smarty, Savant, paTemplate, > > FastTemplate, etc. Figure out how each solved the problems. Then > > determine if you can improve upon their solutions. > > This has all been done before, and I'm assuming that the James knows, > and has seen that before, since he used the same common method names, > as is in many php templating systems. $class->assign has been used in > any templating system I've ever seen(although to be honest I haven't > seen that many). > > I don't think the fact that it has been done before should inhibit him > from doing it again. Carrying out the process, is one of the most > educational ways, and perhaps one of the most enlightening ways to see > how a process works. I agree -- that's why the statement "then determine if you can improve upon their solutions." This wasn't a, "you won't be able to," but more of a, "look for places where you feel it could be done better" type of statement. Templating is tricky. It adds overhead on the processing end, but increases developer/designer efficiency. Finding a happy medium is the challenge. -- Matthew Weier O'Phinney | WEBSITES: Webmaster and IT Specialist | http://www.garden.org National Gardening Association | http://www.kidsgardening.com 802-863-5251 x156 | http://nationalgardenmonth.org mailto:matthew@xxxxxxxxxx | http://vermontbotanical.org -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
