PHP Next Convenient and easy to use template processing class

Title: A convenient and easy-to-use small template processed Author: Stangly Wrong

Handbook address:

Http://blog.9cbs.net/stangly/archive/2004/12/08/209102.aspx

Template technology in PHP has always been a popular technology. Since 2001, many fans in PHP quoted the MVC development model in PHP, template technology is more hot.

Many famous template engines, such as phplib Template, FastTemplate, EasyTPL, BTemplate, and SMARTY template engines that are now packed in PHP.NET and many fans.

I personally like those short-sighted PHP code, like the template engine implemented by SMARTY's 2000-multi-line code, have to be a daunting.

For a few more time, I saw a article on phpe.net called << Beyond Template Engine >> The author Brian Lozier said that it is really very reasonable. He said this: Smarty's goal is to "separate business logic from the performance" rather than "Separation of PHP code and HTML code". But Smarty is really too big. If I am using Smarty, I will feel that Smarty will affect PHP code execution efficiency, first in parsing the SMARTY code that parsed more than 2,000 lines may have a large latency. Although he uses compilation technology, the program still needs to run the smarty engine include at runtime, and the PHP script engine will go to parse this huge code. Think about it is also terrible.

Affected by Brian Lozier, I realized that PHP itself is an embedded scripting language. If we can use a template written with a simple PHP code, and directly in the runtime, isn't it more fast? The result is also the same as I guess. After I use Brian Lozier's class test, I really be 50% faster than Smarty. Tag code my name is {myname}. Why don't we write to my name is . Is this like? And there are common lists in template, in fact, simple loops. Begin user_list -> user ID: {var0} User name: {var1} Why don't we write as follows?

user ID: user name:

As early as a year, I tried to use this method to do some businesses and governments, but I didn't consider the benefits of doing this. Just feeling this template I don't need a separate code to deal with him, just simple include include. Moreover, I remember that when I did these templates directly written directly in PHP language, I was very fast, so that I have developed several artificials, I have developed a lot of interest in PHP, and I started learning PHP. Script language.

Recently, I have been influenced by the << Beyond Template Engine >>, so I decided to implement a template processing class according to his thoughts. After two or three days, I have completed a template. class. Now posted here so that you can discuss with me.

Considering that this tag that is often used often uses {name} to do templates, so I write a simple compile () method to parse such a file, convert it to Such php Template file. The converted file is then stored in the corresponding cache directory and then provides a _parse () method to the include file and then output in the main program. In order to simplify the calling method. Use a PARSE () method to call the above two private methods. The following is an example:

First give a directory structure: / root directory ├ --cache stores PHP template cache file ├─includes class inventory Putalog │ └─Template Template Processing Template.php Class Library File Save Directory └─Templates Template Directory ├─Imgs Template file Picture Directory │ └ -VER.1 └ -TPLS Template file directory └ -VER.1 Example 1: Process for the template file for the HTML type. Example 1: Process for the template file for the HTML type. Test.htm.php template file Store in /Templates/tpls/ver.1/ directory