[Grok-dev] Grok and chameleon

[Chris McDonough]

Core chameleon doesn't support path expression syntax, but it allows for 
expression types to be plugged in.  You'd need to build something like 
http://pypi.python.org/pypi/five.pt/0.8 for zope3 I think.

- C

On 2/5/10 2:33 PM, Souheil CHELFOUH wrote:
> Unless i'm mistaken, all TAL expressions are python ones
> so, you have to replace the current ones by python ones :
>
> tal:content="request/principal/id"  =>   tal:content="request.principal.id"
> tal:define="something context/myMethod" =>  tal:define="something
> context.myMethod()"
>
> 2010/2/5 Martijn Faassen<faassen at startifact.com>:
>> Souheil CHELFOUH wrote:
>>> When i first started Dolmen, a year ago, I used Chameleon as a base
>>> template engine.
>>> Things are : the syntax is not 100% compatible with the current one.
>>> It means adapting templates that already exist.
>>> The speed gain is not that important, on well structured pages. So I
>>> dropped it. I thought people might be confused to have to learn other
>>> languages.
>>> But, if it's shipped as default, then, it might be interesting
>>> That were my .02
>>
>> We need to do impact analysis to see what the cost would be of shipping
>> this by default.
>>
>> Is there a page somewhere which spells out how templates can break due
>> to syntax changes?
>>
>> How easy is to, say, debug chameleon templates compared to
>> zope.pagetemplate ones?
>>
>> What would the possible interactions be with the use of
>> zope.pagetemplate within ZTK code?
>>
>> Without knowing all that, I'm in favor of trying to go there with Grok
>> in the future.
>>
>> Regards,
>>
>> Martijn
>>
>> _______________________________________________
>> Grok-dev mailing list
>> Grok-dev at zope.org
>> https://mail.zope.org/mailman/listinfo/grok-dev
>>
> _______________________________________________
> Grok-dev mailing list
> Grok-dev at zope.org
> https://mail.zope.org/mailman/listinfo/grok-dev
>


-- 
The repoze.bfg Web Application Framework Book: http://bfg.repoze.org/book