Thanks Michael!
Actually the permission may change because the view (a form) applies to a
an object whose permissions depends to it's own parent's status, and I
don't want to make these objects inter-dependant (the "child" doesn't have
to know the class of it's parent!); I also use a quite complex
Does the permission actually need to change or can the context object just
return an appropriate ACL based on its state? If you can have the context
object be smarter then problem solved with a single permission. Otherwise
yes you can certainly just handle it imperatively in the view code.
On
Hi,
In an application using ZODB traversal, I need to create a view whose
required permission depends on the state of the "context" object to which
the view is applied.
Can I just create an "un-protected" view (without static permission) and
check the permission in the view initialization code
