If you are unfamiliar with some of the basic concepts around templating, take a moment to review my previous post: How to Create a Simple PHP Templating Function, where I explain how to look for files, buffer output, and extract variables into scope.
For those unfamiliar with classes and OOP, know that this post doesn’t attempt to explain the concept too much, but instead provides a practical example of how a class can be used.
And before we get started, here is a simple OOP vocabulary list for reference.
- Encapsulation – the concept of grouping like-functionality together.
- Class – group of functions and variables that work together as a single concept. When you write a class, you have “Encapsulated” those functions and variables.
- Method – a function that is part of a class.
- Property – a variable that is part of a class.
- Instantiate – the creation of a new object from a class.
- Instance / Object – a run-time value of some class.
Now let’s take a look at this new template class:
The main take away here is that we have broken our previous single function into multiple smaller functions, and encapsulated them together within a class.
Here is a contrived usage of this class:
Let’s walk through what is going on above:
- First, we instantiate the class as a new object named
$tpl. During the creation of the object, we pass in the folder location where we expect our class to find template files.
- Next, we run the
render()method, providing our template name and the variables we would like to inject into the scope of the template.
render()method then executes another method within the class named
find_template(), which loops through the suggestions and looks for the first file it can find.
- If a template file was found, the
render()method then calls the
render_template()method first starts an output buffer so that our output is captured as opposed to being sent to the screen.
Then it dynamically defines the variables into the scope and includes the found template file.
When done, it returns the buffered output to the caller (in this case the “caller” is the render() method).
- Finally, the
render()method returns the output to the caller (in this case the “caller” is the above example usage of this class).
How this class improves upon the previous function:
- No hard-coded template path. Now each instance of this class can define its own template path, and an instance’s folder can but updated using the
- No potential for extract variable collisions, as no variables are defined within the scope of the
By using the
func_get_args()function to access the values for parameters passed into the
render_template()method, we avoid naming the variables within the scope. This mean that when we later
extract()the variables, it is not possible for an extracted variable to conflict with another variable within the method.
- Template suggestions are run through
array_reverse()before searched, to provided a better developer experience when building the $suggestions array.
This means that when you are creating a list of template suggestions, you can easily add more-specific suggestions to the end of the array, as opposed to needing to unshift() them to the beginning.
Using Template Suggestions
While this example is contrived, hopefully it is clear to see how easily you can add more-specific suggestions to the existing list of suggestions.
There we have it. Using the same concepts presented in the previous blog post we have broken that function into smaller pieces and encapsulated those pieces within a class. In doing so, we have provided significantly better (more flexible, less error-prone) functionality and developer experience.
Let me know what you think!