janwijbrand at gmail.com
Thu Jul 26 04:13:03 EDT 2007
> > Making sensible defaults is in the spirit of agility, right? And the
> > default Zope 3 security policy is sensible.
> > For the developers of Rails, such choices are harder. Since they have
> > no underlying framework like we do, the risk of boxing-in the end
> > developer is greater for them.
> > In Grok I think we can offer one preferred way without fear, because
> > the end developer always has the option of going the Zope 3 way if
> > more flexibility is needed.
> I have a working prototype in my own application already. I can easily
> port it to a grok branch for others to look at. I will do so tomorrow.
It's implemented on the jw-define-roles-directive branch now. Maybe
someone wants to try it?
More information about the Grok-dev