HI Hanno<div><br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Changing the default expression is easy. <a href="http://z3c.pt" target="_blank">z3c.pt</a> does exactly that to<br>
keep compatibility with zope.tal.<br>
<div class="im"><br>
</div></blockquote><div><br></div><div>Just found it too, looks like it might be the right place to start.</div><div><br></div><div>The other thing I am trying to find is batch compiling all of the templates.</div><div>I can't rely on 100% coverage in dev for all of the templates to be compiled with chameleon</div>
<div>before deployment to appengine, have been hunting around for some docs on this.</div><div><br></div><div>Any pointers ?</div><div><br></div><div>T</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">> So at this point chameleon needs to be api/implementation compatible with<br>
> zope.pagetemplates (metal included) or its a big job<br>
> shifting.<br>
<br>
</div>It is 99% compatibile. The only real difference is, that it requires<br>
all your templates to be valid XHTML. Otherwise almost all of<br>
Zope2/Plone with all kinds of weird code works.<br>
<div class="im"><br>
> Hey it was just a suggestion and if people think zope.pagetemplate is a bit<br>
> of a dead end, then maybe I should invest the time<br>
> on chameleon<br>
<br>
</div>I think zope.pagetemplate is a dead end for anyone not using one of<br>
the large frameworks.<br>
<font color="#888888"><br>
Hanno<br>
</font></blockquote></div><br></div>