The PEAR ITX Templating System - The conclusion
(Page 5 of 5 )
What can be said at the end of this tutorial?
The separation of code logic from the data presentation is a well known necessity of proper programming in larger projects. One can often see open source projects which forget or simply aren't aware of this. The code is filled with massive amount of echo statements, which makes customization of the design and I18N (internationalization) attempts rather difficult. My heart would be warmed by the thought that some of the future projects won't suck so much as the result of the use of various templating systems! :)
As the conclusion, I'd be glad to see your comments and suggestions on how to make this tutorial better. You can send me e-mail to the address ivans@email.hinet.hr. I'll try to reply as soon as possible to let you know I've read it, but I can't promise anything!
About the AuthorIvan Stojic likes to play and is a kid at heart. Besides attending the local computer engineering college, he takes time to read and write a lot. Ivan makes software for cash and entertainment. A long time ago he liked writing programs in Pascal, but he has since found a new love - Java. Other than that, he enjoys fooling around with C/C++, Perl, PHP, XML and is specially interested in code generators and distributed computing.
Oh, and he also likes freelance programming jobs, so give him a ring if you need something done!
| DISCLAIMER: The content provided in this article is not warranted or guaranteed by Developer Shed, Inc. The content provided is intended for entertainment and/or educational purposes in order to introduce to the reader key ideas, concepts, and/or product reviews. As such it is incumbent upon the reader to employ real-world tactics for security and implementation of best practices. We are not liable for any negative consequences that may result from implementing any information covered in our articles or tutorials. If this is a hardware review, it is not recommended to open and/or modify your hardware. |