[Grok-dev] megrok.layout --> grokcore.layout and megrok.chameleon --> grokcore.chameleon

Sylvain Viollon sylvain at infrae.com
Fri Jul 15 07:28:44 EDT 2011

On Fri, 15 Jul 2011 13:19:59 +0200
Jan-Wijbrand Kolman <janwijbrand at gmail.com> wrote:

> Hi,


> A while ago I suggested to "promote" megrok.layout and
> megrok.chameleon into the grokcore.* namespace and make them "First
> Class Cavemen".
> This week Jan-Jaap, Sylvain and me worked on this rename, which was
> essentially mechanical work - even though Jan-Jaap was able to
> clean-up megrok^H^H^H^H^Hgrokcore.chameleon even further, freeing it
> from zope.app. cruft that was left behind.
> As a result we do now have grokcore.layout and grokcore.chameleon. The
> grok package depends on these two now and exposes the components of
> grokcore.layout (and at the same mixes in application_url() and
> flash() methods) for Layout, Page, FormPage, AddFormPage,
> EditFormPage, DisplayFormPage. There's also ExceptionPage,
> NotFoundPage and UnauthorizedPage.
> Even though grokcore.chameleon does not have "exposable" components
> per se, the grok package includes the configure.zcml of
> grokcore.chameleon which means, templates with a *.cpt filename
> extension will be processed by the Chameleon template engine.

  I often use megrok.chameleon.components.ChameleonPageTemplate(OrSo),
  when I have a component and no grokker for it. I would love to have a
  nicer import (like in the package __init__).



Sylvain Viollon -- Infrae
t +31 10 243 7051 -- http://infrae.com
Hoevestraat 10 3033GC Rotterdam -- The Netherlands

More information about the Grok-dev mailing list