[Grok-dev] grokcore view

Souheil CHELFOUH trollfot at gmail.com
Sat Dec 19 10:02:04 EST 2009

No, ViewSupport is fine, but, does not provide enough (in my opinion,
for what it worths)
Thing is : in view-ish component, we might also need security or/and
static or/and namespace...
What i'm trying to thing of, is a way to easily plug all these
features, independently on components.

2009/12/19 Martijn Faassen <faassen at startifact.com>:
> Souheil CHELFOUH wrote:
>> Bloody keyboard. Sorry.
>> I was saying :
>> I didn't quite follow all the activity around grokcore.view and I now
>> explore the 1.13.1 version
>> I see that a mixin class has been created (ViewSupport).
>> The usual usecase (the megrok.layout Layout component or the
>> megrok.z3cform Form one),
>> are typically views that don't want to be grokked by the view grokker.
>> I think that we need a way to easily plug the "static" and other
>> namespace features on other components.
>> I don't know if you, guys, ran into such needs, but, I think that we
>> should think of a way to either :
>> 1. Find a way allow or not the grokking of a class by a particular grokker
>> 2. Explode the features into more comprehensive classes and grokkers,
>> that would allow us to reduce the code duplication.
> I'm not sure I understand, perhaps because I haven't delved into the
> details. Maybe JW can say more here. I understood the reason for
> ViewSupport to be so that it could be mixed into other view-like
> classes. ViewSupport itself wouldn't cause such class to be grokked, right?
> Regards,
> Martijn
> _______________________________________________
> Grok-dev mailing list
> Grok-dev at zope.org
> https://mail.zope.org/mailman/listinfo/grok-dev

More information about the Grok-dev mailing list