Re: [Phplib-users] template extensions

[Aric C. <gre...@pe...>]

>
>   The proposed approach would sever that connection. Instead of a
hand-crafted
> script sitting in front of each template defining variables (in a
> coder-dependant manner that may or may not encourage reuse), there would
be a
> standard location where dynamically generated content would live. As a
> template is evaluated, and reference to that content are detected, it
would
> be imported and generated.
>
>   Notice that lovingly hand-crafted scripts (made by italian monks to the
> highest standards, using a secret process handed down from their celebate
> forefathers) are no longer necessary. All templates can be treated the
same.
>
>   Notice that all dynamically generated content in a site is now put into
a
> single location and forced to be encapsulated (there are arguments against
> wholesale encapsulation, but that's where php's 'include' statement comes
into
> play).

Another aspect of this is that if the designer wants something that hasnt
been coded yet, he can just put some dummy html data into a file where the
function would be, and the programmer can come along later and turn it into
proper php code.

> --
> Evan Hughes
> OpenConcept Consulting
(openconcept.ca)
>
>
>
> -------------------------------------------------------
> This SF.NET email is sponsored by: Take your first step towards giving
> your online business a competitive advantage. Test-drive a Thawte SSL
> certificate - our easy online guide will show you how. Click here to get
> started: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0027en
> _______________________________________________
> Phplib-users mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phplib-users
>