HI Hanno
Changing the default expression is easy. z3c.pt does exactly that to > keep compatibility with zope.tal. > > Just found it too, looks like it might be the right place to start. The other thing I am trying to find is batch compiling all of the templates. I can't rely on 100% coverage in dev for all of the templates to be compiled with chameleon before deployment to appengine, have been hunting around for some docs on this. Any pointers ? T > > So at this point chameleon needs to be api/implementation compatible with > > zope.pagetemplates (metal included) or its a big job > > shifting. > > It is 99% compatibile. The only real difference is, that it requires > all your templates to be valid XHTML. Otherwise almost all of > Zope2/Plone with all kinds of weird code works. > > > Hey it was just a suggestion and if people think zope.pagetemplate is a > bit > > of a dead end, then maybe I should invest the time > > on chameleon > > I think zope.pagetemplate is a dead end for anyone not using one of > the large frameworks. > > Hanno >
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
