[Grok-dev] grok.require() can refer to a class too,
Was: sprint mini-report 2
janwijbrand at gmail.com
Fri May 2 06:26:06 EDT 2008
Martijn Faassen wrote:
> * grok.require can now refer to Permissions directly (on a branch),
> instead of only on a name basis.
This branch has just now been merged with the trunk. Now I should update
the grok_overview.rst documentation... And the notes on using
permissions on the grok.zope.org site of course too.
Anway, when you define your own permission in your Grok-based
application, instead of doing:
you can now do:
* your permission components do still need a grok.name() directive (as
they always did), because on a Zope-level it is this name that is used
for (local) grants.
* you can still use the grok.require() directive with a permission name,
e.g. in case of permissions defined outside your own application, like
* Grok defines a special "permission" called Public. So, in case you
explicitly want to "require" the 'zope.Public' "permission" you can do this:
More information about the Grok-dev