[Grok-dev] grok.Layout and grok.Page
trollfot at gmail.com
Tue Oct 20 23:26:32 CEST 2015
Hello there Paul,
i'm one of the developers of grok.layout, so maybe I can share some
I've been away from grok for a while, but I'm still using that concept in
my python projects.
Viewlets and Layouts are not mutually exclusive, they are both tools to
compose a renderable view.
A layout is, as its name indicates, a way to organise your content,
The Layout doesn't hijack the managers, it still renders them, since the
TAL processor uses the 'view' variable of the template namespace to lookup
the managers and viewlet components.
The Layout can be used to radically alter the global rending of a site, but
also the managers called.
A Page is the core of what needs to be rendered for a given context,
without the whole html heavy load, without the contextual viewlets and
components coating, making it easy to aggregate them.
Since Layouts register on a layer, they can be a mean to skin your site
This concept exists in Zope3 for a while, under the name Pagelet (
https://pypi.python.org/pypi/z3c.pagelet). It was merely simplified for
2015-10-20 20:04 GMT+02:00 Christopher Lozinski <lozinski at freerecruiting.com
> Sorry for taking so long to respond. I was at the Plone conference.
> I am using grok.layout.
> And yes it calls a content method.
> I did not realize that i could use the command:
> I do not like grok.layout. Just was painful to use. It is not the
> model for user interfaces that I want to use.
> I have page templates, I edit them through the web. They can acquire
> You have a different approach. A very python centric point of view. If
> that is your point of view, go with it. Grok is
> pretty agnostic. It will let you do whatever you want with views.
> I hope that helps.
> On 10/16/15 10:22 AM, Paul Sephton wrote:
> > Is that correct? Do I have the right of it?
> Grok-dev mailing list
> Grok-dev at zope.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Grok-dev