Summary of advanced PHP templates

How to use PHP to write code quickly, templates seem to be the only choice. But should a PHPer ultimately stick to using templates, give up on templates, or use his own templates?
The following thoughts belong to all PHPers:
“In fact, the most important thing about a template is that it suits your own project needs, not your own habits. For example, a corporate promotional website does not have many visits and few updates. It's the same, or even unnecessary. Writing directly in PHP+HTML is probably the fastest. There's nothing wrong with that. But if it's a news system or a content publishing system, it's very necessary to use templates. Technology. Because they all have one thing in common, that is, there is a type of page that uses the same style of page design. And depending on the actual situation, such as the size of the visits, the urgency of the project and the programmer's proficiency in template technology, Choose the template technology that is most suitable for the project. This is the first choice. "[from leslee]
"I have been exposed to templates since I started learning PHP. I use smarty template engine (officially supported, powerful), and the longer I use it, the better it becomes. I think templates are a good thing. As long as it involves page display, I will use templates to write programs. I think other PHPers will have the same feeling, because the original intention of template design is. Separate the code and the page and process them separately. After all, no one wants to write code and process the page at the same time. ”
“Some people say that SMARTY is already very good, but some people say that SUPERTPL is better, and some people prefer PHPLIB. I think everyone. Each template has its own advantages and disadvantages. The key depends on what your project needs and which one is best! "[from feifengxlq]"There is definitely nothing wrong with using templates. I originally used PHPLIB and have been using it for a while. In the end, it felt too simple. Each template variable had to be replaced by code, and each template referenced also had to write a line of code (maybe PHPLIB has a batch processing function, I am too naive to know), so I gave up and later used plog to build the website. I came into contact with smarty at that time. I felt that smarty was too large and could indeed speed up the development progress. However, many functions were not actually used. Therefore, I finally wrote my own template engine. The function to be implemented by the template is very simple, which is the replacement function of a template variable. , plus include other template and foreach block operation functions. ”
“I still use PHPLIB, but I will write some functions or classes based on my own experience and needs to encapsulate some of the most commonly used template output processing.” [From seraph] "I use my own templates, and I have to write template parsing code, which is tiring. I choose to use existing excellent templates." [From Bantu] "I even saw some great people on other forums who don't use templates. ...Maybe I haven't reached that level... Personally, I think it's better to use templates... At least it can divide the work... and speed up development. Use your own templates? I don't think it's necessary... Just use ready-made ones... Add some practical functions that you want to learn based on the ready-made ones. " [From Phzzy] "I don't use a template engine, but I still use templates, just different from yours. Because the template engine is too slow, it feels difficult to use. ”
“I use a third party, preferably open source. As for which one to use, it depends on personal preference. ” [from leeyupeng] “I still tend to use my own templates that are simple and practical. "[From Yuhi] "Due to performance considerations, I generally do not use universal templates. I will make some trade-offs based on the actual situation, which has certain limitations. "[From Ben] "Decide whether to use templates or not, and what templates to use, based on your needs. It never hurts to be flexible. "[From xlmo] "I personally like simple and fast templates. You can consider using ready-made templates. However, I usually optimize them based on the actual project and delete some functions that are not used. "
"Using templates generally does not cause bottlenecks. As for the efficiency, the main points are as follows:
1. After the program and template are separated, one file becomes two or more, and the IO of reading the template is also It’s important to take time
2. Parsing templates is relatively complicated, generally requiring N preg_match, preg_replace and other functions to process or replace
3. The loading and replacement of templates obviously requires more memory than not using templates
So pay attention to the following points to improve efficiency:
1. Choose a template parsing program that supports compilation and caching. This has the most obvious benefit on performance. It depends on how you apply it flexibly. 2. The parsing program should be as simple as possible, and all functions should be included. It is more convenient to use, but the performance is also worse
3. When making HTML template pages, we also follow simple principles, such as making them according to the xhtml standard, and try not to split a page into many templates and then include them. ”
“If you use a template, I think it’s better to write one yourself if you have the ability. This is also exercise. But if you want to use it, I think Xiaoqiang is good. Can be edited under visualization."[From jejwe]"I personally think that the visual editability of template files is very important. It cannot be required that the production of template pages also requires considerable program development foundation. "[From seraph]"A detailed analysis of specific problems, whether to use templates or not, whether to choose an excellent template class that has already been formed or to write it yourself, everything is based on the specific project development, and you cannot settle on which one. "[From Deepseath] "I feel that the existing templates are not perfect enough, either with few functions or slow speed. It is better to make them yourself. ”
“In summary, PHP templates can make your code context clearer and the structure more rational. However, the development of PHP templates will always be much slower than the rapid development of PHP applications. In this case, it will affect the development of PHP applications. For every PHPer, no PHP template is the most suitable and perfect for him. Because the so-called PHP template is a popular thing, not personal. Therefore, if you can fully understand the advantages and disadvantages of templates and the principles of PHP application based on a clear understanding of PHP characteristics and applications, PHPer can get the PHP templates you need that suit your own development style. This is also one of the most important ideas of PHP. PHP only provides methods and approaches, not the final solution. Therefore, templates, like PHP applications and products, can be transformed into their own PHP templates. Because it contains the thoughts of the creator.
It is limited by various conditions, such as time and experience, so you may think that it is very difficult to make your own PHP template. In fact, what you need is not to reconstruct a PHP template, but to choose a PHP template that is closest to you and transform it. Because PHP needs inheritance and innovation. Of course, make your own PHP template and implement it step by step, and incorporate the latest ideas and concepts in a timely manner. Individual PHPers can start from the details, from where they need it most and from their own development habits. The PHPer team can work together to localize PHP templates, which is especially practical for companies. Even if you just modify a symbol in the PHP template, just a symbol can show that you have modified it, and it belongs to you. The most important thing is that your own PHP template is never fixed. It will grow with you and become a witness of your PHP journey.
PHP does not require very proficient syntax; PHP does not require you to develop numerous libraries yourself; PHP does not require you to worry about performance, stability and other characteristics of the language itself. What PHP needs is your logic; what PHP needs is your creativity; what PHP needs is your thinking! "

The above introduces the summary of the advanced part of PHP templates, including aspects of content. I hope it will be helpful to friends who are interested in PHP tutorials.