Re: Template Proposal
| From: | Paul Meagher | Date: | Fri, 09 Nov 2001 15:09:49 +0000 |
| Subject: | Re: Template Proposal | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-2728@lists.php.net to get a copy of this message | ||
http://www.developmentor.com/genx/default.asp
> 3. Templates are nice tools, but it remains Search and Replace solutions.
> Abstract builders are much more powerful, as you can:
> - code pages entirely using objects without HTML,
> - build a page visually and generate code.
> I see not problem in using templates in abstract builders.
One of the main purposes of the templating we have been talking about has
been to shield designers from the complexity of coding by allowing them to
embed tags into their HTML code that, when run through a transformation
engine, would populate the HTML with relevant values pulled from a content
store.
When I suggested XSLT as the ultimate templating solution this is arguably
incorrect for the above scenario. Smarty and IT[X] may be better ways to
go when shielding designers is the goal of your templating engine.
Another use of templates, however, is to try to achieve a separation of
content from presentation so that you can take the same content and deliver
it via multiple devices. In this type of scenario, XSLT is arguably the
tool for the job. Graphic designers would still need to be involved in a
project like this, but I think that they need to add XML and XSLT to their
skill sets if they don't want to be left behind. Molly E. Holzschlag is
taking the pulse of this trend at:
http://www.webtechniques.com/archives/2001/11/desi/
Another use of templates is for the abstract builders you are talking
about. Not sure exactly what you mean, but my interpretation is that it
involves using templates to autogenerate code. In this scenario, the users
are primarily programmers wanting the achieve the goal of rapid code
development which is a scenario that is quite different in terms of users
and goals then the two mentioned previously.
The best example I have seen of using "templates" to autogenerate code is:
http://www.developmentor.com/genx/default.asp
The term templating is confusing because it can be used in these three
different scenarios and involves using "templates" to achieve very
different goals.
We need to start being more precise in our use of terms or we will be
talking past one another. I am guilty of this myself in my previous
posts.
Regards,
Paul Meagher