[Grok-dev] solving the grok.template() bug - part A of the solution

Jan-Wijbrand Kolman janwijbrand at gmail.com
Tue Jan 13 02:47:22 EST 2009

On Mon, Jan 12, 2009 at 11:28 PM, Martijn Faassen
<faassen at startifact.com> wrote:
> We could consider giving up rule 3) altogether as "too magic" and
> requiring everyone to spell out grok.context() on the module-level at
> the least. That's not a very onerous requirement.

As you might expect, I'm very much +1 on this.

> Perhaps we need a
> design rule that a directive default can be either a fixed value, or a
> value based on properties of the class it is used on, but cannot be
> dependent on other things in the module. grok.context would violate that
> rule, but I cannot think of other directives that do.

There's one other directive that behaves a bit like grok.context and
that it grok.viewletmanager.

BTW, if we'd change the rules for grok.context and grok.viewletmanager
not to have them look for implicit information, then only
grok.template still does. What's your opinion on that.

> We'd need to widely discuss this with the community though before making
> any such move.

When we reach consensus on a proposal, I could write it and send it to
the list as a separate topic.


Jan-Wijbrand Kolman

More information about the Grok-dev mailing list