<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Embedding code in web templates doesn't work well when you have<br>designers on board.<br></blockquote>
<div> </div>
<div>That's not necesarily true. Templates where there is mostly markup, but let you embed code into them using special tags (ex, <% code %>) are extremely popular and work fairly well. They also keep the template language simple because there is already a full-powered programming language thats embedded into it. Good examples of this method are ERB templates in Rails, JSPs, Perl Mason templates, etc.
</div>
<div> </div>
<div>In these cases one of two things happen: either the designers learn enough of the programming language to embed the right things in, or they just hand off HTML to the developers, who can then replace the dynamic parts with <% %> tags. If I'm a designer and I have learn a new templating language anyway, I may as well just learn a little bit of Haskell/Ruby/Perl/Java/whatever.
</div>
<div> </div>
<div>The best choice of templating technology really depends who the target audience of the web framework is. Has there been much thought given to that yet?</div>
<div> </div>
<div>Maurice</div>
<div><br><br> </div>
<div><span class="gmail_quote">On 4/5/07, <b class="gmail_sendername">Joel Reymont</b> <<a href="mailto:joelr1@gmail.com">joelr1@gmail.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><br>On Apr 5, 2007, at 2:51 PM, David House wrote:<br><br>> Why add another dependency, force your coders to learn another
<br>> language, restrict yourself to a language which isn't as expressive as<br>> Haskell, reduce your ability to reuse code from different areas of the<br>> project and decrease project-wide consistency when you could just
<br>> write your templates in Haskell to begin with?<br><br>Embedding code in web templates doesn't work well when you have<br>designers on board.<br><br>Let me elaborate on my approach as it doesn't reduce or restrict
<br>anything!<br><br>I'm suggesting that you make your templates look like this, which is<br>parseable as XML. Note the "tal:" tags. Please scroll through to the<br>bottom for more thoughts.<br><br><?xml version="
1.0" encoding="ISO-8859-1"?><br><html><br> <head><br> <title tal:content="page/title">Page title</title><br> </head><br> <body><br> <h1 tal:content="page/title">Heading</h1>
<br> <p><br> Hello <b tal:omit-tag="visitor/humble"><span<br>tal:replace="visitor/name">wo<br>rld</span></b><br> </p><br> <p tal:condition="msg page/message" tal:content="msg">Message</p>
<br> <ul><br> <li>Hard-coded</li><br> <li tal:define="users page/users" tal:repeat="item users"<br>tal:content="ite<br>m/name">Dummy</li><br> </ul>
<br> <p tal:condition="page/renderfooter"><br> Back to<br> <a href="#" tal:define="up page/up" tal:attributes="href up/<br>href;title up/<br>title">index</a>
<br> </p><br> </body><br></html><br><br>The above expands into this:<br><br><html><br> <head><br> <title>Demo page</title><br> </head><br> <body><br> <h1>Demo page</h1>
<br> <p><br> Hello<br> <b>Bruno</b><br> </p><br> <p>(c) 2006</p><br> <ul><br> <li>Hard-coded</li><br> <li>Xavier</li><br> <li>Damien</li>
<br> <li>Jacques</li><br> <li>Didier</li><br> <li>Jerome</li><br> </ul><br> <p><br> Back to<br> <a title="Caml Home" href="<a href="http://caml.inria.fr/">
http://caml.inria.fr/</a>">index</a><br> </p><br> </body><br></html><br><br>Note how<br><br> <ul><br> <li>Hard-coded</li><br> <li tal:define="users page/users" tal:repeat="item users"
<br>tal:content="ite<br>m/name">Dummy</li><br> </ul><br><br>is expanded to<br><br> <ul><br> <li>Hard-coded</li><br> <li>Xavier</li><br> <li>Damien</li>
<br> <li>Jacques</li><br> <li>Didier</li><br> <li>Jerome</li><br> </ul><br><br>This is nice and _very_ clean and allows you to use any Haskell code<br>you want to _process_ the template. You can, in fact, make template
<br>processing recursive and have tags produce more tags, i.e. make your<br>components produce HTML instead of data for tags in the template.<br><br>What do you think?<br><br>--<br><a href="http://wagerlabs.com/">http://wagerlabs.com/
</a><br><br><br><br><br><br>_______________________________________________<br>web-devel mailing list<br><a href="mailto:web-devel@haskell.org">web-devel@haskell.org</a><br><a href="http://www.haskell.org/mailman/listinfo/web-devel">
http://www.haskell.org/mailman/listinfo/web-devel</a><br></blockquote></div><br><br clear="all"><br>-- <br><a href="http://blog.mauricecodik.com">http://blog.mauricecodik.com</a>