[Grok-dev] megrok.chameleon and (custom) template namespaces

Uli Fouquet uli at gnufix.de
Sat Apr 16 09:40:31 EDT 2011

Hi Soulheil,

Souheil CHELFOUH wrote:

> For the provider: expression, you can copy the code from Dolmen
> it's the work i did for chameleon 2.0 on Dolmen, after we forked from grok
> http://gitweb.dolmen-project.org/dolmen.tales.git

Thanks a lot, Souheil! I already had a look into dolmen.template and
dolmen.tales. Especially the TALES-expression-plugin-technique via entry
points looks interesting.

But now I already switched to z3c.pt for the base work. z3c.pt registers
almost everything we normally need - including the `provider`
expression. This already worked in megrok.chameleon before JJ and JW
showed up.

I reintroduced z3c.pt for TALES evaluation because the new z3c.pt
version (2.x) is a complete rewrite for Chameleon 2.x (the older
versions raised some problems) and it is maintained by Malthe (the
Chameleon-man), so we can delegate that (sometimes nasty) part to
someone who should really be into this. When Chameleon changes, that's
my hope, also z3c.pt will change and we don't have to do much from our
side except updating the version numbers in gtk.

The overall idea is to have the standard set of TALES expression
registered automatically when you depend on megrok.chameleon. That takes
the burden of identifying possible expressions and registering them for
the own project from users. Just depend on megrok.chameleon and all the
expressions from the common howtos are available.

That, however, does not need to be the end of the road.

Best regards,


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
Url : http://mail.zope.org/pipermail/grok-dev/attachments/20110416/c790afdc/attachment.bin 

More information about the Grok-dev mailing list