[Grok-dev] A simple view grokker?

Souheil CHELFOUH trollfot at gmail.com
Thu Mar 19 07:15:24 EDT 2009

Hi Martin,

You can register your simple view as a grok.MultiAdapter. When not
using it strictly as a rendering component, it makes more sense,
according to me.

2009/3/19 Martin Aspeli <optilude+lists at gmail.com>:
> Hi folks,
> Today, I've used grokcore.view (actually, five.grok) for a few views
> that are not, strictly speaking, browser pages. One of them is a form
> handler that does all its work in __call__() and then redirects to one
> of several possible pages. The other is a control panel form that uses
> some Plone base classes and z3c.form.
> In both cases, I don't want a render() or a template. Unfortunately, I
> have to define an empty render() for the grok.View grokker to work. I'm
> also a bit worried that the various helpers that grok.View has in the
> base class could collide with some of the forms stuff.
> Perhaps it would be nice to have a grok.SimpleView (better names
> welcome) grokker that registered a view and supported the various
> directives, but did not attempt to find a template or provided any base
> class functions beyond the __init__?
> Cheers,
> Martin
> --
> Author of `Professional Plone Development`, a book for developers who
> want to work with Plone. See http://martinaspeli.net/plone-book
> _______________________________________________
> Grok-dev mailing list
> Grok-dev at zope.org
> http://mail.zope.org/mailman/listinfo/grok-dev

More information about the Grok-dev mailing list