Re: [PHP3] template engine example document
| From: | Monte Ohrt | Date: | Fri, 24 Mar 2000 22:11:37 +0000 |
| Subject: | Re: [PHP3] template engine example document | ||
| References: | 1 2 | Groups: | php.template |
| Request: | Send a blank email to php-template+get-464@lists.php.net to get a copy of this message | ||
Hi Ron,
Ron Chmara wrote:
>
> So, the programmer sticks the logic in an include (or require), the HTML folks
> assign values to the variables....the coders mess with the logic, not the html,
> the html folks mess with the HTML (as needed).
>
> What's missing from this?
>
> -Bop
With your method, the programmer must change the PHP logic (what is
included) for each template. How is this scalable to manage many
templates? You are no longer separating form (presentation) from
content.
The way we proposed to make this work: the programmer passes content to
the template, the designer controls the presentation of this content,
and they control ONLY the presentation. The small set of functionality
in the template spec accomplishes just that. The designer can make
templates to their hearts desire without the need to change the PHP code
underneath. Then later if you want to update the PHP code, there is only
one set of code to update, not a whole slew of differing PHP code for
each template.
Monte