This could be also achieved simply by using _set and _get, so: class Template else throw new TemplateNotFoundException() Īnd invoking it would look like: $view = new Template() Īs far as I remember, this is how the old Symfony 1.x and the Zend_View template engines look like, and for me it's fine. Personally, what I usually prefer is to implement an ArrayObject class with a properties array, and the template would refer to $this->propertyName, which in fact would be the template object's $this->property. I wouldn't do the second approach as the parameters aren't named.Ī well-written essay on describing how a template system should work is coming from Parr, it's often quoted by people writing template systems and/or web-mvc frameworks. Is the second approach better? Is there an even better way to do it? I feel like a better approach is to wrap your template inside a function:
PHP HTML TEMPLATE CODE
And you're using an include() to execute code when you do include('template.php')(as opposed to using include() to include a class or a function which isn't immediately executed). The basic idea of this mechanism is to separate the data elements (the model), the user interface (the view), and the code that connects the model and the view (the controller). To me the above isn't well structured in the sense that template.php depends on variables that are defined in other scripts. As web development becomes standardized, the Model-View-Controller (MVC) architecture has become more popular. I was reading this question over on stackoverflow:Īnd the accepted answer says to do plain PHP templates like this:
0 kommentar(er)
