FreakyWiki: a simple wiki banged out in Grok

...the update-method (re: page.py) is not to prepare data that will only ever get used once, e.g. ``rendered_content``, but rather to provide a chance to peek or poke at the rendering environment before any page element gets rendered.

I think it causes less confusion to simply have a method ``get_rendered_content`` and call it straight from the template.

\malthe

The purpose of the update() method on a Grok view is exactly preparing stuff for the template. That's how we've been advertising this method in Grok and I think it makes sense that way. Because with it you can write templates that are push-like: You prepare data in the update() method, push it onto the view class and then just use it from the template.

I don't see the advantage of writing abitrary methods on the view class (and thereby introducing some custom interface of how to talk to the view code).

I'm not disagreeing with the fact that update() could be used to implement more, for instance form handling, updating database objects, or take a peek at the environment. I'm just saying it's nice to have one well-documented entry-point for view code. And I like "push" for templates rather than "pull" and the update() method together with view attributes are a neat way to get there, I think.

-- philiKON